why-hotel.com - robtex.com
why-hotel.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1777294586 | ||||||
Same first word
why-hotel.com |
DNS History
10 records (7 active, 3 former)
●MXmx01.cloud.vadesecure.com2026-02-20 → 2026-04-27 · 3 obs
● 2026-02-20 13:24:10
● 2026-04-27 13:05:52
○MXmx01.vaderetro-cloud.net2015-08-09 → 2017-03-30 · 4 obs
● 2017-03-30 08:46:52
○ 2026-02-20 13:24:10
○ 2026-04-27 13:05:52
●MXmx02.cloud.vadesecure.com2026-02-20 → 2026-04-27 · 3 obs
● 2026-02-20 13:24:10
● 2026-04-27 13:05:52
○MXmx02.vaderetro-cloud.net2015-08-09 → 2017-03-30 · 4 obs
● 2017-03-30 08:46:52
○ 2026-02-20 13:24:10
○ 2026-04-27 13:05:52
●MXmx03.cloud.vadesecure.com2026-02-20 → 2026-04-27 · 3 obs
● 2026-02-20 13:24:10
● 2026-04-27 13:05:52
●MXmx04.cloud.vadesecure.com2026-02-20 → 2026-04-27 · 3 obs
● 2026-02-20 13:24:10
● 2026-04-27 13:05:52
●A85.236.158.1862026-02-20 → 2026-04-27 · 3 obs
● 2026-02-20 13:24:10
● 2026-04-27 13:05:52
○A94.125.167.2172015-08-09 → 2017-03-30 · 4 obs
● 2017-03-30 08:46:52
○ 2026-02-20 13:24:10
○ 2026-04-27 13:05:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| why-hotel.com | dns100.ovh.net, ns100.ovh.net | - |
✅ Authoritative Response
Server:5.135.44.185
NS records: dns100.ovh.net, ns100.ovh.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for why-hotel.com (unsigned zone)
⏱️ Timing
Total: 571ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 85.236.158.186 |
| NS | 2 | ns100.ovh.net, dns100.ovh.net |
| MX | 4 | mx04.cloud.vadesecure.com (pri: 10), mx02.cloud.vadesecure.com (pri: 10)... |
| TXT | 5 | brevo-code:a58b43611446a616b82b7efb9cd92, MS=ms84228280... |
| SOA | 1 | dns100.ovh.net tech.ovh.net |
Analysis
IP Addresses
why-hotel.com points to a single IP address: 85.236.158.186.
Other host names such as canufix.com, winecity.fr, eliazarconcept.com, 3adt.com and iampox.com share IP numbers with why-hotel.com.
Name Servers
why-hotel.com is delegated to two name servers: dns100.ovh.net and ns100.ovh.net.
why-hotel.com uses the same name server setup as other domains, including maniere-noire.com, prodenplaqueoff.eu, xn--ativaao-netflixpt-esb.com, peugeot-valence.fr and ip-94-23-106.eu.
Host names with two IP numbers:
dns100.ovh.net points to 2001:41d0:d00:fa00::2 and 5.135.250.177.
ns100.ovh.net points to 2001:41d0:b00:f400::2 and 5.135.44.185.
Mail Servers
why-hotel.com is handled by four mail servers: mx01.cloud.vadesecure.com, mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com and mx04.cloud.vadesecure.com.
why-hotel.com shares at least some mail servers with other domains, for example d-e.fr, ville-lieusaint.fr, auto-addict.fr, fourviere.org and pcrfamily.com.
Host names with one IP: mx01.cloud.vadesecure.com points to 163.172.240.110; mx02.cloud.vadesecure.com points to 163.172.240.111; mx03.cloud.vadesecure.com points to 135.125.122.66; mx04.cloud.vadesecure.com points to 135.125.122.67.