Domain report: plaatsengids.nl

Registration

info

.nl country-code

Found

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

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

#3

Delegation

warn

ns1.dnsmanager.nl, ns2.dnsmanager.nl

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.dnsmanager.nl	141.138.151.155 2a01:a680:a1:f::155	AS59545 VXbits - Vertixo BV, NL AS59545 VXbits - Vertixo BV, NL	141.138.151.155 2a01:a680:a1:f::155
ns2.dnsmanager.nl	141.138.151.156 2a01:a680:a1:f::156	AS59545 VXbits - Vertixo BV, NL AS59545 VXbits - Vertixo BV, NL	141.138.151.156 2a01:a680:a1:f::156

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dnsmanager.nl, ns2.dnsmanager.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 one network

all IPv4 addresses are in 141.138.151.0/24; all IPv6 addresses are in 2a01:a680:a1::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS59545 (VXbits - Vertixo BV, 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

warn

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.dnsmanager.nl 141.138.151.155	NOERROR, 11 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns1.dnsmanager.nl 2a01:a680:a1:f::155	NOERROR, 11 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns2.dnsmanager.nl 141.138.151.156	NOERROR, 16 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns2.dnsmanager.nl 2a01:a680:a1:f::156	NOERROR, 15 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)

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

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dnsmanager.nl: "PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)"; ns2.dnsmanager.nl: "PowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)". 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 2026081401 · primary ns1.dnsmanager.nl

Found

Primary (MNAME): ns1.dnsmanager.nl
Contact (RNAME): hm.mv.nl
Serial: 2026081401
Refresh / retry: 28800 s / 7200 s
Expire: 604800 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
ns1.dnsmanager.nl (141.138.151.155)	2026081401
ns1.dnsmanager.nl (2a01:a680:a1:f::155)	2026081401
ns2.dnsmanager.nl (141.138.151.156)	2026081401
ns2.dnsmanager.nl (2a01:a680:a1:f::156)	2026081401

Checks

✓ Serial 2026081401 everywhere #22

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

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

The primary nameserver ns1.dnsmanager.nl is one of the listed nameservers.
✓ Contact hm@mv.nl #25

The SOA RNAME hm.mv.nl means hm@mv.nl.
✓ Date-based serial #26

The serial 2026081401 follows the YYYYMMDDnn convention (2026-08-14).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver: no
Denial of existence: NSEC
Signatures valid until: 5 November 2026

DNSKEY in the zone

Key tag	Role	Algorithm
60694	KSK (257)	ECDSAP256SHA256 (13)

Checks

!

Signed but not delegated securely

The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

#27
✓ Modern algorithms #29

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

The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 UTC.
i

NSEC

The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.

#31

Records

info

7 records at the apex

Found

Read from: 141.138.151.155:53

Type	Value	TTL
SOA	ns1.dnsmanager.nl. hm.mv.nl. 2026081401 28800 7200 604800 3600	3600
NS	ns2.dnsmanager.nl.	3600
NS	ns1.dnsmanager.nl.	3600
A	92.63.163.157	3600
AAAA	2a01:a680:a1:d::157	3600
MX	0 .	3600
TXT	"v=spf1 -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