botdom.com - dns.ninja
botdom.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=1786940619 | ||||||
Subdomains
www.botdom.com |
Same first word
botdom.com |
Similar names
DNS History
18 records (9 active, 9 former)
●NSns1.digitalocean.com2026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
○NSns1.mediatemple.net2008-03-13 → 2017-01-22 · 4 obs
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
●NSns2.digitalocean.com2026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
○NSns2.mediatemple.net2008-03-13 → 2017-01-22 · 4 obs
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
●NSns3.digitalocean.com2026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
●MXalt1.aspmx.l.google.com2015-06-23 → 2026-08-17 · 3 obs
● 2015-06-23 09:02:00
● 2026-08-17 04:42:52
●MXalt2.aspmx.l.google.com2015-06-23 → 2026-08-17 · 3 obs
● 2015-06-23 09:02:00
● 2026-08-17 04:42:52
●MXalt3.aspmx.l.google.com2026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
●MXalt4.aspmx.l.google.com2026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
●MXaspmx.l.google.com2015-06-23 → 2026-08-17 · 3 obs
● 2015-06-23 09:02:00
● 2026-08-17 04:42:52
○MXaspmx2.googlemail.com2015-06-23 → 2017-01-22 · 5 obs
● 2015-06-23 09:02:00
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
○MXaspmx3.googlemail.com2015-06-23 → 2017-01-22 · 5 obs
● 2015-06-23 09:02:00
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
○MXaspmx4.googlemail.com2015-06-23 → 2017-01-22 · 5 obs
● 2015-06-23 09:02:00
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
○MXaspmx5.googlemail.com2015-06-23 → 2017-01-22 · 5 obs
● 2015-06-23 09:02:00
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
○MXmail.botdom.com2008-03-13 → 2008-03-13 · 3 obs
○ 2015-06-23 09:02:00
○ 2026-08-17 04:42:52
●A167.172.42.1712026-02-27 → 2026-08-17 · 3 obs
● 2026-02-27 05:06:04
● 2026-08-17 04:42:52
○A64.13.227.242008-03-13 → 2008-03-13 · 3 obs
○ 2015-06-23 09:02:00
○ 2026-08-17 04:42:52
○A72.47.228.2012015-06-23 → 2017-01-22 · 5 obs
● 2015-06-23 09:02:00
● 2017-01-22 15:24:16
○ 2026-02-27 05:06:04
○ 2026-08-17 04:42:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net... | - |
| botdom.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for botdom.com (unsigned zone)
⏱️ Timing
Total: 229ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 167.172.42.171 |
| NS | 3 | ns1.digitalocean.com, ns2.digitalocean.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| SOA | 1 | ns1.digitalocean.com hostmaster.botdom.c |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
Hierarchy
botdom.com serves as the parent of www.botdom.com.
IP Addresses
botdom.com resolves to one IP address: 167.172.42.171.
mail.24bps.com, andreasgraulund.com, www.botdom.com and two other host names share IP numbers with botdom.com.
Name Servers
botdom.com has three name servers — ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
botdom.com has at least partial name server overlap with other domains, such as wepg.online, hwsg.com, centroeducativoendaragalimany.com and two others.
Each of ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com points to two IP numbers. ns1.digitalocean.com points to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com points to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com points to 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
Mail for botdom.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
botdom.com has at least partial mail server overlap with other domains such as airbbus.com, ns500759.ns500698.ns500758.ns500698.ns500736.ns500735.ns500698.ns500708.ns500708.ns500576.ns500698.tracksymphony.com, gestionmax.fr and two more.
The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to 173.194.45.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.