universiteitleiden.nl

Checked 21 October 2026, 21:26 UTC · via 8.8.8.8
iAll checks passed
26 passed 0 warnings 0 failed 9 info

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
9 February 2001
Last changed
19 December 2024
Status
active
Registry nameservers
ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.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.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl
NS in the zone
ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl
NameserverAddressesNetwork (AS)Glue
ns1.surfnet.nl192.87.106.101 2001:610:1:800a:192:87:106:101AS1103 SURFNET-NL - SURF B.V., NL AS1103 SURFNET-NL - SURF B.V., NL192.87.106.101 2001:610:1:800a:192:87:106:101
ns2.surfnet.nl192.87.36.2 2001:610:3:200a:192:87:36:2AS1103 SURFNET-NL - SURF B.V., NL AS1103 SURFNET-NL - SURF B.V., NL192.87.36.2 2001:610:3:200a:192:87:36:2
ns3.surfnet.nl195.169.124.71 2001:610:0:800c:195:169:124:71AS1103 SURFNET-NL - SURF B.V., NL AS1103 SURFNET-NL - SURF B.V., NL195.169.124.71 2001:610:0:800c:195:169:124:71

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.surfnet.nl, ns2.surfnet.nl, ns3.surfnet.nl.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1103 (SURFNET-NL - SURF B.V., NL): 6 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 .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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.surfnet.nl 192.87.106.101NOERROR, 9 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl
ns1.surfnet.nl 2001:610:1:800a:192:87:106:101NOERROR, 9 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl
ns2.surfnet.nl 192.87.36.2NOERROR, 12 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl
ns2.surfnet.nl 2001:610:3:200a:192:87:36:2NOERROR, 12 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl
ns3.surfnet.nl 195.169.124.71NOERROR, 10 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl
ns3.surfnet.nl 2001:610:0:800c:195:169:124:71NOERROR, 10 ms, authoritativenoyes / yesrefusedThis is a SURFnet nameserver - dns-beheer@surfnet.nl

Checks

  • ✓ All respond #14
    All 6 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.surfnet.nl: "This is a SURFnet nameserver - dns-beheer@surfnet.nl"; ns2.surfnet.nl: "This is a SURFnet nameserver - dns-beheer@surfnet.nl"; ns3.surfnet.nl: "This is a SURFnet nameserver - dns-beheer@surfnet.nl".
    #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

info

serial 2005229430 · primary arachne.leidenuniv.nl

Found

Primary (MNAME)
arachne.leidenuniv.nl
Contact (RNAME)
postmaster.leidenuniv.nl
Serial
2005229430
Refresh / retry
10800 s / 1080 s
Expire
2592000 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.surfnet.nl (192.87.106.101)2005229430
ns1.surfnet.nl (2001:610:1:800a:192:87:106:101)2005229430
ns2.surfnet.nl (192.87.36.2)2005229430
ns2.surfnet.nl (2001:610:3:200a:192:87:36:2)2005229430
ns3.surfnet.nl (195.169.124.71)2005229430
ns3.surfnet.nl (2001:610:0:800c:195:169:124:71)2005229430

Checks

  • ✓ Serial 2005229430 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 18m, expire 30d, negative TTL 2h.
  • i
    Hidden master
    The primary nameserver arachne.leidenuniv.nl is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact postmaster@leidenuniv.nl #25
    The SOA RNAME postmaster.leidenuniv.nl means postmaster@leidenuniv.nl.
  • ✓ Timestamp serial #26
    The serial 2005229430 is a Unix timestamp (2033-07-17 16:10 UTC).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
25 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
56950RSASHA256 (8)SHA256 F5E07F2F335DE8F4…yes

DNSKEY in the zone

Key tagRoleAlgorithm
62916ZSK (256)RSASHA256 (8)
15276ZSK (256)RSASHA256 (8)
56950KSK (257)RSASHA256 (8)
53133ZSK (256)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 56950 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 97h0m0s and created on demand; the current one was made at 2026-10-21 11:01 UTC and expires at 2026-10-25 11:48 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

13 records at the apex

Found

Read from
192.87.106.101:53
TypeValueTTL
SOAarachne.leidenuniv.nl. postmaster.leidenuniv.nl. 2005229430 10800 1080 2592000 720028800
NSns1.surfnet.nl.28800
NSns3.surfnet.nl.28800
NSns2.surfnet.nl.28800
A132.229.29.70300
MX0 universiteitleiden-nl.k-v1.mx.microsoft.28800
TXT"facebook-domain-verification=i7dmrn8v3p50vcpvbklhh2imk6ghos"300
TXT"google-site-verification=lDW7ZJy_kHGpzCFC7kFYyj96huHupUonb0ytLJHIAdE"300
TXT"MS=ms50955834"300
TXT"d365mktkey=eQ8nBdw5IxUNMyrAGp3jEuh3kIB13FHcI2bBXuza58sx"300
TXT"v=spf1 include:_spf.xqueue.com ip4:132.229.92.91 ip4:132.229.92.94 ~all"300
TXT"MHlhvquCdwRJRYkTS56GSEY+DQj+UiYMZF/IOe4KopQIx9o1tQw9R75rdXDd3wu3ipiXoQU024B59OvW9jAisw=="300
TXT"d365mktkey=v3LRuP2RS80N3tx4BHxZSUhezhKNEeV5sxntlqJVMBMx"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 8h, NS 8h. The NS TTL at the parent is 1h and in the zone 8h; 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.
  • 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