generated: '2026-07-25'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.marshmallow.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  6 23:59:59 2026 GMT
  hsts: false
- host: auth.marshmallow.com
  role: authorization server
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov 11 23:59:59 2026 GMT
  hsts: true
  hsts_max_age: 31536000
  hsts_include_subdomains: true
- host: api.marshmallow.com
  role: private application API
  https: true
  tls_version: TLSv1.3
  cert_expires: Jan 12 23:59:59 2027 GMT
  hsts: false
- host: account.marshmallow.com
  role: consumer account portal
  https: true
  tls_version: TLSv1.3
  cert_expires: Jan  9 23:59:59 2027 GMT
  hsts: true
  hsts_max_age: 63072000
  hsts_include_subdomains: true
- host: docs.marshmallow.com
  role: gated docs distribution (403 anonymous)
  https: true
  tls_version: TLSv1.3
  cert_expires: Feb 27 23:59:59 2027 GMT
  hsts: false
domains:
- domain: marshmallow.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: reject
notes:
- >-
  Extended on 2026-07-25 beyond the script's apis.yml-derived host list to cover
  the four other live Marshmallow hosts (auth., api., account., docs.), each
  probed directly over TLS and HTTP HEAD.
- >-
  HSTS is enforced on the two hosts that handle user credentials
  (auth., account.) but not on www., api. or docs.
- No CAA records and no DNSSEC on marshmallow.com; SPF present and DMARC at p=reject.
- No RFC 9116 security.txt is published on any host (see well-known/marshmallow-well-known.yml).