hotelcms.com - dns.ninja
hotelcms.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 86.105.245.69🇳🇱 TRANSIP-AS86.105.244.0/22 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 86-105-245-69.haip.transip.net | ||||||
| NS | ns1.eftydns.com ⭐ | ||||||
| A | 87.253.137.197🇳🇱 TRANSIP-AS87.253.128.0/19 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 87-253-137-197.colo.transip.net | ||||||
| NS | ns2.eftydns.com | ||||||
| A | 136.144.254.183🇳🇱 TRANSIP-AS136.144.128.0/17 TransIP BV Amsterdam, The Netherlands | ||||||
| PTR | 136-144-254-183.colo.transip.net | ||||||
| SOA | ns1.eftydns.comhostmaster@hotelcms.com 2026-08-13 #1 | ||||||
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=1786749414 | ||||||
Same first word
Similar names
DNS History
14 records (3 active, 11 former)
○NSbuy.internettraffic.com2016-03-08 → 2016-06-26 · 5 obs
○ 2015-07-17 22:07:38
● 2016-03-08 08:22:10
● 2016-06-26 01:16:18
○ 2017-03-14 09:04:48
○ 2026-08-14 23:19:54
● 2016-03-08 08:22:10
● 2016-06-26 01:16:18
○ 2017-03-14 09:04:48
○ 2026-08-14 23:19:54
○NSns1.digitalocean.com2015-07-17 → 2015-07-17 · 3 obs
● 2015-07-17 22:07:38
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
●NSns1.eftydns.com2026-02-19 → 2026-08-14 · 3 obs
○ 2020-04-06 17:25:38
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
○NSns1.uniregistrymarket.link2017-03-14 → 2020-04-06 · 5 obs
○ 2016-06-26 01:16:18
● 2017-03-14 09:04:48
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
● 2017-03-14 09:04:48
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
○NSns2.digitalocean.com2015-07-17 → 2015-07-17 · 3 obs
● 2015-07-17 22:07:38
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
●NSns2.eftydns.com2026-02-19 → 2026-08-14 · 3 obs
○ 2020-04-06 17:25:38
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
○NSns2.uniregistrymarket.link2017-03-14 → 2020-04-06 · 5 obs
○ 2016-06-26 01:16:18
● 2017-03-14 09:04:48
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
● 2017-03-14 09:04:48
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
○NSns3.digitalocean.com2015-07-17 → 2015-07-17 · 3 obs
● 2015-07-17 22:07:38
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
○NSsell.internettraffic.com2016-03-08 → 2016-06-26 · 5 obs
○ 2015-07-17 22:07:38
● 2016-03-08 08:22:10
● 2016-06-26 01:16:18
○ 2017-03-14 09:04:48
○ 2026-08-14 23:19:54
● 2016-03-08 08:22:10
● 2016-06-26 01:16:18
○ 2017-03-14 09:04:48
○ 2026-08-14 23:19:54
○A184.168.221.532015-07-17 → 2015-07-17 · 3 obs
● 2015-07-17 22:07:38
○ 2015-12-02 15:52:32
○ 2026-08-14 23:19:54
○ 2015-12-02 15:52:32
○ 2026-08-14 23:19:54
○A69.172.201.1532016-06-26 → 2020-04-06 · 5 obs
○ 2016-03-08 08:22:10
● 2016-06-26 01:16:18
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
● 2016-06-26 01:16:18
● 2020-04-06 17:25:38
○ 2026-02-19 17:08:50
○ 2026-08-14 23:19:54
○A69.172.201.2082016-03-08 → 2016-03-08 · 4 obs
○ 2015-12-02 15:52:32
● 2016-03-08 08:22:10
○ 2016-06-26 01:16:18
○ 2026-08-14 23:19:54
● 2016-03-08 08:22:10
○ 2016-06-26 01:16:18
○ 2026-08-14 23:19:54
○A69.64.147.2422015-12-02 → 2015-12-02 · 4 obs
○ 2015-07-17 22:07:38
● 2015-12-02 15:52:32
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
● 2015-12-02 15:52:32
○ 2016-03-08 08:22:10
○ 2026-08-14 23:19:54
●A86.105.245.692026-02-19 → 2026-08-14 · 3 obs
○ 2020-04-06 17:25:38
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
● 2026-02-19 17:08:50
● 2026-08-14 23:19:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net... | - |
| hotelcms.com | ns1.eftydns.com, ns2.eftydns.com | 2 records |
✅ Authoritative Response
Server:87.253.137.197
NS records: ns1.eftydns.com, ns2.eftydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hotelcms.com (unsigned zone)
⏱️ Timing
Total: 264ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 86.105.245.69 |
| NS | 2 | ns1.eftydns.com, ns2.eftydns.com |
| SOA | 1 | ns1.eftydns.com hostmaster.hotelcms.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.eftydns.com, ns2.eftydns.com)
Analysis
IP Addresses
hotelcms.com has exactly one IP address — 86.105.245.69.
mzizi.com, yudo.xyz, temzy.com plus two other host names have IP numbers in common with hotelcms.com.
Name Servers
hotelcms.com is delegated to two name servers: ns1.eftydns.com and ns2.eftydns.com.
The name server configuration of hotelcms.com is shared with other domains, for instance cuare.com, dnbq.com, openapp.com and two others.
Each of ns1.eftydns.com and ns2.eftydns.com has one IP address: ns1.eftydns.com uses 87.253.137.197 and ns2.eftydns.com uses 136.144.254.183.