SurfaceMap › o › openculture.com

openculture.com

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

Domain & DNS

warn

23 passed 2 warn 0 failed

Areas

iRegistration iDelegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 51h46m40s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 1h, expire 14d, negative TTL 51h46m40s.
    #23
  • !
    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

Recent checks

!

Full report

Domain & DNS report for openculture.com ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    4 of 10 DNS lookups, with problems
    SPF · SPF record needs 4 DNS lookups (limit is 10). Problems found: include loop detected at openculture.com.
    #2
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for openculture.com ›