interparking.nl

Checked 22 October 2026, 13:52 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 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/interparking.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/interparking.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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-02.azure-dns.com 13.107.236.2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1-02.azure-dns.com 2603:1061:0:700::2NOERROR, 4 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 / yesrefused-
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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2020112300 · primary ns1-02.azure-dns.com

Found

Primary (MNAME)
ns1-02.azure-dns.com
Contact (RNAME)
username.example.com
Serial
2020112300
Refresh / retry
7200 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1-02.azure-dns.com (13.107.236.2)2020112300
ns1-02.azure-dns.com (2603:1061:0:700::2)2020112300
ns2-02.azure-dns.net (150.171.21.2)2020112300
ns2-02.azure-dns.net (2620:1ec:8ec:700::2)2020112300
ns3-02.azure-dns.org (204.14.183.2)2020112300
ns3-02.azure-dns.org (2a01:111:4000:700::2)2020112300
ns4-02.azure-dns.info (208.84.5.2)2020112300
ns4-02.azure-dns.info (2620:1ec:bda:700::2)2020112300

Checks

  • ✓ Serial 2020112300 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-02.azure-dns.com is one of the listed nameservers.
  • ✓ Contact username@example.com #25
    The SOA RNAME username.example.com means username@example.com.
  • ✓ Date-based serial #26
    The serial 2020112300 follows the YYYYMMDDnn convention (2020-11-23).

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

warn

16 records at the apex

Found

Read from
13.107.236.2:53
TypeValueTTL
SOAns1-02.azure-dns.com. username.example.com. 2020112300 7200 3600 1209600 36003600
NSns1-02.azure-dns.com.172800
NSns2-02.azure-dns.net.172800
NSns3-02.azure-dns.org.172800
NSns4-02.azure-dns.info.172800
A150.171.109.10110
MX0 interparking-nl.mail.protection.outlook.com.3600
TXT"MS=ms86008646"3600
TXT"www=6cd001cd9de9115c2dc8b638d02632cc"3600
TXT"v=spf1 mx ip4:94.140.172.21 ip4:193.46.190.100 ip4:145.128.243.31 include:spf.protection.outlook.com include:servers.mcsv.net include:spf.afas.online include:_spf.cobytes.email include:_spf.salesforce.com -all"3600
TXT"google-site-verification=einBtm6xwJ2FkOOU_L0tJPiR_vjB-C_iarLucECX7cs"3600
TXT"google-site-verification=JQ3FVk5yMi-j7Lz5fT_1w3oGqZFGgBAf0ShseIDYdSo"3600
TXT"_globalsign-domain-verification=LWq8qLGEFZsbePW0Jw5gfTankLSuSkaXO1gcTjVU6a"3600
TXT"ms-domain-verification=0003b0f0-b3db-4594-95db-c53edcf4eb6b"3600
TXT"mandrill_verify.Gc9fA2UUNLTbV8TEC_nT-w"3600
TXT"ms-domain-verification=6c7fba65-d939-478e-8a5b-b06b139974c9"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (10s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
    #32
  • ✓ 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