asr.nl

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

Registration

info

.nl country-code

Found

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

Delegation

info

bob.ns.cloudflare.com, rosalyn.ns.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
bob.ns.cloudflare.com, rosalyn.ns.cloudflare.com
NS in the zone
bob.ns.cloudflare.com, rosalyn.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
bob.ns.cloudflare.com108.162.193.104 173.245.59.104 172.64.33.104 2803:f800:50::6ca2:c168 2a06:98c1:50::ac40:2168 2606:4700:58::adf5:3b68AS13335 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-
rosalyn.ns.cloudflare.com108.162.194.59 162.159.38.59 172.64.34.59 2803:f800:50::6ca2:c23b 2a06:98c1:50::ac40:223b 2606:4700:50::a29f:263bAS13335 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: bob.ns.cloudflare.com, rosalyn.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
bob.ns.cloudflare.com 108.162.193.104NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 173.245.59.104NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 172.64.33.104NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2803:f800:50::6ca2:c168NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2a06:98c1:50::ac40:2168NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
bob.ns.cloudflare.com 2606:4700:58::adf5:3b68NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 108.162.194.59NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 162.159.38.59NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 172.64.34.59NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 2803:f800:50::6ca2:c23bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 2a06:98c1:50::ac40:223bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rosalyn.ns.cloudflare.com 2606:4700:50::a29f:263bNOERROR, 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: bob.ns.cloudflare.com: "2026.10.2"; rosalyn.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 2417974247 · primary bob.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
bob.ns.cloudflare.com (108.162.193.104)2417974247
bob.ns.cloudflare.com (173.245.59.104)2417974247
bob.ns.cloudflare.com (172.64.33.104)2417974247
bob.ns.cloudflare.com (2803:f800:50::6ca2:c168)2417974247
bob.ns.cloudflare.com (2a06:98c1:50::ac40:2168)2417974247
bob.ns.cloudflare.com (2606:4700:58::adf5:3b68)2417974247
rosalyn.ns.cloudflare.com (108.162.194.59)2417974247
rosalyn.ns.cloudflare.com (162.159.38.59)2417974247
rosalyn.ns.cloudflare.com (172.64.34.59)2417974247
rosalyn.ns.cloudflare.com (2803:f800:50::6ca2:c23b)2417974247
rosalyn.ns.cloudflare.com (2a06:98c1:50::ac40:223b)2417974247
rosalyn.ns.cloudflare.com (2606:4700:50::a29f:263b)2417974247

Checks

  • ✓ Serial 2417974247 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 bob.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 2417974247 is a Unix timestamp (2046-08-15 19:30 UTC).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
2371ECDSAP256SHA256 (13)SHA256 C2EA6530D5539AAC…yes

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)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 2371 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-20 19:45 UTC and expires at 2026-10-22 21:45 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

warn

40 records at the apex

Found

Read from
108.162.193.104:53
TypeValueTTL
SOAbob.ns.cloudflare.com. dns.cloudflare.com. 2417974247 10000 2400 604800 18001800
NSbob.ns.cloudflare.com.86400
NSrosalyn.ns.cloudflare.com.86400
A91.216.184.560
MX0 asr-nl.mail.protection.outlook.com.300
TXT"05dd42a577a105955eb22566869673ed91caa57d"300
TXT"99d0a1aa-3169-4ac7-a6d4-024b72ff6f0d-04032019"300
TXT"DNSscript=202305161052"300
TXT"Dynatrace-site-verification=251c978a-4d1f-4d65-9255-f32cce3ec1cb__8a7h2oh5v8ineb4cno4gsmjm8q"300
TXT"Dynatrace-site-verification=b2df5849-3155-4958-81f3-281ff155b95e__nmkbbiafi07c23fgp719qs0s0n"300
TXT"IZfqOvr4CSmxO42/0kX99KkrfjXtv/vGasZu22ZPja5hJRQPdoYs1ILXt8n9Lm5+KVDXAkDkJTqXk6opS+Qddw=="300
TXT"MS=ms32291996"300
TXT"QuoVadis=438a6c3f-dcd1-4e38-8eac-3c1636207f33"300
TXT"QuoVadis=64eb12dc-d5af-4dab-be1e-2c0ea59d1ea0"300
TXT"SnI6XKqrsBUW9ddni7lbDUfSjuZrNdlcOeuxpvqmXW4="300
TXT"apple-domain-verification=OiAXaoT2W81qEOJp"300
TXT"atlassian-domain-verification=2haKrga6QRGTIBMONf4vFDQYwQqlSnnUjMitQ/TsYfIJZJopJzBbKGFSKiICgi5R"300
TXT"d365mktkey=lD1R5FUAxN2ExUVydxkiVR11z9eWBYbb3znRSgqTUSkx"300
TXT"facebook-domain-verification=h0x3rxzxkvw6zw2beldavlktwwrn4m"300
TXT"gAjn0P9ejyoMVU4IsVD9F4XsmgEX5YqrLGqgZftwwvE="300
TXT"google-site-verification=oJVcqsdFq58rPzqLi3hA8IdJ2TY5PrSLIi-9GKVd4bo"300
TXT"mentimeter-0f03c405-c744-4c8b-a317-87b3e5bb434a"300
TXT"onetrust-domain-verification=6a088b3ad8d146bfa3c1028a2fc390ba"300
TXT"paloaltonetworks-site-verification=4659e04335e38ef104201e958bdc448a39d69af3ef369ee8a0a294b25ab08b90"300
TXT"sqn6g2lvhggk3nfzts5s733pldzljqg5"300
TXT"v=spf1 include:_spf.asr.nl ip4:193.105.111.9 include:_spf.zorgmail.nl ip4:185.177.101.5 -all"300
CAA0 iodef "mailto:certificaten.itc@asr.nl"300
CAA0 issue "comodoca.com"300
CAA0 issue "digicert.com; cansignhttpexchanges=yes"300
CAA0 issue "globalsign.com"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "pki.goog; cansignhttpexchanges=yes"300
CAA0 issue "quovadisglobal.com"300
CAA0 issue "sectigo.com"300
CAA0 issue "ssl.com"300
CAA0 issuewild "comodoca.com"300
CAA0 issuewild "digicert.com; cansignhttpexchanges=yes"300
CAA0 issuewild "letsencrypt.org"300
CAA0 issuewild "pki.goog; cansignhttpexchanges=yes"300
CAA0 issuewild "ssl.com"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: comodoca.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog, quovadisglobal.com, sectigo.com, ssl.com.