SurfaceMap › w › watchguard.com

watchguard.com

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

Domain & DNS

warn

26 passed 3 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: ns1.dnsimple-edge.com, ns2.dnsimple-edge.net, ns3.dnsimple-edge.io, ns4.dnsimple-edge.org; only in the zone: ns1.dnsimple.com, ns2.dnsimple.com, ns3.dnsimple.com, ns4.dnsimple.com. ns1.dnsimple-edge.com, ns1.dnsimple.com, ns2.dnsimple-edge.net, ns2.dnsimple.com, ns3.dnsimple-edge.io, ns3.dnsimple.com, ns4.dnsimple-edge.org, ns4.dnsimple.com report NS ns1.dnsimple.com ns2.dnsimple.com ns3.dnsimple.com ns4.dnsimple.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 1h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for watchguard.com ›

Mail

fail

28 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    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.watchguard.com/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.watchguard.com on 127.0.0.53:53: no such host.
    #33
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx-cluster-usa01.hornetsecurity.com, mx-cluster-usa02.hornetsecurity.com, mx-cluster-usa03.hornetsecurity.com, mx-cluster-usa04.hornetsecurity.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (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 watchguard.com ›