toyota.nl

Checked 22 October 2026, 16:40 UTC · via 8.8.8.8
!Passed with warnings
27 passed 1 warning 0 failed 5 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

Found

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

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info.
  • ✓ 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 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 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .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-02.azure-dns.com 13.107.236.2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-02.azure-dns.com 2603:1061:0:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-02.azure-dns.net 150.171.21.2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-02.azure-dns.net 2620:1ec:8ec:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-02.azure-dns.org 204.14.183.2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-02.azure-dns.org 2a01:111:4000:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-02.azure-dns.info 208.84.5.2NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-02.azure-dns.info 2620:1ec:bda:700::2NOERROR, 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-02.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-02.azure-dns.com

Found

Primary (MNAME)
ns1-02.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-02.azure-dns.com (13.107.236.2)1
ns1-02.azure-dns.com (2603:1061:0:700::2)1
ns2-02.azure-dns.net (150.171.21.2)1
ns2-02.azure-dns.net (2620:1ec:8ec:700::2)1
ns3-02.azure-dns.org (204.14.183.2)1
ns3-02.azure-dns.org (2a01:111:4000:700::2)1
ns4-02.azure-dns.info (208.84.5.2)1
ns4-02.azure-dns.info (2620:1ec:bda:700::2)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-02.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

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
29635ECDSAP256SHA256 (13)SHA256 01ABF08EAC04C369…yes

DNSKEY in the zone

Key tagRoleAlgorithm
29635KSK (257)ECDSAP256SHA256 (13)
48113ZSK (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 29635 (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-21 15:40 UTC and expires at 2026-10-23 17:40 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

info

17 records at the apex

Found

Read from
13.107.236.2:53
TypeValueTTL
SOAns1-02.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-02.azure-dns.com.172800
NSns2-02.azure-dns.net.172800
NSns3-02.azure-dns.org.172800
NSns4-02.azure-dns.info.172800
A195.177.80.76900
MX0 toyota-nl.mail.protection.outlook.com.3600
TXT"google-site-verification=oieOIJWBDQqH6-eWMu6POlq0FGAehIPLMcIhrNEx6nk"900
TXT"_yxgo3qcjakli61r1azsfq86pdd0nukq"900
TXT"_7frchiupxe42yyjlz0elb5fvaau7l92"900
TXT"8slt1w6z9r3mvts91m44t153l606m7y1"900
TXT"facebook-domain-verification=ayf8pwfjmx15uu2rck3f4zogty6gia"900
TXT"atlassian-domain-verification=yaW0kyKKh4HQVhVajObY0/8dd6ApennfZRXRZu53Po/9HOaJr4mIChqDKzj7qaXp"900
TXT"google-site-verification=-CICEzsuV1vlhZqfim9MclcjSShzQV4tfIdriqW6aww"900
TXT"qlh24lfpq5m7z4m4n7f9l88nxz94lfzt"900
TXT"onetrust-domain-verification=e1b711032e9c484689d81940288ce833"900
TXT"v=spf1 include:spf.protection.outlook.com include:_spf.smtp.com include:spf.flowmailer.net include:spf.trustit.eu include:spf.plan-it-online.com ip4:193.239.132.0/24 ip4:77.243.232.216 ip4:93.174.141.38 include:spf.privatehost.nl ip4:94.232.164.10 ip4:19" "5.177.80.26 ip4:195.177.80.25 ip4:93.117.251.9 -all"900

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, 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