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