Domain report: noloc.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

ns0.nl, ns11.net, ns5.be

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns0.nl, ns11.net, ns5.be
NS in the zone: ns0.nl, ns11.net, ns5.be

Nameserver	Addresses	Network (AS)	Glue
ns0.nl	195.135.195.95 2a01:7c8:dddd:195::95	AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL	195.135.195.95 2a01:7c8:dddd:195::95
ns11.net	37.97.199.95 2a01:7c8:f:c1f::95	AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL	-
ns5.be	195.8.195.95 2a01:7c8:7000:195::95	AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL	-

Checks

✓ 3 nameservers #6

Delegated to ns0.nl, ns11.net, ns5.be.
✓ 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 (AS20857 (TRANSIP-AS - Signet 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
✓ Nameserver names under 3 TLDs #12

Nameserver names use the TLDs .be, .net, .nl.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns0.nl 195.135.195.95	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns0.nl 2a01:7c8:dddd:195::95	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns11.net 37.97.199.95	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-
ns11.net 2a01:7c8:f:c1f::95	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-
ns5.be 195.8.195.95	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns5.be 2a01:7c8:7000:195::95	NOERROR, 13 ms, authoritative	no	yes / yes	refused	-

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.
✓ 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 2026091502 · primary ns0.nl

Found

Primary (MNAME): ns0.nl
Contact (RNAME): hostmaster.ns0.nl
Serial: 2026091502
Refresh / retry: 86400 s / 1800 s
Expire: 2419200 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
ns0.nl (195.135.195.95)	2026091502
ns0.nl (2a01:7c8:dddd:195::95)	2026091502
ns11.net (37.97.199.95)	2026091502
ns11.net (2a01:7c8:f:c1f::95)	2026091502
ns5.be (195.8.195.95)	2026091502
ns5.be (2a01:7c8:7000:195::95)	2026091502

Checks

✓ Serial 2026091502 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1d, retry 30m, expire 28d, negative TTL 5m.
✓ Primary is a public nameserver #24

The primary nameserver ns0.nl is one of the listed nameservers.
✓ Contact hostmaster@ns0.nl #25

The SOA RNAME hostmaster.ns0.nl means hostmaster@ns0.nl.
✓ Date-based serial #26

The serial 2026091502 follows the YYYYMMDDnn convention (2026-09-15).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 8-byte salt
Signatures valid until: 5 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
21162	ECDSAP256SHA256 (13)	SHA256 E4D5F29EFDCCD8B1…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
21162	KSK (257)	ECDSAP256SHA256 (13)
19274	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 21162 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13).
✓ Signatures valid until 2026-11-05 #30

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 0 iterations and a 8-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

info

11 records at the apex

Found

Read from: 195.135.195.95:53

Type	Value	TTL
SOA	ns0.nl. hostmaster.ns0.nl. 2026091502 86400 1800 2419200 300	3600
NS	ns0.nl.	86400
NS	ns11.net.	86400
NS	ns5.be.	86400
A	213.193.247.32	300
MX	0 noloc-nl.mail.protection.outlook.com.	86400
TXT	"procurios-site-verification=bXMnoLKr3j3Qfo1lNJKl"	3600
TXT	"google-site-verification=0Q3aYYZYu1LQIAHRwD0GrESCNO_dcqLF36exxZ59pNg"	3600
TXT	"MS=ms39298206"	3600
TXT	"v=spf1 include:_spf.mos-net.nl include:spf.protection.outlook.com include:amazonses.com include:_spf.google.com include:procurios.cloud -all"	3600
TXT	"spf2.0/pra,mfrom include:_spf.mos-net.nl include:spf.kingsquare.nl include:communibase.nl include:_spf.google.com ~all"	3600

Checks

✓ TTLs within range #32

TTLs: A 5m, 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.
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
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