mooiedomeinnaam.nl

Checked 21 October 2026, 21:23 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 9 info

Registration

info

.nl country-code · Media Village B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Media Village B.V.
Registered
2 March 2014
Last changed
29 December 2022
Status
active
Registry nameservers
ns1.dnsmanager.nl, ns2.dnsmanager.nl
RDAP server
https://rdap.sidn.nl/

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
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

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
NameserverAddressesNetwork (AS)Glue
ns1.dnsmanager.nl141.138.151.155 2a01:a680:a1:f::155AS59545 VXbits - Vertixo BV, NL AS59545 VXbits - Vertixo BV, NL141.138.151.155 2a01:a680:a1:f::155
ns2.dnsmanager.nl141.138.151.156 2a01:a680:a1:f::156AS59545 VXbits - Vertixo BV, NL AS59545 VXbits - Vertixo BV, NL141.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

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dnsmanager.nl 141.138.151.155NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns1.dnsmanager.nl 2a01:a680:a1:f::155NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns2.dnsmanager.nl 141.138.151.156NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.6.3 (built Jul 12 2022 13:11:08 by root@8a04583573b7)
ns2.dnsmanager.nl 2a01:a680:a1:f::156NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS 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 2026092100 · primary ns1.dnsmanager.nl

Found

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

Serial per nameserver

NameserverSerial
ns1.dnsmanager.nl (141.138.151.155)2026092100
ns1.dnsmanager.nl (2a01:a680:a1:f::155)2026092100
ns2.dnsmanager.nl (141.138.151.156)2026092100
ns2.dnsmanager.nl (2a01:a680:a1:f::156)2026092100

Checks

  • ✓ Serial 2026092100 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 2026092100 follows the YYYYMMDDnn convention (2026-09-21).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
7656ECDSAP256SHA256 (13)SHA256 904732285ED98455…yes

DNSKEY in the zone

Key tagRoleAlgorithm
7656KSK (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 7656 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 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

11 records at the apex

Found

Read from
141.138.151.155:53
TypeValueTTL
SOAns1.dnsmanager.nl. hm.mv.nl. 2026092100 28800 7200 604800 36003600
NSns1.dnsmanager.nl.86400
NSns2.dnsmanager.nl.86400
A141.138.151.6086400
AAAA2a01:a680:a1:d::157600
MX10 ASPMX3.GOOGLEMAIL.COM.3600
MX10 ASPMX2.GOOGLEMAIL.COM.3600
MX5 ALT1.ASPMX.L.GOOGLE.COM.86400
MX5 ALT2.ASPMX.L.GOOGLE.COM.86400
MX1 ASPMX.L.GOOGLE.COM.86400
TXT"v=spf1 include:_spf.google.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 10m, MX 1h, 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.
  • 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