canonvannederland.nl

Checked 21 October 2026, 21:00 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 7 info

Registration

info

.nl country-code · Driebit Hosting B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Driebit Hosting B.V.
Registered
6 July 2005
Last changed
10 August 2017
Status
active
Registry nameservers
ns1.driebit.nl, ns2.driebit.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

info

ns1.driebit.nl, ns2.driebit.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.driebit.nl, ns2.driebit.nl
NS in the zone
ns1.driebit.nl, ns2.driebit.nl
NameserverAddressesNetwork (AS)Glue
ns1.driebit.nl109.204.10.53 2a02:cb0:1::53AS45014 NCONNECT - Nuco Technologies Ltd, GB AS45014 NCONNECT - Nuco Technologies Ltd, GB109.204.10.53 2a02:cb0:1::53
ns2.driebit.nl85.17.32.205 2001:1af8:2100:a004:3::1AS60781 LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V., NL AS60781 LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V., NL85.17.32.205 2001:1af8:2100:a004:3::1

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.driebit.nl, ns2.driebit.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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS45014 (NCONNECT - Nuco Technologies Ltd, GB): 2 addresses; AS60781 (LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V., NL): 2 addresses.
  • 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.driebit.nl 109.204.10.53NOERROR, 19 ms, authoritativenoyes / yesrefusedKnot DNS 3.3.7
ns1.driebit.nl 2a02:cb0:1::53NOERROR, 12 ms, authoritativenoyes / yesrefusedKnot DNS 3.3.7
ns2.driebit.nl 85.17.32.205NOERROR, 9 ms, authoritativenoyes / yesrefusedKnot DNS 3.4.7
ns2.driebit.nl 2001:1af8:2100:a004:3::1NOERROR, 10 ms, authoritativenoyes / yesrefusedKnot DNS 3.4.7

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.driebit.nl: "Knot DNS 3.3.7"; ns2.driebit.nl: "Knot DNS 3.4.7". 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 2026092101 · primary ns1.driebit.nl

Found

Primary (MNAME)
ns1.driebit.nl
Contact (RNAME)
hosting.driebit.nl
Serial
2026092101
Refresh / retry
10800 s / 3600 s
Expire
1814400 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.driebit.nl (109.204.10.53)2026092101
ns1.driebit.nl (2a02:cb0:1::53)2026092101
ns2.driebit.nl (85.17.32.205)2026092101
ns2.driebit.nl (2001:1af8:2100:a004:3::1)2026092101

Checks

  • ✓ Serial 2026092101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 21d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.driebit.nl is one of the listed nameservers.
  • ✓ Contact hosting@driebit.nl #25
    The SOA RNAME hosting.driebit.nl means hosting@driebit.nl.
  • ✓ Date-based serial #26
    The serial 2026092101 follows the YYYYMMDDnn convention (2026-09-21).

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
109.204.10.53:53
TypeValueTTL
SOAns1.driebit.nl. hosting.driebit.nl. 2026092101 10800 3600 1814400 600600
NSns1.driebit.nl.600
NSns2.driebit.nl.600
A83.98.140.23600
AAAA2001:16f8:4::23600
MX0 plesk.driebit.eu.600
TXT"facebook-domain-verification=fi168y168hyn4o68hdr7vbshj3xvc9"600
TXT"google-site-verification=_hVfZHkk2QTf8D1QwXYPMK3LCpe1xgt7xhKf5KwJQrw"600
TXT"v=spf1 include:_spf.driebit.net include:mailswitch.nl include:mandrillapp.com ~all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, MX 10m, NS 10m. The NS TTL at the parent is 1h and in the zone 10m; 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