managersonline.nl

Checked 22 October 2026, 14:21 UTC · via 8.8.8.8
✗Problems found
21 passed 1 warning 1 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/managersonline.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/managersonline.nl returned HTTP 429
    #3

Delegation

info

ns.naamserver.net, ns1.naamserver.net, ns2.naamserver.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns.naamserver.net, ns1.naamserver.net, ns2.naamserver.net
NS in the zone
ns.naamserver.net, ns1.naamserver.net, ns2.naamserver.net
NameserverAddressesNetwork (AS)Glue
ns.naamserver.net185.103.159.158 2a00:f10:400:4:1c00:aff:fe00:169cAS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
ns1.naamserver.net185.94.228.152 2a05:1500:501:1:1c00:67ff:fe00:108AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
ns2.naamserver.net92.63.173.169 2a05:1500:702:3:1c00:d2ff:fe00:14b2AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.naamserver.net, ns1.naamserver.net, ns2.naamserver.net.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS48635 (CLDIN-NL - Your Hosting B.V., NL): 6 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 .net
    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

fail

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.naamserver.net 185.103.159.158NOERROR, 10 ms, authoritativenoyes / yesALLOWED (29 records)-
ns.naamserver.net 2a00:f10:400:4:1c00:aff:fe00:169cNOERROR, 11 ms, authoritativenoyes / yesALLOWED (29 records)-
ns1.naamserver.net 185.94.228.152NOERROR, 9 ms, authoritativenoyes / yesALLOWED (29 records)-
ns1.naamserver.net 2a05:1500:501:1:1c00:67ff:fe00:108NOERROR, 10 ms, authoritativenoyes / yesALLOWED (29 records)-
ns2.naamserver.net 92.63.173.169NOERROR, 10 ms, authoritativenoyes / yesALLOWED (29 records)-
ns2.naamserver.net 2a05:1500:702:3:1c00:d2ff:fe00:14b2NOERROR, 10 ms, authoritativenoyes / yesALLOWED (29 records)-

Checks

  • ✓ All respond #14
    All 6 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 transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.naamserver.net (185.103.159.158): 29 records; ns.naamserver.net (2a00:f10:400:4:1c00:aff:fe00:169c): 29 records; ns1.naamserver.net (185.94.228.152): 29 records; ns1.naamserver.net (2a05:1500:501:1:1c00:67ff:fe00:108): 29 records; ns2.naamserver.net (92.63.173.169): 29 records; ns2.naamserver.net (2a05:1500:702:3:1c00:d2ff:fe00:14b2): 29 records. Restrict zone transfers to your secondary servers.
    #18
  • ✓ 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 2021083104 · primary ns.naamserver.net

Found

Primary (MNAME)
ns.naamserver.net
Contact (RNAME)
hostmaster.naamserver.net
Serial
2021083104
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.naamserver.net (185.103.159.158)2021083104
ns.naamserver.net (2a00:f10:400:4:1c00:aff:fe00:169c)2021083104
ns1.naamserver.net (185.94.228.152)2021083104
ns1.naamserver.net (2a05:1500:501:1:1c00:67ff:fe00:108)2021083104
ns2.naamserver.net (92.63.173.169)2021083104
ns2.naamserver.net (2a05:1500:702:3:1c00:d2ff:fe00:14b2)2021083104

Checks

  • ✓ Serial 2021083104 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 ns.naamserver.net is one of the listed nameservers.
  • ✓ Contact hostmaster@naamserver.net #25
    The SOA RNAME hostmaster.naamserver.net means hostmaster@naamserver.net.
  • ✓ Date-based serial #26
    The serial 2021083104 follows the YYYYMMDDnn convention (2021-08-31).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

9 records at the apex

Found

Read from
185.103.159.158:53
TypeValueTTL
SOAns.naamserver.net. hostmaster.naamserver.net. 2021083104 14400 3600 604800 8640086400
NSns1.naamserver.net.86400
NSns2.naamserver.net.86400
NSns.naamserver.net.86400
A185.110.174.7600
MX10 mx01.provider.nl.3600
MX20 mx02.provider.nl.3600
TXT"v=spf1 include:s.mc1.nl ip4:185.110.174.7 -all"600
TXT"google-site-verification=LtAcDahDjjCy94KZ7ocEasgsGXRAgXrFjNGko98HUxw"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 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