hotels.nl

Checked 22 October 2026, 13:51 UTC · via 8.8.8.8
✗Problems found
17 passed 4 warnings 1 failed 7 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.realtime-hotels.com, ns2.realtime-hotels.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.realtime-hotels.com, ns2.realtime-hotels.com
NS in the zone
ns1.realtime-hotels.com, ns2.realtime-hotels.com
NameserverAddressesNetwork (AS)Glue
ns1.realtime-hotels.com185.40.57.243AS30870 TRANS-IX-AS - Trans-iX B.V., NL-
ns2.realtime-hotels.com37.97.136.143AS20857 TRANSIP-AS - Signet B.V., NL-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.realtime-hotels.com, ns2.realtime-hotels.com.
    #6
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20857 (TRANSIP-AS - Signet B.V., NL): 1 address; AS30870 (TRANS-IX-AS - Trans-iX B.V., NL): 1 address.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.realtime-hotels.com 185.40.57.243no responsenono / no--
ns2.realtime-hotels.com 37.97.136.143NOERROR, 11 ms, authoritativenoyes / yesrefusedTrans-iX B.V.

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.realtime-hotels.com (185.40.57.243): read udp 46.225.38.91:45714->185.40.57.243:53: i/o timeout.
    #14
  • ✓ 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: ns2.realtime-hotels.com: "Trans-iX B.V.".
    #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

warn

serial 2026092605 · primary ns1.realtime-hotels.com

Found

Primary (MNAME)
ns1.realtime-hotels.com
Contact (RNAME)
hostmaster.hotels.nl
Serial
2026092605
Refresh / retry
60 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Checks

  • ✓ Serial 2026092605 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 1m is outside 20m–1d; retry 1h should be shorter than refresh 1m. Current values: refresh 1m, retry 1h, expire 14d, negative TTL 1d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.realtime-hotels.com is one of the listed nameservers.
  • ✓ Contact hostmaster@hotels.nl #25
    The SOA RNAME hostmaster.hotels.nl means hostmaster@hotels.nl.
  • ✓ Date-based serial #26
    The serial 2026092605 follows the YYYYMMDDnn convention (2026-09-26).

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
37.97.136.143:53
TypeValueTTL
SOAns1.realtime-hotels.com. hostmaster.hotels.nl. 2026092605 60 3600 1209600 8640060
NSns1.realtime-hotels.com.60
NSns2.realtime-hotels.com.60
A193.222.137.1060
MX5 ALT1.ASPMX.L.GOOGLE.COM.60
MX10 ALT3.ASPMX.L.GOOGLE.COM.60
MX1 ASPMX.L.GOOGLE.COM.60
MX30 ASPMX2.GOOGLEMAIL.COM.60
MX10 ALT4.ASPMX.L.GOOGLE.COM.60
MX5 ALT2.ASPMX.L.GOOGLE.COM.60
TXT"v=spf1 include:_spf.enem.nl include:mail.hotels.nl include:_spf.google.com -all"60
TXT"google-site-verification=-764hb9qcaOde576XTfKvpWwFDlooeEog61DKdLumaw"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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