Domain report: loods5.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

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

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1-33.azure-dns.com	150.171.10.33 2603:1061:0:10::21	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns2-33.azure-dns.net	150.171.16.33 2620:1ec:8ec:10::21	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns3-33.azure-dns.org	13.107.222.33 2a01:111:4000:10::21	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns4-33.azure-dns.info	13.107.206.33 2620:1ec:bda:10::21	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-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.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

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1-33.azure-dns.com 150.171.10.33	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns1-33.azure-dns.com 2603:1061:0:10::21	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns2-33.azure-dns.net 150.171.16.33	NOERROR, 4 ms, authoritative	no	yes / yes	refused	Knot DNS 3.1.2.1770717641.d6b376aff
ns2-33.azure-dns.net 2620:1ec:8ec:10::21	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns3-33.azure-dns.org 13.107.222.33	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns3-33.azure-dns.org 2a01:111:4000:10::21	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-
ns4-33.azure-dns.info 13.107.206.33	NOERROR, 4 ms, authoritative	no	yes / yes	refused	Knot DNS 3.1.2.1770717641.d6b376aff
ns4-33.azure-dns.info 2620:1ec:bda:10::21	NOERROR, 5 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2-33.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-33.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 1 · primary ns1-33.azure-dns.com

Found

Primary (MNAME): ns1-33.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-33.azure-dns.com (150.171.10.33)	1
ns1-33.azure-dns.com (2603:1061:0:10::21)	1
ns2-33.azure-dns.net (150.171.16.33)	1
ns2-33.azure-dns.net (2620:1ec:8ec:10::21)	1
ns3-33.azure-dns.org (13.107.222.33)	1
ns3-33.azure-dns.org (2a01:111:4000:10::21)	1
ns4-33.azure-dns.info (13.107.206.33)	1
ns4-33.azure-dns.info (2620:1ec:bda:10::21)	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-33.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

pass

Signed, DS published at parent

Found

Validated by resolver: yes
Signatures valid until: 23 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
25817	ECDSAP256SHA256 (13)	SHA256 1141653F2841B546…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
25817	KSK (257)	ECDSAP256SHA256 (13)
10030	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 25817 (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 13:11 UTC and expires at 2026-10-23 15:11 UTC.

Records

info

18 records at the apex

Found

Read from: 150.171.10.33:53

Type	Value	TTL
SOA	ns1-33.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300	3600
NS	ns1-33.azure-dns.com.	172800
NS	ns2-33.azure-dns.net.	172800
NS	ns3-33.azure-dns.org.	172800
NS	ns4-33.azure-dns.info.	172800
A	13.107.253.67	3600
MX	0 loods5-nl.mail.protection.outlook.com.	600
TXT	"apple-domain-verification=Bh9sXHg8hjMfntVN"	600
TXT	"facebook-domain-verification=l80rwn3ftqy4sbq8dmgkljg8gyab5o"	600
TXT	"google-site-verification=AqasfdP1yjxGrfeCGN9MJlUarZA44eUWb9YCG_NMTQg"	600
TXT	"google-site-verification=n-T9zI6bVRTucu379mWkuwjPLVTxd8WLXFGmPvXEgJs"	600
TXT	"google-site-verification=ZlXx7ULo0L0wtyMj4es8lt6G5N86nfjwGDllQl32oZI"	600
TXT	"MS=ms84848256"	600
TXT	"v=spf1 a mx include:amazonses.com include:servers.mcsv.net include:spf.mailjet.com include:spf.protection.outlook.com include:spf.eu.exclaimer.NET include:spf.afas.online ip4:85.12.31.55 ip4:82.94.210.74 ip4:95.211.19.101 ip4:85.17.166.135 ip4:185.46.182." "1 ip4:185.46.182.200/29 ip4:185.46.182.208/31 ip4:20.82.87.96/28 ip4:104.40.229.156 ip4:52.169.0.179 ip4:20.50.220.144/28 ip4:40.127.253.48/28 -all"	600
CAA	0 issuewild "sectigo.com"	3600
CAA	0 issuewild "digicert.com"	3600
CAA	0 iodef "mailto:security@loods5.nl"	3600
CAA	0 issuewild "letsencrypt.org"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, MX 10m, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
✓ CAA restricts issuance #35

Certificates may be issued by: sectigo.com, digicert.com, letsencrypt.org.