Domain report: vwa.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

info

ns1.dictu.nl, ns2.dictu.nl

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.dictu.nl	145.12.216.1 2a04:9a00:1021:201c::1	AS203396 MinEZ-DICTU - Ministerie van Economische Zaken, NL AS203396 MinEZ-DICTU - Ministerie van Economische Zaken, NL	145.12.216.1 2a04:9a00:1021:201c::1
ns2.dictu.nl	145.69.216.1 2a04:9a00:1022:201c::1	AS203396 MinEZ-DICTU - Ministerie van Economische Zaken, NL AS203396 MinEZ-DICTU - Ministerie van Economische Zaken, NL	145.69.216.1 2a04:9a00:1022:201c::1

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dictu.nl, ns2.dictu.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 2 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS203396 (MinEZ-DICTU - Ministerie van Economische Zaken, NL): 4 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
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.dictu.nl 145.12.216.1	NOERROR, 21 ms, authoritative	no	yes / yes	refused	-
ns1.dictu.nl 2a04:9a00:1021:201c::1	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-
ns2.dictu.nl 145.69.216.1	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-
ns2.dictu.nl 2a04:9a00:1022:201c::1	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 4 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 41262 · primary ns1.dictu.nl

Found

Primary (MNAME): ns1.dictu.nl
Contact (RNAME): datacom.dictu.nl
Serial: 41262
Refresh / retry: 43200 s / 3600 s
Expire: 2419200 s
Negative TTL: 900 s

Serial per nameserver

Nameserver	Serial
ns1.dictu.nl (145.12.216.1)	41262
ns1.dictu.nl (2a04:9a00:1021:201c::1)	41262
ns2.dictu.nl (145.69.216.1)	41262
ns2.dictu.nl (2a04:9a00:1022:201c::1)	41262

Checks

✓ Serial 41262 everywhere #22

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

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

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

The SOA RNAME datacom.dictu.nl means datacom@dictu.nl.
✓ Counter serial #26

The serial 41262 is a plain counter.

DNSSEC

warn

Signed, DS published at parent

Found

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

DS at the parent

Key tag	Algorithm	Digest	Matches a key
38949	ECDSAP256SHA256 (13)	SHA256 B97A19048CA12B28…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
55819	KSK (257)	RSASHA256 (8)
50731	KSK (257)	RSASHA256 (8)
54684	ZSK (256)	ECDSAP256SHA256 (13)
6461	ZSK (256)	ECDSAP256SHA256 (13)
38949	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 38949 (SHA256).
✓ Modern algorithms #29

Key algorithms: ECDSAP256SHA256 (13), 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-21 20:24 UTC and expires at 2026-10-25 20:50 UTC.
!

NSEC3 with extra iterations or salt

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

10 records at the apex

Found

Read from: 145.12.216.1:53

Type	Value	TTL
SOA	ns1.dictu.nl. datacom.dictu.nl. 41262 43200 3600 2419200 900	3600
NS	ns1.dictu.nl.	3600
NS	ns2.dictu.nl.	3600
MX	20 mail03.dictu.nl.	3600
MX	10 mail02.dictu.nl.	3600
MX	20 mail01.dictu.nl.	3600
MX	10 mail04.dictu.nl.	3600
TXT	"cisco-ci-domain-verification=7ba94fb7808101c4113248e8e23e8634953702049198819be7d136b78cc26504"	3600
TXT	"v=spf1 include:_spf.dictu.nl include:amazonses.com -all"	3600
TXT	"_ww2sf3rrto3csyt449e4euu7z7c876f"	3600

Checks

✓ TTLs within range #32

TTLs: 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