rotterdam.nl

Checked 21 October 2026, 21:25 UTC · via 8.8.8.8
✗Problems found
29 passed 1 warning 1 failed 4 info

Registration

info

.nl country-code · Gemeente Rotterdam

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Gemeente Rotterdam
Registered
8 March 1995
Last changed
25 June 2026
Status
active
Registry nameservers
ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl
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

ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl
NS in the zone
ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl
NameserverAddressesNetwork (AS)Glue
ns1.rotterdam.nl193.176.221.253 2a07:3500:1061:1100::1AS208240 GMT-ROTTERDAM - Gemeente Rotterdam, NL AS208240 GMT-ROTTERDAM - Gemeente Rotterdam, NL193.176.221.253 2a07:3500:1061:1100::1
ns2.rotterdam.nl193.176.221.254 2a07:3500:1061:1100::2AS208240 GMT-ROTTERDAM - Gemeente Rotterdam, NL AS208240 GMT-ROTTERDAM - Gemeente Rotterdam, NL193.176.221.254 2a07:3500:1061:1100::2
ns3.rotterdam.nl31.160.192.198 2a02:a400:b3::f001:1003AS1136 KPN - KPN B.V., NL AS1136 KPN - KPN B.V., NL31.160.192.198 2a02:a400:b3::f001:1003

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.rotterdam.nl, ns2.rotterdam.nl, ns3.rotterdam.nl.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1136 (KPN - KPN B.V., NL): 2 addresses; AS208240 (GMT-ROTTERDAM - Gemeente Rotterdam, NL): 4 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.rotterdam.nl 193.176.221.253NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns1.rotterdam.nl 2a07:3500:1061:1100::1NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns2.rotterdam.nl 193.176.221.254NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.rotterdam.nl 2a07:3500:1061:1100::2NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.rotterdam.nl 31.160.192.198NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.rotterdam.nl 2a02:a400:b3::f001:1003no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3.rotterdam.nl (2a02:a400:b3::f001:1003): read udp [2a01:4f8:1c1c:eebf::1]:52910->[2a02:a400:b3::f001:1003]:53: i/o timeout.
    #14
  • ✓ 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

pass

serial 2017354671 · primary ns1.rotterdam.nl

Found

Primary (MNAME)
ns1.rotterdam.nl
Contact (RNAME)
hostmaster.rotterdam.nl
Serial
2017354671
Refresh / retry
86400 s / 7200 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.rotterdam.nl (193.176.221.253)2017354671
ns1.rotterdam.nl (2a07:3500:1061:1100::1)2017354671
ns2.rotterdam.nl (193.176.221.254)2017354671
ns2.rotterdam.nl (2a07:3500:1061:1100::2)2017354671
ns3.rotterdam.nl (31.160.192.198)2017354671

Checks

  • ✓ Serial 2017354671 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.rotterdam.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@rotterdam.nl #25
    The SOA RNAME hostmaster.rotterdam.nl means hostmaster@rotterdam.nl.
  • ✓ Timestamp serial #26
    The serial 2017354671 is a Unix timestamp (2033-12-05 00:17 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
45385RSASHA256 (8)SHA256 ABD10C83490C63FF…yes

DNSKEY in the zone

Key tagRoleAlgorithm
39055KSK (257)RSASHA256 (8)
20233ZSK (256)RSASHA256 (8)
9000ZSK (256)RSASHA256 (8)
45385KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 45385 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 96h0m0s and created on demand; the current one was made at 2026-10-20 21:56 UTC and expires at 2026-10-24 22:04 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 10 iterations and a 14-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

pass

32 records at the apex

Found

Read from
193.176.221.253:53
TypeValueTTL
SOAns1.rotterdam.nl. hostmaster.rotterdam.nl. 2017354671 86400 7200 604800 360086400
NSns2.rotterdam.nl.86400
NSns3.rotterdam.nl.86400
NSns1.rotterdam.nl.86400
A185.135.13.3086400
AAAA2a06:efc0:0:103::2586400
MX10 rotterdam-nl.mail.protection.outlook.com.86400
TXT"atlassian-domain-verification=LaySuPFSx0MaXgcb7GCue1FJhA8B8C063iTasxOVsfzg5ch6ysimsXzGUa4OKsBE"86400
TXT"autodesk-domain-verification=GZbID3yMrJrPKEbqato_"86400
TXT"uQPPjf5RuUzVehTy5KePTFPlDk10o6BvUXCaamkoaiKz2qmmhceh9NT0bPXGkFnp"86400
TXT"ms-domain-verification=d265c2fb-abac-4a45-a36d-d3c418197487"86400
TXT"f2x6l886tc"86400
TXT"cisco-ci-domain-verification=3643c61405f8ad203572941485cf2045ae251882028c6a75945150b005a379f9"86400
TXT"DomainVerification=2MPA4FHVL3FK9DSK6WODLLU8CP7MAAABG2OX9BH68BMVAHAPCDLMYM0U06M94NKN"86400
TXT"brevo-code:91f92b58940284a611ef8613c4046b61"86400
TXT"4q1jkErlnTVN56fjkdmbFwv537wUjxjxLmOMYkf3a7Ciy2N6lXWwsGu5wweDcKS0"86400
TXT"v=spf1 redirect=_policy1.rotterdam.nl"86400
TXT"citrix.mobile.ads.otp=hts1nfkncgzwp9zuv3yb"86400
TXT"aanmelder.nl-user=87363"86400
TXT"kDKfU9c1hcKaQgqwFPAxmkqM9BVCKG2FJ9ftbKEY2sa0le6exoBM/lpJRjs0E/8uX7kFMMr+NUUkuJJfBJDUEg=="86400
TXT"MS=ms81193378"86400
TXT"adobe-idp-site-verification=4c455aa4754ad3dbc29112adade0f5cde8960ff1e2a96e432b85307501bb363a"86400
TXT"apple-domain-verification=sZSEYvG8acsw3Kdq"86400
TXT"miro-verification=3dfab1861888add724f810dbc13d49f242b6b524"86400
TXT"Dynatrace-site-verification=1b8d2f27-38fe-4e24-a588-a0a66ddb89ea__2gul6j9ee7j9ejgl4pc8bgfsjb"86400
TXT"WyPdDyN4yX0pyTVg0RIYzXqkWW4GiRFtPQnishT5nKNyAZTPiSxncIaTvSTVqsxo"86400
TXT"Dynatrace-site-verification=3e284fa8-09df-4ae6-a93b-4663eb3e90b8__3m4a7u7ikfs55o46rv9ugkhi39"86400
CAA0 issue "sectigo.com"21600
CAA0 issue "pki.goog"21600
CAA0 issue "letsencrypt.org"21600
CAA0 issue "amazon.com"21600
CAA0 issue "certsign.ro"21600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: sectigo.com, pki.goog, letsencrypt.org, amazon.com, certsign.ro.