blogspot.nl

Checked 21 October 2026, 20:45 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/blogspot.nl returned HTTP 429

Checks

  • i
    .nl is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/blogspot.nl returned HTTP 429
    #3

Delegation

info

ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
NS in the zone
ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
NameserverAddressesNetwork (AS)Glue
ns1.google.com216.239.32.10 2001:4860:4802:32::aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns2.google.com216.239.34.10 2001:4860:4802:34::aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns3.google.com216.239.36.10 2001:4860:4802:36::aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns4.google.com216.239.38.10 2001:4860:4802:38::aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:4860:4802::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS15169 (GOOGLE - Google LLC, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.google.com 216.239.32.10NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns1.google.com 2001:4860:4802:32::aNOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.google.com 216.239.34.10NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns2.google.com 2001:4860:4802:34::aNOERROR, 24 ms, authoritativenoyes / yesrefused-
ns3.google.com 216.239.36.10NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns3.google.com 2001:4860:4802:36::aNOERROR, 10 ms, authoritativenoyes / yesrefused-
ns4.google.com 216.239.38.10NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4.google.com 2001:4860:4802:38::aNOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1002974787 · primary ns1.google.com

Found

Primary (MNAME)
ns1.google.com
Contact (RNAME)
dns-admin.google.com
Serial
1002974787
Refresh / retry
900 s / 900 s
Expire
1800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.google.com (216.239.32.10)1002974787
ns1.google.com (2001:4860:4802:32::a)1002974787
ns2.google.com (216.239.34.10)1002974787
ns2.google.com (2001:4860:4802:34::a)1002974787
ns3.google.com (216.239.36.10)1002974787
ns3.google.com (2001:4860:4802:36::a)1002974787
ns4.google.com (216.239.38.10)1003797344
ns4.google.com (2001:4860:4802:38::a)1003797344

Checks

  • !
    Serials differ
    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
    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
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.google.com is one of the listed nameservers.
  • ✓ Contact dns-admin@google.com #25
    The SOA RNAME dns-admin.google.com means dns-admin@google.com.
  • ✓ Timestamp serial #26
    The serial 1002974787 is a Unix timestamp (2001-10-13 12:06 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

9 records at the apex

Found

Read from
216.239.32.10:53
TypeValueTTL
SOAns1.google.com. dns-admin.google.com. 1002974787 900 900 1800 6060
NSns4.google.com.345600
NSns1.google.com.345600
NSns3.google.com.345600
NSns2.google.com.345600
A142.251.13.191300
AAAA2a00:1450:4001:c13::bf300
TXT"v=spf1 -all"300
CAA0 issue "pki.goog"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, NS 4d. The NS TTL at the parent is 1h and in the zone 4d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: pki.goog.