Domain report: underware.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

ns1.anony.nl, ns2.anony.nl

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.anony.nl	62.84.243.10 2a02:2968:2::10	AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL	62.84.243.10 2a02:2968:2::10
ns2.anony.nl	185.27.140.33	AS48635 CLDIN-NL - Your Hosting B.V., NL	185.27.140.33

Checks

i

2 nameservers

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

#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.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS48635 (CLDIN-NL - Your Hosting B.V., NL): 3 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
i

Partly IPv6

These nameservers have no IPv6 address: ns2.anony.nl.

#13

Nameservers

info

3 of 3 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.anony.nl 62.84.243.10	NOERROR, 11 ms, authoritative	no	yes / yes	refused	Bind
ns1.anony.nl 2a02:2968:2::10	NOERROR, 11 ms, authoritative	no	yes / yes	refused	Bind
ns2.anony.nl 185.27.140.33	NOERROR, 11 ms, authoritative	no	yes / yes	refused	Bind

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.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.anony.nl: "Bind"; ns2.anony.nl: "Bind".

#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 2100000618 · primary ns1.anony.nl

Found

Primary (MNAME): ns1.anony.nl
Contact (RNAME): hostmaster.underware.nl
Serial: 2100000618
Refresh / retry: 14400 s / 3600 s
Expire: 604800 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
ns1.anony.nl (62.84.243.10)	2100000618
ns1.anony.nl (2a02:2968:2::10)	2100000618
ns2.anony.nl (185.27.140.33)	2100000618

Checks

✓ Serial 2100000618 everywhere #22

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

SOA refresh 4h, retry 1h, expire 7d, negative TTL 1d.
✓ Primary is a public nameserver #24

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

The SOA RNAME hostmaster.underware.nl means hostmaster@underware.nl.
✓ Timestamp serial #26

The serial 2100000618 is a Unix timestamp (2036-07-18 13:30 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
14629	RSASHA256 (8)	SHA256 06A74D37C80259E9…	NO
12040	RSASHA256 (8)	SHA256 4FCDD3C8B25C0AD5…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
12040	KSK (257)	RSASHA256 (8)
22266	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.
i

Unused DS records

These DS records match no key in the zone: key tag 14629 (SHA256). That is normal during a key rollover; otherwise remove them.

#28
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ 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 1 iteration 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

8 records at the apex

Found

Read from: 62.84.243.10:53

Type	Value	TTL
SOA	ns1.anony.nl. hostmaster.underware.nl. 2100000618 14400 3600 604800 86400	900
NS	ns2.anony.nl.	900
NS	ns1.anony.nl.	900
A	46.17.2.79	3600
MX	10 srv2.flexfilter.nl.	86400
MX	10 srv1.flexfilter.nl.	86400
TXT	"v=spf1 a mx a:spf.flexfilter.nl include:servers.mcsv.net -all"	86400
TXT	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt8aQVH9Tc9CYtawnRwBv1x8ysf6Sx3/ryqC0gUobeSG1pzuzInImbxgaTtM2ZWk2C08O57hgFbwG++Cg97g2ZbvzsSAD8s0BGi87TRjwQjnDYjbL37IzMJTRnMcVtDM/52iTQck75bTxjGPfExvP2H+apR0H/51YELaF9Ef3AVgmZD6ELrc1HouGsNepjlmB9" "+KF1GnbfNTfdOPcKB4KbAHZgzNinMwJkHVvIE55AbheBymaraOR6CEC3ov1ElSSoIu1HMrXFqcZpc7kWDbo8jMNDmcG6CyQBIhqnsKBN9YngTgJf9z6gnY5JtIMBGy1J4d0oW71+jSOYAyZ7s5lrwIDAQAB"	86400

Checks

✓ TTLs within range #32

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