generated: '2026-07-25' method: probed source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts hosts: - host: apollocover.com https: true tls_version: TLSv1.3 cert_expires: Oct 13 23:59:59 2026 GMT hsts: false - host: docs.apollocover.com https: true tls_version: TLSv1.3 cert_expires: Sep 17 03:05:30 2026 GMT hsts: true hsts_max_age: 31536000 - host: fpl95knwc1.execute-api.ca-central-1.amazonaws.com https: true tls_version: TLSv1.3 cert_expires: Feb 5 23:59:59 2027 GMT hsts: null - host: api.covertrack.ca https: true tls_version: TLSv1.3 cert_expires: Mar 4 23:59:59 2027 GMT cert_valid: true hsts: false domains: - domain: apollocover.com dnssec: false caa: [] spf: true dmarc: true dmarc_policy: none - domain: covertrack.ca dnssec: false caa: [] spf: true spf_record: 'v=spf1 include:_spf.google.com include:3917439.spf04.hubspotemail.net ~all' dmarc: true dmarc_policy: none - domain: amazonaws.com dnssec: false caa: [] spf: true dmarc: true dmarc_policy: quarantine findings: note: >- Recorded observations, not assertions of risk. Added api.covertrack.ca and the covertrack.ca registrable domain in this round — the mechanical probe covered only the apis.yml hosts and the first spec's servers. observations: - No HSTS on apollocover.com or api.covertrack.ca; present only on docs.apollocover.com (max-age 31536000). APOLLO's own security page states "we leverage browser protections such as HTTP Strict Transport Protection", which holds for the docs host but not the primary website or the CoverTrack API host. - No CAA records on either apollocover.com or covertrack.ca — any CA may issue for these names. - No DNSSEC on either registrable domain. - DMARC is published on both apollocover.com and covertrack.ca but at 'p=none' — monitoring only, no enforcement against spoofed mail. For a broker that emails policy documents to consumers this is the weakest published control. - TLS 1.3 observed on every host, above the TLS 1.2 minimum APOLLO publishes.