snelstart.nl

Checked 22 October 2026, 16:10 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 3 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org
NS in the zone
ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-01.azure-dns.com13.107.236.1 2603:1061:0:700::1AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-01.azure-dns.net150.171.21.1 2620:1ec:8ec:700::1AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-01.azure-dns.org204.14.183.1 2a01:111:4000:700::1AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-01.azure-dns.info (zone only)208.84.5.1 2620:1ec:bda:700::1AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns4-01.azure-dns.info. ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info report NS ns1-01.azure-dns.com ns2-01.azure-dns.net ns3-01.azure-dns.org ns4-01.azure-dns.info.
    #7
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 3 TLDs #12
    Nameserver names use the TLDs .com, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-01.azure-dns.com 13.107.236.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-01.azure-dns.com 2603:1061:0:700::1NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-01.azure-dns.net 150.171.21.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-01.azure-dns.net 2620:1ec:8ec:700::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-01.azure-dns.org 204.14.183.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-01.azure-dns.org 2a01:111:4000:700::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-01.azure-dns.info 208.84.5.1NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-01.azure-dns.info 2620:1ec:bda:700::1NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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: ns4-01.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 1 · primary ns1-01.azure-dns.com

Found

Primary (MNAME)
ns1-01.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-01.azure-dns.com (13.107.236.1)1
ns1-01.azure-dns.com (2603:1061:0:700::1)1
ns2-01.azure-dns.net (150.171.21.1)1
ns2-01.azure-dns.net (2620:1ec:8ec:700::1)1
ns3-01.azure-dns.org (204.14.183.1)1
ns3-01.azure-dns.org (2a01:111:4000:700::1)1
ns4-01.azure-dns.info (208.84.5.1)1
ns4-01.azure-dns.info (2620:1ec:bda:700::1)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-01.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

pass

16 records at the apex

Found

Read from
13.107.236.1:53
TypeValueTTL
SOAns1-01.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-01.azure-dns.com.172800
NSns2-01.azure-dns.net.172800
NSns3-01.azure-dns.org.172800
NSns4-01.azure-dns.info.172800
A51.105.232.102600
MX10 snelstart-nl.mail.protection.outlook.com.86400
TXT"v=spf1 include:spf.protection.outlook.com include:spf.afas.online include:sendgrid.net include:239619.spf10.hubspotemail.net ip4:82.151.55.142 ip4:93.117.204.30 ip4:31.160.172.25 ip4:185.239.63.99 include:spf.dc.accent.nl include:spf.sebsoft.nl ~all"3600
TXT"miro-verification=66e7a4f02c6c5991fdd0d3eff5fa7167084d2dee"3600
TXT"google-site-verification=ozvzKh91cg424gnwHl_jKl7aLgf3v86GLhK0FguouPo"3600
TXT"anthropic-domain-verification-vzjftr=FHLsOBlVKPgAsUnMDPLr2VCjk"3600
TXT"openai-domain-verification=dv-r9lel5kQUHpYnwKNN9r4ybxC"3600
CAA0 issue "digicert.com"3600
CAA0 issue "pki.goog"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "d-trust.net"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1d, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; 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.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, pki.goog, letsencrypt.org, d-trust.net.