jamin.nl

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

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
23 April 1995
Last changed
30 March 2021
Status
active
Registry nameservers
lilith.ns.cloudflare.com, peter.ns.cloudflare.com
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

lilith.ns.cloudflare.com, peter.ns.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
lilith.ns.cloudflare.com, peter.ns.cloudflare.com
NS in the zone
lilith.ns.cloudflare.com, peter.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
lilith.ns.cloudflare.com162.159.38.143 108.162.194.143 172.64.34.143 2803:f800:50::6ca2:c28f 2606:4700:50::a29f:268f 2a06:98c1:50::ac40:228fAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
peter.ns.cloudflare.com162.159.44.3 108.162.195.3 172.64.35.3 2606:4700:58::a29f:2c03 2a06:98c1:50::ac40:2303 2803:f800:50::6ca2:c303AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: lilith.ns.cloudflare.com, peter.ns.cloudflare.com.
    #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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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 .com
    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

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
lilith.ns.cloudflare.com 162.159.38.143NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
lilith.ns.cloudflare.com 108.162.194.143NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
lilith.ns.cloudflare.com 172.64.34.143NOERROR, 19 ms, authoritativenoyes / yesrefused2026.10.2
lilith.ns.cloudflare.com 2803:f800:50::6ca2:c28fNOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
lilith.ns.cloudflare.com 2606:4700:50::a29f:268fNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
lilith.ns.cloudflare.com 2a06:98c1:50::ac40:228fNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 162.159.44.3NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 108.162.195.3NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 172.64.35.3NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 2606:4700:58::a29f:2c03NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 2a06:98c1:50::ac40:2303NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
peter.ns.cloudflare.com 2803:f800:50::6ca2:c303NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: lilith.ns.cloudflare.com: "2026.10.2"; peter.ns.cloudflare.com: "2026.10.2". 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 2416560376 · primary lilith.ns.cloudflare.com

Found

Primary (MNAME)
lilith.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2416560376
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
lilith.ns.cloudflare.com (162.159.38.143)2416560376
lilith.ns.cloudflare.com (108.162.194.143)2416560376
lilith.ns.cloudflare.com (172.64.34.143)2416560376
lilith.ns.cloudflare.com (2803:f800:50::6ca2:c28f)2416560376
lilith.ns.cloudflare.com (2606:4700:50::a29f:268f)2416560376
lilith.ns.cloudflare.com (2a06:98c1:50::ac40:228f)2416560376
peter.ns.cloudflare.com (162.159.44.3)2416560376
peter.ns.cloudflare.com (108.162.195.3)2416560376
peter.ns.cloudflare.com (172.64.35.3)2416560376
peter.ns.cloudflare.com (2606:4700:58::a29f:2c03)2416560376
peter.ns.cloudflare.com (2a06:98c1:50::ac40:2303)2416560376
peter.ns.cloudflare.com (2803:f800:50::6ca2:c303)2416560376

Checks

  • ✓ Serial 2416560376 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver lilith.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2416560376 is a Unix timestamp (2046-07-30 10:46 UTC).

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

13 records at the apex

Found

Read from
162.159.38.143:53
TypeValueTTL
SOAlilith.ns.cloudflare.com. dns.cloudflare.com. 2416560376 10000 2400 604800 18001800
NSlilith.ns.cloudflare.com.86400
NSpeter.ns.cloudflare.com.86400
A172.67.145.193300
A104.21.63.136300
AAAA2606:4700:3031::ac43:91c1300
AAAA2606:4700:3030::6815:3f88300
MX0 d333088.a.ess.de.barracudanetworks.com.300
MX5 d333088.b.ess.de.barracudanetworks.com.300
TXT"MS=ms67848218"300
TXT"ca3-72dbdb4ed03f4efa9cef2a41d0ae818b"300
TXT"google-site-verification=iOEd99oxJrZfM80ohmw07FRrKSzOTFmXRjBkCQsOI-c"300
TXT"v=spf1 a mx ip4:94.237.43.187 ip4:85.214.244.150 ip4:94.237.45.217 ip4:80.69.67.19/24 ip6:2a01:7c8::2500/124 ip4:81.4.64.105 ip4:81.173.50.130 ip4:81.173.50.163 ip4:81.4.69.3 ip4:185.36.134.73 ip4:149.210.244.136 ip4:37.97.228.193 ip4:81.173.50.151 ip4:81" ".173.50.152 ip4:136.144.142.37 ip4:77.171.150.243 ip4:82.169.10.254 ip4:86.91.153.218 ip4:213.127.105.124 ip4:213.127.98.72 ip4:83.87.28.209 ip4:81.173.50.130 include:_spf.hellodialog.com include:spf.protection.outlook.com ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, 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.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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