SurfaceMap › r › registerguard.com

registerguard.com

Checked 2026-10-22 10:30 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

23 passed 3 warn 0 failed 1 errors

lookups failed for zone-ns; results are incomplete

Areas

iRegistration !Delegation iNameservers iSOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, ns01.gannett-dns.com, ns02.gannett-dns.com, ns03.gannett-dns.com, ns04.gannett-dns.com report NS dns1.p06.nsone.net dns2.p06.nsone.net dns3.p06.nsone.net dns4.p06.nsone.net ns01.gannett-dns.com ns02.gannett-dns.com ns03.gannett-dns.com ns04.gannett-dns.com.
    #7
  • !
    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: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 15m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for registerguard.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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits), 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 registerguard.com ›