SurfaceMap › i › iheart.com

iheart.com

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

Domain & DNS

warn

26 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns0121.secondary.cloudflare.com, ns0237.secondary.cloudflare.com; only in the zone: pdns196.ultradns.co.uk. ns0121.secondary.cloudflare.com, ns0237.secondary.cloudflare.com, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org report NS pdns196.ultradns.biz pdns196.ultradns.co.uk pdns196.ultradns.com pdns196.ultradns.info pdns196.ultradns.net pdns196.ultradns.org.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0121.secondary.cloudflare.com: "2026.10.2"; ns0237.secondary.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; retry 1d should be shorter than refresh 15m; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1d must be longer than refresh + retry. Current values: refresh 15m, retry 1d, expire 1d, negative TTL 1d.
    #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 iheart.com ›

Mail

fail

21 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 iheart.com ›