SurfaceMap › o › opendns.com

opendns.com

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

Domain & DNS

warn

25 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1792663654 on auth3.opendns.com (208.69.39.2); 1792663669 on auth2.opendns.com (146.112.60.53); 1792663680 on auth2.opendns.com (2a04:e4c0:53::53); 1792663735 on auth1.opendns.com (208.69.39.2); 1792663814 on auth1.opendns.com (2620:119:30::53). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 opendns.com ›

Mail

fail

20 passed 6 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
  • !
    Uses deprecated ptr mechanism
    SPF · The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    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: default (1024 bits), mail (1024 bits), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: default, mail. Remove t=y once DKIM works.
    #24
  • !
    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 opendns.com ›