Domain report: ntg.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

ns.aanhet.net, ns4.aanhet.net

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns.aanhet.net, ns4.aanhet.net
NS in the zone: ns.aanhet.net, ns4.aanhet.net

Nameserver	Addresses	Network (AS)	Glue
ns.aanhet.net	5.39.185.225	AS58291 ColoCenter - ColoCenter b.v., NL	-
ns4.aanhet.net	85.10.129.212 2a01:7c8:bb0a:598:5054:ff:feab:f88f	AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.aanhet.net, ns4.aanhet.net.

#6
✓ 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 2 IPv4 /24s and 1 IPv6 /48.
✓ 2 autonomous systems #11

The nameservers are spread over: AS20857 (TRANSIP-AS - Signet B.V., NL): 2 addresses; AS58291 (ColoCenter - ColoCenter b.v., NL): 1 address.
i

All nameserver names under .net

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
i

Partly IPv6

These nameservers have no IPv6 address: ns.aanhet.net.

#13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns.aanhet.net 5.39.185.225	NOERROR, 11 ms, authoritative	no	yes / yes	refused	9.18.39-0ubuntu0.24.04.8-Ubuntu
ns4.aanhet.net 85.10.129.212	NOERROR, 11 ms, authoritative	no	yes / yes	refused	unknown
ns4.aanhet.net 2a01:7c8:bb0a:598:5054:ff:feab:f88f	NOERROR, 11 ms, authoritative	no	yes / yes	refused	unknown

Checks

✓ All respond #14

All 3 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: ns.aanhet.net: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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 2026101802 · primary ns4.aanhet.net

Found

Primary (MNAME): ns4.aanhet.net
Contact (RNAME): root.ns4.aanhet.net
Serial: 2026101802
Refresh / retry: 7200 s / 540 s
Expire: 1209600 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns.aanhet.net (5.39.185.225)	2026101802
ns4.aanhet.net (85.10.129.212)	2026101802
ns4.aanhet.net (2a01:7c8:bb0a:598:5054:ff:feab:f88f)	2026101802

Checks

✓ Serial 2026101802 everywhere #22

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

SOA refresh 2h, retry 9m, expire 14d, negative TTL 1h.
✓ Primary is a public nameserver #24

The primary nameserver ns4.aanhet.net is one of the listed nameservers.
✓ Contact root@ns4.aanhet.net #25

The SOA RNAME root.ns4.aanhet.net means root@ns4.aanhet.net.
✓ Date-based serial #26

The serial 2026101802 follows the YYYYMMDDnn convention (2026-10-18).

DNSSEC

pass

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
24626	ECDSAP256SHA256 (13)	SHA256 51F72C62DA91C013…	yes

DNSKEY in the zone

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

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

The earliest DNSKEY/SOA signature expires at 2026-11-03 02:31 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

7 records at the apex

Found

Read from: 5.39.185.225:53

Type	Value	TTL
SOA	ns4.aanhet.net. root.ns4.aanhet.net. 2026101802 7200 540 1209600 3600	3600
NS	ns.aanhet.net.	3600
NS	ns4.aanhet.net.	3600
A	5.39.185.202	3600
AAAA	2a02:f640::20c:29ff:fef5:418	3600
MX	10 mail.ntg.nl.	3600
TXT	"v=spf1 mx a ip4:136.144.247.29 ip4:5.39.185.202 a:host3.aanhet.net -all"	3600

Checks

✓ TTLs within range #32

TTLs: A 1h, AAAA 1h, MX 1h, NS 1h.
✓ 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