Domain report: rocmn.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

warn

ns1.rocmn.nl, ns2.rocmn.nl

Found

Parent zone: nl
Delegation from: ns1.dns.nl (194.0.28.53)
NS at the parent: ns1.rocmn.nl, ns2.rocmn.nl
NS in the zone: ns1.rocmn.nl, ns2.rocmn.nl

Nameserver	Addresses	Network (AS)	Glue
ns1.rocmn.nl	194.171.158.1	AS1103 SURFNET-NL - SURF B.V., NL	194.171.158.1 2001:610:518:158::1
ns2.rocmn.nl	145.120.255.1	AS1103 SURFNET-NL - SURF B.V., NL	145.120.255.1

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.rocmn.nl, ns2.rocmn.nl.

#6
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
!

Glue differs from the zone

The addresses at the parent (glue) differ from the addresses in the zone: ns1.rocmn.nl (glue 194.171.158.1, 2001:610:518:158::1, zone 194.171.158.1). Update the glue at your registrar.

#8
✓ 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 0 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS1103 (SURFNET-NL - SURF B.V., NL): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
i

All nameserver names under .nl

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

2 of 2 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.rocmn.nl 194.171.158.1	NOERROR, 10 ms, authoritative	no	yes / yes	refused	-
ns2.rocmn.nl 145.120.255.1	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 2 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 2011389018 · primary ns1.rocmn.nl

Found

Primary (MNAME): ns1.rocmn.nl
Contact (RNAME): postmaster.rocmn.nl
Serial: 2011389018
Refresh / retry: 10800 s / 1080 s
Expire: 2419200 s
Negative TTL: 900 s

Serial per nameserver

Nameserver	Serial
ns1.rocmn.nl (194.171.158.1)	2011389018
ns2.rocmn.nl (145.120.255.1)	2011389018

Checks

✓ Serial 2011389018 everywhere #22

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

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

The primary nameserver ns1.rocmn.nl is one of the listed nameservers.
✓ Contact postmaster@rocmn.nl #25

The SOA RNAME postmaster.rocmn.nl means postmaster@rocmn.nl.
✓ Timestamp serial #26

The serial 2011389018 is a Unix timestamp (2033-09-26 23:10 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
3379	RSASHA256 (8)	SHA256 3688EA3A8233B619…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
3379	KSK (257)	RSASHA256 (8)
48171	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 3379 (SHA256).
✓ Modern algorithms #29

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

Signatures are valid for 97h0m0s and created on demand; the current one was made at 2026-10-22 11:21 UTC and expires at 2026-10-26 11:58 UTC.
!

NSEC3 with extra iterations or salt

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

20 records at the apex

Found

Read from: 194.171.158.1:53

Type	Value	TTL
SOA	ns1.rocmn.nl. postmaster.rocmn.nl. 2011389018 10800 1080 2419200 900	28800
NS	ns1.rocmn.nl.	28800
NS	ns2.rocmn.nl.	28800
A	86.105.246.112	28800
AAAA	2a01:7c8:e001:72::1f3b	28800
MX	0 rocmn-nl.mail.protection.outlook.com.	3600
TXT	"HARICA-A9pZFmw6Sy1jTgwxVZB"	300
TXT	"DomainVerification=9OENTUFEEI5UK04BV6Y0UYYLU64R7FATY00O344Y5JZ231NSR7E2X6S54WS0CH4X"	300
TXT	"v=spf1 ip4:84.241.176.43 ip4:84.241.173.108 ip4:5.157.87.166 ip4:212.83.220.41 ip4:212.83.220.42 ip6:2001:4018:1404::1041 include:spf.protection.outlook.com ip4:37.97.250.30 ip4:193.172.33.120 ip4:193.172.33.122 ip4:198.2.128.0/24 ip4:198.2.132.0/22" " ip4:198.2.136.0/23 ip4:198.2.145.0/24 ip4:198.2.186.0/23 ip4:205.201.131.128/25 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:198.2.177.0/24 ip4:198.2.178.0/23 ip4:198.2.180.0/24 include:spf1.rocmn.nl ~all"	300
TXT	"MS=ms63793706"	300
TXT	"google-site-verification=IKvVSdV7PSiID2SJgEIjx4A_ArBXY-X_npmjx8YSS8A"	300
TXT	"facebook-domain-verification=krzafh9mp70d1d4kq98vaxcv020zrv"	300
TXT	"pardot791243=17b948b54ec64225bac86551882a814cacbcb4c6a589cf67bb63ecdbb9e3e4a8"	300
TXT	"ufQy9qsjVlyOlmJMVG4dbzQyiN7t7OOoHGLqwcMWJlxJpg3j0afjuJTN5W3eehID"	300
TXT	"KpJJFtYz1gFmvV3SY7Ry6FtTg7X0eoBmrrqO2rnceD5poXkXL9aacL92vGSUSAVr"	300
TXT	"xkWkPfvYklBrLuIVGLGVerjgYPOHLt1LwahoXxcEnRvtbBeFYwAiRLww0L3CIwKQ"	300
TXT	"autodesk-domain-verification=uotqYu-jxFI9c3T4zkaW"	300
TXT	"detectify-verification=82932f6a1b5cde75df49f0af9b1110f4"	300
TXT	"v=NTA7516-1;startdate=2019-06;enddate=2029-09;provider=bastionic;ntamx=10 mx.bastion365.net"	300
TXT	"bastion365-domain-validation=c2c0941257ef7"	300

Checks

✓ TTLs within range #32

TTLs: A 8h, AAAA 8h, MX 1h, NS 8h. The NS TTL at the parent is 1h and in the zone 8h; 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