gelderlander.nl

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

Registration

info

.nl country-code · Registrar.eu

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Registrar.eu
Registered
17 April 1996
Last changed
1 October 2026
Status
active
Registry nameservers
eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net
RDAP server
https://rdap.sidn.nl/

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
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net
NS in the zone
eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net
NameserverAddressesNetwork (AS)Glue
eur2.akam.net95.100.173.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur5.akam.net23.74.25.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur6.akam.net2.22.230.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-125.akam.net193.108.91.125 2600:1401:2::7dAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-25.akam.net193.108.91.25 2600:1401:2::19AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usc2.akam.net184.26.160.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use2.akam.net96.7.49.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use5.akam.net2.16.40.64 2600:1403:a::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 8 nameservers #6
    Delegated to eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-125.akam.net, ns1-25.akam.net, usc2.akam.net, use2.akam.net, use5.akam.net.
  • ✓ 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 7 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 2 addresses; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 9 addresses.
  • i
    All nameserver names under .net
    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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: eur2.akam.net, eur5.akam.net, eur6.akam.net, usc2.akam.net, use2.akam.net.
    #13

Nameservers

warn

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
eur2.akam.net 95.100.173.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
eur5.akam.net 23.74.25.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
eur6.akam.net 2.22.230.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
ns1-125.akam.net 193.108.91.125NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
ns1-125.akam.net 2600:1401:2::7dNOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
ns1-25.akam.net 193.108.91.25NOERROR, 3 ms, authoritativenoyes / yesrefused41824.10
ns1-25.akam.net 2600:1401:2::19NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
usc2.akam.net 184.26.160.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.33
use2.akam.net 96.7.49.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.8
use5.akam.net 2.16.40.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
use5.akam.net 2600:1403:a::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.30

Checks

  • ✓ All respond #14
    All 11 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: eur2.akam.net: "48878.27"; eur5.akam.net: "48878.26"; eur6.akam.net: "41824.11"; ns1-125.akam.net: "41824.10"; ns1-125.akam.net: "41824.5"; ns1-25.akam.net: "41824.10"; usc2.akam.net: "48878.33"; use2.akam.net: "41824.8"; use5.akam.net: "48878.26"; use5.akam.net: "48878.30". 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

warn

serial 329 · primary ns1-25.akam.net

Found

Primary (MNAME)
ns1-25.akam.net
Contact (RNAME)
hostmaster.persgroep.be
Serial
329
Refresh / retry
900 s / 600 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
eur2.akam.net (95.100.173.64)329
eur5.akam.net (23.74.25.64)329
eur6.akam.net (2.22.230.64)329
ns1-125.akam.net (193.108.91.125)329
ns1-125.akam.net (2600:1401:2::7d)329
ns1-25.akam.net (193.108.91.25)329
ns1-25.akam.net (2600:1401:2::19)329
usc2.akam.net (184.26.160.64)329
use2.akam.net (96.7.49.64)329
use5.akam.net (2.16.40.64)329
use5.akam.net (2600:1403:a::40)329

Checks

  • ✓ Serial 329 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 14d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-25.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@persgroep.be #25
    The SOA RNAME hostmaster.persgroep.be means hostmaster@persgroep.be.
  • ✓ Counter serial #26
    The serial 329 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
24 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
50461ECDSAP256SHA256 (13)SHA256 C2632EE280C45130…NO
42411ECDSAP256SHA256 (13)SHA256 654270A50DC1A4E3…yes

DNSKEY in the zone

Key tagRoleAlgorithm
42411KSK (257)ECDSAP256SHA256 (13)
64432ZSK (256)ECDSAP256SHA256 (13)
65185ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • i
    Unused DS records
    These DS records match no key in the zone: key tag 50461 (SHA256). That is normal during a key rollover; otherwise remove them.
    #28
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 73h0m0s and created on demand; the current one was made at 2026-10-21 13:02 UTC and expires at 2026-10-24 14:02 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

27 records at the apex

Found

Read from
95.100.173.64:53
TypeValueTTL
SOAns1-25.akam.net. hostmaster.persgroep.be. 329 900 600 1209600 300900
NSeur5.akam.net.900
NSusc2.akam.net.900
NSuse2.akam.net.900
NSns1-25.akam.net.900
NSeur2.akam.net.900
NSns1-125.akam.net.900
NSeur6.akam.net.900
NSuse5.akam.net.900
A23.55.163.17420
MX1 aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX10 alt4.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
TXT"klaviyo-site-verification=XWU6yJ"900
TXT"MS=ms69084723"900
TXT"google-site-verification=J5BWicrkxnQy7iMadTV3u6hVLXksoC_e03WIFGXvD3g"900
TXT"facebook-domain-verification=1jjxpsd2m2fsfxgfzm7y02qw6xa1v2"900
TXT"atlassian-domain-verification=gqfC576h6pKDntEMQCdrUMXTtOD2vfhKvXTSXAIxiT3BSdIBLzbPWwOkt0jwiITX"900
TXT"persgroep-ecommerce-prod.azurewebsites.net"900
TXT"facebook-domain-verification=poaj2j8ddsgbo0m72yurd6w618rkd2"900
TXT"v=spf1 ip4:145.60.8.129 include:_spf.google.com include:et._spf.pardot.com include:_spf.relay.mailprotect.be include:spf.flowmailer.net include:spf.mailjet.com include:_spf1.gelderlander.nl ~all"900
TXT"google-site-verification=P8JUGrb7JDI0OCA8ro-n-_KRNXCNnJ9n752-3Q186o0"900
TXT"google-site-verification=MxotKf5xvR4NXplZJ8irf6hLmUPrnvkPQ_MfV1raKaU"900
TXT"/mW4BwPiH823wtRlmoPnY8R8jBg/iO/yI2B0rypGO9/8ZLExRcAuY8gDwxNMe96GsAt70SmypQchZgB4aO1iqQ=="900
TXT"google-site-verification=d0b7kWQiEc0tZKY_UTLGFL9zHMNfkB_vIK29pfIhTAQ"900

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 15m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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