Datafy · Domain Security

Datafy Domain Security

Domain security

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

CompanyAnalyticsAdvertisingLocation IntelligenceAttributionTourismMarketingVisitation DataDestination MarketingMeasurement

Transport & Host Security

www.datafy.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 6 10:18:29 2026 GMT
api.datafy.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 6 10:18:29 2026 GMT

Domain (DNS/Email) Security

datafy.com
DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: none

Source

Domain Security

datafy-domain-security.yml Raw ↑ 
generated: '2026-08-12'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.datafy.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  6 10:18:29 2026 GMT
  hsts: true
  hsts_max_age: 63072000
- host: api.datafy.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  6 10:18:29 2026 GMT
  hsts: true
  hsts_max_age: 15552000
  hsts_include_subdomains: true
  note: >-
    Corrected by hand on 2026-08-12 from a direct probe. The automated pass
    recorded hsts: null because every request to this host returns HTTP 500
    (UnauthorizedError) and the header was not read off a non-2xx response;
    `curl -I https://api.datafy.com/` does return
    `strict-transport-security: max-age=15552000; includeSubDomains`. The host
    also returns a full Helmet-style header set (CSP, X-Content-Type-Options,
    X-Frame-Options, Referrer-Policy, COOP/CORP) behind Cloudflare, with
    Access-Control-Allow-Origin: *.
domains:
- domain: datafy.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: reject