SurfaceMap › g › google.nl

google.nl

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

Domain & DNS

error

18 passed 3 warn 0 failed 1 errors

lookups failed for delegation; results are incomplete

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1002974787 on ns1.google.com (216.239.32.10), ns1.google.com (2001:4860:4802:32::a), ns2.google.com (216.239.34.10), ns2.google.com (2001:4860:4802:34::a), ns3.google.com (216.239.36.10), ns3.google.com (2001:4860:4802:36::a); 1003797344 on ns4.google.com (216.239.38.10), ns4.google.com (2001:4860:4802:38::a). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; retry 15m should be shorter than refresh 15m; expire 30m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 30m must be longer than refresh + retry; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 15m, expire 30m, negative TTL 1m.
    #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 google.nl ›

Mail

fail

23 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.google.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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
  • !
    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 google.nl ›