Domain report: nam.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

warn

dns1.shell.com, dns2.shell.com, dns3.shell.com

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: dns1.shell.com, dns2.shell.com, dns3.shell.com
NS in the zone: dns1.shell.com, dns2.shell.com, dns3.shell.com

Nameserver	Addresses	Network (AS)	Glue
dns1.shell.com	134.146.80.20	AS3917 SHELL-3917 - Shell Information Technology International B.V., EU	-
dns2.shell.com	144.199.196.20	AS3918 SHELL-3918 - Shell Information Technology International B.V., EU	-
dns3.shell.com	134.163.128.20	AS11355 SHELL - Shell Information Technology International, Inc., US	-

Checks

✓ 3 nameservers #6

Delegated to dns1.shell.com, dns2.shell.com, dns3.shell.com.
✓ 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 0 IPv6 /48s.
✓ 3 autonomous systems #11

The nameservers are spread over: AS11355 (SHELL - Shell Information Technology International, Inc., US): 1 address; AS3917 (SHELL-3917 - Shell Information Technology International B.V., EU): 1 address; AS3918 (SHELL-3918 - Shell Information Technology International B.V., EU): 1 address.
i

All nameserver names under .com

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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns1.shell.com 134.146.80.20	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-
dns2.shell.com 144.199.196.20	NOERROR, 248 ms, authoritative	no	yes / yes	refused	-
dns3.shell.com 134.163.128.20	NOERROR, 134 ms, authoritative	no	yes / yes	refused	-

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.
✓ 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 16862 · primary dns1.shell.com

Found

Primary (MNAME): dns1.shell.com
Contact (RNAME): dns.shell.com
Serial: 16862
Refresh / retry: 10800 s / 1080 s
Expire: 2419200 s
Negative TTL: 600 s

Serial per nameserver

Nameserver	Serial
dns1.shell.com (134.146.80.20)	16862
dns2.shell.com (144.199.196.20)	16862
dns3.shell.com (134.163.128.20)	16862

Checks

✓ Serial 16862 everywhere #22

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

SOA refresh 3h, retry 18m, expire 28d, negative TTL 10m.
✓ Primary is a public nameserver #24

The primary nameserver dns1.shell.com is one of the listed nameservers.
✓ Contact dns@shell.com #25

The SOA RNAME dns.shell.com means dns@shell.com.
✓ Counter serial #26

The serial 16862 is a plain counter.

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 10 iterations, 1-byte salt
Signatures valid until: 26 October 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
25765	RSASHA256 (8)	SHA256 B44C4C964CC3019B…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
759	ZSK (256)	RSASHA256 (8)
48631	ZSK (256)	RSASHA256 (8)
5822	KSK (257)	RSASHA256 (8)
25765	KSK (257)	RSASHA256 (8)
10509	ZSK (256)	RSASHA256 (8)

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 25765 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Short-lived signatures (online signing) #30

Signatures are valid for 96h0m0s and created on demand; the current one was made at 2026-10-22 05:57 UTC and expires at 2026-10-26 06:07 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 10 iterations and a 1-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

15 records at the apex

Found

Read from: 134.146.80.20:53

Type	Value	TTL
SOA	dns1.shell.com. dns.shell.com. 16862 10800 1080 2419200 600	86400
NS	dns3.shell.com.	86400
NS	dns1.shell.com.	86400
NS	dns2.shell.com.	86400
A	4.210.156.184	86400
MX	0 nam-nl.j-v1.mx.microsoft.	86400
TXT	"f7jpdw16b5jytf7qg9pg1w5bs2w9v41j"	300
TXT	"_5wtvr6abpj9l6dz0y4zxf6t8lw6l9em"	300
TXT	"mindmanager-verification=46eaa26621e4955c1675b55d446c6d03325f458b59a465f898d42924010e7286"	300
TXT	"v=spf1 include:_spf.shell.com include:spf.protection.outlook.com -all"	300
TXT	"vfr29GuOJiuywjcDpZCVdLbC3cvBtMhiv1vgYDh/r9ml1m18kgo/tjCPRGIuwK4ifBwtfisW8ELyJLyWtiq55Q=="	300
TXT	"google-site-verification=NnKevEGirq-1i-FfFEl6aB7tv0HaoHLTAzeEA1geBDE"	300
TXT	"Nz2oAMC5XkbeWqSs/dXn2j8HwgbXbkywr3XRppExlj8tyr2PKSsZ9QErm+QXeqegCHKdnJTmR7HPg/k/zVkxxA=="	300
TXT	"b1tgvjlw53shbd75xjn9hqsjdzgw5h5d"	300
TXT	"facebook-domain-verification=4zv17g0puztvot8wlaermlggxzisi0"	300

Checks

✓ TTLs within range #32

TTLs: A 1d, 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.
✓ 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