inntelhotels.nl

Checked 22 October 2026, 13:52 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 1 failed 6 info

Registration

info

.nl country-code

Found

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

Delegation

fail

ns0.ndi.nl, ns1.ndi.nl, ns3.ndi.nu, ns4.ndi.nu

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns0.ndi.nl, ns1.ndi.nl, ns3.ndi.nu, ns4.ndi.nu
NS in the zone
ns0.ndi.nl, ns1.ndi.nl, ns3.ndi.nu, ns4.ndi.nu
NameserverAddressesNetwork (AS)Glue
ns0.ndi.nl217.160.80.161 2001:8d8:fe:53:217:160:80:161AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
ns1.ndi.nl217.160.81.161 2001:8d8:fe:53:217:160:81:161AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
ns3.ndi.nu(does not resolve)-
ns4.ndi.nu(does not resolve)-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns0.ndi.nl, ns1.ndi.nl, ns3.ndi.nu, ns4.ndi.nu.
  • ✓ 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.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns3.ndi.nu, ns4.ndi.nu.
    #9
  • i
    One address family in one network
    all IPv6 addresses are in 2001:8d8:fe::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8560 (IONOS-AS - IONOS SE, DE): 4 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 2 TLDs #12
    Nameserver names use the TLDs .nl, .nu.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.ndi.nl 217.160.80.161NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns0.ndi.nl 2001:8d8:fe:53:217:160:80:161NOERROR, 10 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.ndi.nl 217.160.81.161NOERROR, 10 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.ndi.nl 2001:8d8:fe:53:217:160:81:161NOERROR, 10 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

Checks

  • ✓ All respond #14
    All 4 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns0.ndi.nl: "Served by PowerDNS - https://www.powerdns.com/"; ns1.ndi.nl: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2025112120 · primary ns0.ndi.nl

Found

Primary (MNAME)
ns0.ndi.nl
Contact (RNAME)
hostmaster.kixtart.nl
Serial
2025112120
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns0.ndi.nl (217.160.80.161)2025112120
ns0.ndi.nl (2001:8d8:fe:53:217:160:80:161)2025112120
ns1.ndi.nl (217.160.81.161)2025112120
ns1.ndi.nl (2001:8d8:fe:53:217:160:81:161)2025112120

Checks

  • ✓ Serial 2025112120 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.ndi.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@kixtart.nl #25
    The SOA RNAME hostmaster.kixtart.nl means hostmaster@kixtart.nl.
  • ✓ Date-based serial #26
    The serial 2025112120 follows the YYYYMMDDnn convention (2025-11-21).

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

12 records at the apex

Found

Read from
217.160.80.161:53
TypeValueTTL
SOAns0.ndi.nl. hostmaster.kixtart.nl. 2025112120 43200 7200 1209600 8640086400
NSns1.ndi.nl.86400
NSns4.ndi.nu.86400
NSns3.ndi.nu.86400
NSns0.ndi.nl.86400
A161.35.153.229180
MX0 inntelhotels-nl.mail.protection.outlook.com.300
TXT"google-site-verification=pw2i95BX8862oWyQvsvr8k9gdMZJOfb8Y65UAyIV9pY"180
TXT"ms-domain-verification=3957f249-c7ba-4227-a921-b534c4173815"180
TXT"MS=E0F879B1A7AAD11FBD8FF15B36E4690C48A10A93"180
TXT"v=spf1 ip4:62.204.74.183 include:spf.afas.online include:spf.protection.outlook.com include:spf.synxis.com include:_spf.mijnmaks.nl include:_spf.smtp.com include:spf_hotellocaties.inntelhotels.nl include:spf2.inntelhotels.nl -all"180
TXT"MS=ms11717755"180

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m). 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.
  • ✓ 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