generated: '2026-08-25'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: max.maicoin.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep  7 23:59:59 2026 GMT
  hsts: null
- host: campaign.maicoin.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  8 04:04:28 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: max-api.maicoin.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep  7 23:59:59 2026 GMT
  hsts: partial
  hsts_max_age: 63072000
  hsts_include_subdomains: true
  hsts_note: >-
    PATH-DEPENDENT, corrected after the automated probe. The probe reads the host ROOT, which
    returns 200 with NO strict-transport-security header, so it recorded hsts:false. A follow-up
    probe on 2026-08-25 of the actual API paths (GET /api/v3/timestamp and /api/v3/markets) DID
    return `strict-transport-security: max-age=63072000; includeSubDomains`. HSTS is therefore
    enforced on the API surface but absent on the bare host, which is a real (minor) gap: a first
    contact with https://max-api.maicoin.com/ is not pinned.
domains:
- domain: maicoin.com
  dnssec: true
  caa:
  - 0 issue "globalsign.com"
  - 0 issue "letsencrypt.org"
  - 0 iodef "mailto:security@maicoin.com"
  - 0 issue "amazon.com"
  - 0 issue "digicert.com"
  spf: true
  dmarc: true
  dmarc_policy: quarantine