Domain report: woonzorg.nl

Registration

info

.nl country-code

Found

TLD: .nl (country-code)
ICANN policies apply: no

Lookup error: https://rdap.sidn.nl/domain/woonzorg.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/woonzorg.nl returned HTTP 429

#3

Delegation

info

ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info
NS in the zone: ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.azure-dns.info

Nameserver	Addresses	Network (AS)	Glue
ns1-08.azure-dns.com	13.107.236.8 2603:1061:0:700::8	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns2-08.azure-dns.net	150.171.21.8 2620:1ec:8ec:700::8	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns3-08.azure-dns.org	204.14.183.8 2a01:111:4000:700::8	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns4-08.azure-dns.info	208.84.5.8 2620:1ec:bda:700::8	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-

Checks

✓ 4 nameservers #6

Delegated to ns1-08.azure-dns.com, ns2-08.azure-dns.net, ns3-08.azure-dns.org, ns4-08.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

pass

8 of 8 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1-08.azure-dns.com 13.107.236.8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns1-08.azure-dns.com 2603:1061:0:700::8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns2-08.azure-dns.net 150.171.21.8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns2-08.azure-dns.net 2620:1ec:8ec:700::8	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns3-08.azure-dns.org 204.14.183.8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns3-08.azure-dns.org 2a01:111:4000:700::8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns4-08.azure-dns.info 208.84.5.8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns4-08.azure-dns.info 2620:1ec:bda:700::8	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-

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.
✓ 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 1 · primary ns1-08.azure-dns.com

Found

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

Serial per nameserver

Nameserver	Serial
ns1-08.azure-dns.com (13.107.236.8)	1
ns1-08.azure-dns.com (2603:1061:0:700::8)	1
ns2-08.azure-dns.net (150.171.21.8)	1
ns2-08.azure-dns.net (2620:1ec:8ec:700::8)	1
ns3-08.azure-dns.org (204.14.183.8)	1
ns3-08.azure-dns.org (2a01:111:4000:700::8)	1
ns4-08.azure-dns.info (208.84.5.8)	1
ns4-08.azure-dns.info (2620:1ec:bda:700::8)	1

Checks

✓ Serial 1 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-08.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.
✓ Counter serial #26

The serial 1 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
23641	ECDSAP256SHA256 (13)	SHA256 DCD509E4811E7C54…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
23641	KSK (257)	ECDSAP256SHA256 (13)
34003	ZSK (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 23641 (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-21 16:20 UTC and expires at 2026-10-23 18:20 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

12 records at the apex

Found

Read from: 13.107.236.8:53

Type	Value	TTL
SOA	ns1-08.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300	3600
NS	ns1-08.azure-dns.com.	120
NS	ns2-08.azure-dns.net.	120
NS	ns3-08.azure-dns.org.	120
NS	ns4-08.azure-dns.info.	120
A	150.171.109.107	1
MX	10 woonzorg-nl.e-v1.mx.microsoft.	3600
TXT	"KEfaeosN0cEV7CiaE+tMOOyM/+DLxJojJKxmPQG6TtAo2iwuvwDuOjmSZgtc65nd5xkjxmy/iVVMs1KLDaDrlA=="	1
TXT	"MS=ms49944007"	1
TXT	"v=spf1 include:spf.protection.outlook.com include:_u.woonzorg.nl._spf.dmarcli.com -all"	1
TXT	"9f170772-5a50-428b-b806-4a1c0ae774d3"	1
TXT	"hWwgoQBfdU4vHBQVSCpvnrJsfv5Lmuuq"	1

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1s), NS (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2m; 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