SurfaceMap › s › storyblok.com

storyblok.com

Checked 2026-10-22 10:52 UTC · first added 2026-10-21
✗Problems found Score 65 of 100

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for storyblok.com ›

Mail

fail

26 passed 3 warn 2 failed

Areas

✗SPF ✓DMARC !DKIM !DNSSEC ✓MX ✗TLS iBIMI

Problems

  • ✗
    12 DNS lookups, over the limit of 10
    SPF · SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    Policy not reachable
    TLS · The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.storyblok.com/.well-known/mta-sts.txt": read tcp 46.225.38.91:43288->3.5.120.91:443: read: connection reset by peer.
    #33
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), google (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for storyblok.com ›