Finite State · Domain Security

Finite State Domain Security

Domain security

Domain security posture for Finite State, probed live across 4 host(s) and 1 registrable domain(s). 4 host(s) serve HTTPS (up to TLSv1.3); 4 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=reject).

Product SecuritySoftware Supply Chain SecuritySBOMFirmware AnalysisVulnerability ManagementBinary AnalysisConnected DevicesComplianceCybersecurityIoT

Transport & Host Security

finitestate.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Sep 20 05:33:16 2026 GMT
app.finitestate.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 6 12:53:47 2026 GMT
docs.finitestate.io
HTTPS: yes · TLS: TLSv1.2 · HSTS: yes · cert expires: Nov 19 23:59:59 2026 GMT
platform.finitestate.io
HTTPS: yes · TLS: TLSv1.2 · HSTS: yes · cert expires: Nov 19 23:59:59 2026 GMT

Domain (DNS/Email) Security

finitestate.io
DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: none

Source

Domain Security

finite-state-domain-security.yml Raw ↑
generated: '2026-08-04'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml hosts (0-working/probe-domain-security.py,
  then hand-verified with curl and openssl s_client on 2026-08-04)
note: 'The mechanical probe reported hsts: null for every host and omitted
  platform.finitestate.io. Both were corrected against direct HEAD and GET
  observations: all four hosts return a Strict-Transport-Security header.'
hosts:
- host: finitestate.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 20 05:33:16 2026 GMT
  hsts: true
  hsts_max_age: 63072000
  hsts_include_subdomains: false
  hsts_preload: false
- host: app.finitestate.io
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  6 12:53:47 2026 GMT
  hsts: true
  hsts_max_age: 63072000
  hsts_include_subdomains: false
  hsts_preload: false
- host: docs.finitestate.io
  https: true
  tls_version: TLSv1.2
  cert_expires: Nov 19 23:59:59 2026 GMT
  hsts: true
  hsts_max_age: 31536000
  hsts_include_subdomains: true
  hsts_preload: false
- host: platform.finitestate.io
  https: true
  tls_version: TLSv1.2
  cert_expires: Nov 19 23:59:59 2026 GMT
  hsts: true
  hsts_max_age: 31536000
  hsts_include_subdomains: true
  hsts_preload: false
domains:
- domain: finitestate.io
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: reject
findings:
- id: no-caa
  severity: low
  detail: no CAA record is published for finitestate.io, so certificate issuance is
    not restricted to named CAs
- id: no-dnssec
  severity: low
  detail: DNSSEC is not enabled on finitestate.io
- id: tls12-on-platform-hosts
  severity: informational
  detail: docs.finitestate.io and platform.finitestate.io negotiated TLSv1.2 while
    finitestate.io and app.finitestate.io negotiated TLSv1.3
- id: dmarc-reject
  severity: positive
  detail: DMARC is published with p=reject, the strongest policy
- id: no-security-txt
  severity: medium
  detail: no RFC 9116 security.txt on any host, and no vulnerability-disclosure or
    trust page was found — a notable gap for a product security vendor

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/finite-state-domain-security"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.