hanze.nl

Checked 21 October 2026, 21:21 UTC · via 8.8.8.8
!Passed with warnings
28 passed 2 warnings 0 failed 5 info

Registration

info

.nl country-code · SURF B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
SURF B.V.
Registered
15 November 1993
Last changed
15 July 2026
Status
active
Registry nameservers
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
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-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
NS in the zone
ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-03.azure-dns.com13.107.236.3 2603:1061:0:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-03.azure-dns.net150.171.21.3 2620:1ec:8ec:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-03.azure-dns.org204.14.183.3 2a01:111:4000:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-03.azure-dns.info208.84.5.3 2620:1ec:bda:700::3AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, 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
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-03.azure-dns.com 13.107.236.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-03.azure-dns.com 2603:1061:0:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 150.171.21.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 2620:1ec:8ec:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 204.14.183.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 2a01:111:4000:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-03.azure-dns.info 208.84.5.3NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-03.azure-dns.info 2620:1ec:bda:700::3NOERROR, 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-03.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 2018021301 · primary ns1-03.azure-dns.com

Found

Primary (MNAME)
ns1-03.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
2018021301
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-03.azure-dns.com (13.107.236.3)2018021301
ns1-03.azure-dns.com (2603:1061:0:700::3)2018021301
ns2-03.azure-dns.net (150.171.21.3)2018021301
ns2-03.azure-dns.net (2620:1ec:8ec:700::3)2018021301
ns3-03.azure-dns.org (204.14.183.3)2018021301
ns3-03.azure-dns.org (2a01:111:4000:700::3)2018021301
ns4-03.azure-dns.info (208.84.5.3)2018021301
ns4-03.azure-dns.info (2620:1ec:bda:700::3)2018021301

Checks

  • ✓ Serial 2018021301 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-03.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Date-based serial #26
    The serial 2018021301 follows the YYYYMMDDnn convention (2018-02-13).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
37683ECDSAP256SHA256 (13)SHA256 E7910D6C21F512B2…yes

DNSKEY in the zone

Key tagRoleAlgorithm
37683KSK (257)ECDSAP256SHA256 (13)
53603ZSK (256)ECDSAP256SHA256 (13)

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 37683 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-20 20:21 UTC and expires at 2026-10-22 22:21 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

warn

24 records at the apex

Found

Read from
13.107.236.3:53
TypeValueTTL
SOAns1-03.azure-dns.com. azuredns-hostmaster.microsoft.com. 2018021301 3600 300 2419200 3003600
NSns1-03.azure-dns.com.172800
NSns2-03.azure-dns.net.172800
NSns3-03.azure-dns.org.172800
NSns4-03.azure-dns.info.172800
A104.47.160.1460
MX10 hanze-nl.w-v1.mx.microsoft.60
TXT"v=spf1 ip4:145.33.5.0/24 include:spf.protection.outlook.com include:spf.interconnect.nl include:a._spf.brightspace.com -all"600
TXT"r1Ja/1ZSoJoXQXF2iftYXXFd1qOnjl62ubrdstJmRp9mSBUQlodb3mpXU9Vi9vT6t/pR8LKOnY9tG2pERKTxYA=="600
TXT"MS=ms18941436"600
TXT"hanze-nl.azurewebsites.net"600
TXT"atlassian-domain-verification=2dwUB6/57CYn5T51HFtLwaClwI4kHCoyiLcWqGTndtxljo5t2sIznzb2K+A3Ghi2"600
TXT"d365mktkey=3bdwuszbj33qb3sx5ini5s9u6"600
TXT"ZOOM_verify_av0qPV7gQ8e6HBV0LJDnaA"600
TXT"ca3-0f9eccb908a04723b7f41e3ddd2862c2"600
TXT"mentimeter-f4503459-d98d-4328-a2be-df91daf82fab"600
TXT"HARICA-vq6zuGo98arJJEjXb6P"600
TXT"meltwater_sso_20260204"600
CAA0 iodef "mailto:postmaster@org.hanze.nl"3600
CAA0 issue "digicert.com"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "harica.gr"3600
CAA0 issue "amazon.com"3600
CAA0 issuewild "harica.gr"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2d; 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, letsencrypt.org, harica.gr, amazon.com.