bookingbot.com - dns.ninja
bookingbot.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=1783085056 | ||||||
Subdomains
mx.bookingbot.com |
Same first word
bookingbot.com |
bookingbot.cloud |
DNS History
8 records (6 active, 2 former)
●NSns1.fatcow.com2015-07-20 → 2026-07-03 · 2 obs
● 2026-07-03 13:40:30
●NSns1.mydomain.com2026-03-25 → 2026-07-03 · 3 obs
● 2026-03-25 07:08:14
● 2026-07-03 13:40:30
●NSns2.fatcow.com2015-07-20 → 2026-07-03 · 2 obs
● 2026-07-03 13:40:30
●NSns2.mydomain.com2026-03-25 → 2026-07-03 · 3 obs
● 2026-03-25 07:08:14
● 2026-07-03 13:40:30
●MXmx.bookingbot.com2015-07-20 → 2026-07-03 · 5 obs
● 2026-06-16 16:36:16
○ 2026-06-19 03:26:06
● 2026-06-22 03:27:36
● 2026-07-03 13:40:30
○A65.254.227.2242016-06-21 → 2017-02-13 · 5 obs
● 2016-06-21 00:41:12
● 2017-02-13 13:21:50
○ 2019-02-10 16:48:10
○ 2026-07-03 13:40:30
●A65.254.248.1432019-02-10 → 2026-07-03 · 6 obs
● 2019-02-10 16:48:10
● 2026-06-16 16:36:16
○ 2026-06-19 03:26:06
● 2026-06-22 03:27:36
● 2026-07-03 13:40:30
○A65.254.248.1992015-07-20 → 2016-02-26 · 4 obs
● 2016-02-26 05:54:52
○ 2016-06-21 00:41:12
○ 2026-07-03 13:40:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bookingbot.com | ns1.mydomain.com, ns2.mydomain.com | 2 records |
✅ Authoritative Response
Server:172.64.52.99
NS records: ns1.mydomain.com, ns2.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bookingbot.com (unsigned zone)
⏱️ Timing
Total: 251ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.254.248.143 |
| NS | 2 | ns1.fatcow.com, ns2.fatcow.com |
| MX | 1 | mx.bookingbot.com (pri: 30) |
| TXT | 1 | v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0 |
| SOA | 1 | ns1.fatcow.com dnsadmin.fatcow.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.mydomain.com, ns2.mydomain.com)
Analysis
Hierarchy
The domain mx.bookingbot.com falls under the parent bookingbot.com.
IP Addresses
bookingbot.com resolves to one IP address: 65.254.248.143.
ivoltd.com, incigesas.com, harmonsquad.com and two other host names share IP numbers with bookingbot.com.
Name Servers
The authoritative name servers for bookingbot.com are ns1.fatcow.com, ns2.fatcow.com, ns1.mydomain.com and ns2.mydomain.com.
At least some of bookingbot.com's name servers are shared with other domains, for example worldbookbank.com, financefitnesscentral.com, bgcinn.com and two more.
It is common to find these name servers alongside the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and two others.
Each of the four hosts ns1.fatcow.com, ns2.fatcow.com, ns1.mydomain.com and ns2.mydomain.com points to a single IP address — ns1.fatcow.com points to 65.254.254.100, ns2.fatcow.com points to 65.254.254.101, ns1.mydomain.com points to 172.64.52.99 and ns2.mydomain.com points to 172.64.53.76.
Mail Servers
Mail for bookingbot.com is handled by a single mail server, mx.bookingbot.com.
mx.bookingbot.com resolves to 6 IP addresses — 65.254.254.50, 65.254.254.51, 65.254.254.52 and 3 others.