timing.nl

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

Registration

info

.nl country-code

Found

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

Delegation

warn

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

Found

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

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns4-03.azure-dns.info. ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info report NS ns1-03.azure-dns.com ns2-03.azure-dns.net ns3-03.azure-dns.org ns4-03.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-03.azure-dns.com 13.107.236.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-03.azure-dns.com 2603:1061:0:700::3NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 150.171.21.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-03.azure-dns.net 2620:1ec:8ec:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 204.14.183.3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-03.azure-dns.org 2a01:111:4000:700::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-03.azure-dns.info 208.84.5.3NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-03.azure-dns.info 2620:1ec:bda:700::3NOERROR, 5 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-03.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-03.azure-dns.com

Found

Primary (MNAME)
ns1-03.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-03.azure-dns.com (13.107.236.3)1
ns1-03.azure-dns.com (2603:1061:0:700::3)1
ns2-03.azure-dns.net (150.171.21.3)1
ns2-03.azure-dns.net (2620:1ec:8ec:700::3)1
ns3-03.azure-dns.org (204.14.183.3)1
ns3-03.azure-dns.org (2a01:111:4000:700::3)1
ns4-03.azure-dns.info (208.84.5.3)1
ns4-03.azure-dns.info (2620:1ec:bda:700::3)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-03.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

info

16 records at the apex

Found

Read from
13.107.236.3:53
TypeValueTTL
SOAns1-03.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-03.azure-dns.com.172800
NSns2-03.azure-dns.net.172800
NSns3-03.azure-dns.org.172800
NSns4-03.azure-dns.info.172800
A20.50.2.85300
MX10 timing-nl.mail.protection.outlook.com.3600
TXT"v=spf1 ip4:83.137.145.0/24 ip4:89.188.15.0/24 ip6:2a01:1b0:7999:402::/64 ip4:217.114.96.238 ip4:85.209.108.192/27 ip4:87.249.107.205 ip4:89.207.28.4 ip4:87.249.107.196 ip4:167.89.0.0/17 ip4:204.220.160.0/21 ip4:95.168.220.192/26 ip4:208.117.48.0/20 ip4:5" "0.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:82.201.64.228 ip4:205.201.128.0/20 ip4:148.105.8.0/21 ip4" ":198.37.153.132 ip4:104.40.229.156 ip4:52.169.0.179 ip4:20.50.220.144/28 ip4:40.127.253.48/28 ip4:85.214.60.41 ip4:81.169.234.199/32 ip4:81.169.242.205/32 ip4:85.214.235.145/32 ip4:81.169.234.114/32 ip4:149.72.88.121/32 ip4:79.174.130.64/27 ip4:213.171.1" "51.80/29 ip4:178.208.56.145/28 ip4:79.174.134.160/28 ip4:185.46.182.1 ip4:185.46.182.200/29 ip4:185.46.182.208/31 ip4:95.168.207.80/28 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.23" "6.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:185.136.64.128/27 ip4:159.183.0.0/16 ip4:185.211.208.10/32 ip4:185.136.65.128/27 ip4:88.86.113.160/27 ip4:185.18.11.16/29 ip4:82.208.41.201 ip4:198.2.128.0/18 ip" "4:86.105.244.9 ip4:86.105.244.3 ip4:86.105.244.8 ip4:198.2.186.0/23 ip4:205.201.131.0/24 ip4:205.201.134.128/25 ip4:205.201.136.0/23 ip4:205.201.139.0/24 ip4:185.6.160.213/32 include:_spf.eu.sparkpostmail.com include:amazonses.com include:turbo-smtp.com " "include:spf.sendinblue.com include:spf.protection.outlook.com include:spf.afas.online ~all"3600
TXT"atlassian-domain-verification=SVjjtK8x/a2tmoxEzf9KZik/KvuaJWFuAVC08zDyOVbNJsXu/x8mdi8N1bP7fa4J"3600
TXT"apple-domain-verification=YkRq9ytYTLbeLMx4"3600
TXT"atlassian-domain-verification=iiSqElVWb924W6YkEX4S/OeR4Z7c05nr5acBMmLw5AYN0slbVblkkA7dFh8RDYzV"3600
TXT"bw=oFsGm2aXPZodnvBh7cBLb+/osEco7nEYMMYkLooeTYW1"3600
TXT"d365mktkey=bLLzhv1kQ7PG5j3CObKCyUT1llu4AfinosxxzgxxSCcx"3600
TXT"knowbe4-site-verification=b616f00809934f1eaefd5990707ea91e"3600
TXT"Sendinblue-code:8bcc7ab560606c4fe595bb0e5968c79e"3600
TXT"anthropic-domain-verification-cm7mcd=Cqi2YWx3PhUSkLFsfFlDkynCC"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, 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.
  • 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