gld.nl

Checked 21 October 2026, 21:20 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 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/gld.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/gld.nl returned HTTP 429
    #3

Delegation

warn

ns1.geldersnetwerk.nl, ns2.geldersnetwerk.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.geldersnetwerk.nl, ns2.geldersnetwerk.nl
NS in the zone
ns1.geldersnetwerk.nl, ns2.geldersnetwerk.nl
NameserverAddressesNetwork (AS)Glue
ns1.geldersnetwerk.nl85.10.128.132AS20857 TRANSIP-AS - Signet B.V., NL85.10.128.132
ns2.geldersnetwerk.nl188.205.147.22AS1136 KPN - KPN B.V., NL188.205.147.22

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.geldersnetwerk.nl, ns2.geldersnetwerk.nl.
    #6
  • ✓ 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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1136 (KPN - KPN B.V., NL): 1 address; AS20857 (TRANSIP-AS - Signet B.V., NL): 1 address.
  • i
    All nameserver names under .nl
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.geldersnetwerk.nl 85.10.128.132NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns2.geldersnetwerk.nl 188.205.147.22NOERROR, 15 ms, authoritativenoyes / yesrefused9.16.3

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.geldersnetwerk.nl: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; ns2.geldersnetwerk.nl: "9.16.3". Hide or replace the version string.
    #17
  • ✓ 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

pass

serial 2026102104 · primary ns1.geldersnetwerk.nl

Found

Primary (MNAME)
ns1.geldersnetwerk.nl
Contact (RNAME)
root.geldersnetwerk.nl
Serial
2026102104
Refresh / retry
14400 s / 7200 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.geldersnetwerk.nl (85.10.128.132)2026102104
ns2.geldersnetwerk.nl (188.205.147.22)2026102104

Checks

  • ✓ Serial 2026102104 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 1000h, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.geldersnetwerk.nl is one of the listed nameservers.
  • ✓ Contact root@geldersnetwerk.nl #25
    The SOA RNAME root.geldersnetwerk.nl means root@geldersnetwerk.nl.
  • ✓ Date-based serial #26
    The serial 2026102104 follows the YYYYMMDDnn convention (2026-10-21).

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

warn

12 records at the apex

Found

Read from
85.10.128.132:53
TypeValueTTL
SOAns1.geldersnetwerk.nl. root.geldersnetwerk.nl. 2026102104 14400 7200 3600000 8640060
NSns2.geldersnetwerk.nl.60
NSns1.geldersnetwerk.nl.60
A85.10.128.13260
MX8 gld-nl.mail.protection.outlook.com.60
TXT"v=spf1 ip4:217.19.238.48/29 ip4:145.58.26.176/28 ip4:145.58.30.176/28 ip4:85.10.128.132 ip4:188.205.147.66 ip4:188.205.147.44 " "ip4:188.205.147.45 ip4:188.205.147.98 include:spf.protection.outlook.com include:_spf.transip.email include:pigeon1.gomsp.nl " "include:spf.tribecrm.nl ~all"60
TXT"apple-domain-verification=JTZgtMjqCwAG0zcW"60
TXT"facebook-domain-verification=fi2jlzam09ln4f8fcwdgfut1e23d67"60
TXT"openai-domain-verification=dv-DdHaUr21hppsCtngKVqisIUg"60
TXT"linkedin-site-verification=019f020f-0e0e-414e-83c3-08cabe4b4d10"60
TXT"google-site-verification=JTeqeEnnrtawPD1Z_Vy2sMwwW538L2NgfAq06TI_oAo"60
TXT"MS=ms40927524"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35