botspace.com - dns.ninja
botspace.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns1.yourhostingaccount.com ⚠️ Not in parent delegation | ||||||
| A | 65.254.254.102🇺🇸 EIG-2987365.254.224.0/19 Newfold Digital, Inc. | ||||||
| PTR | ns1.yourhostingaccount.com | ||||||
| NS | ns2.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.yourhostingaccount.com ⚠️ Not in parent delegation | ||||||
| A | 65.254.254.155🇺🇸 EIG-2987365.254.224.0/19 Newfold Digital, Inc. | ||||||
| PTR | ns2.yourhostingaccount.com | ||||||
| NS | ns3.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns4.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
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=1785290017 | ||||||
Same first word
Similar names
DNS History
16 records (6 active, 10 former)
●NSns1.mydomain.com2008-03-18 → 2026-07-29 · 5 obs
○ 2015-05-15 16:39:52
○ 2020-04-07 10:13:02
● 2026-03-08 20:27:02
● 2026-07-29 02:08:56
●NSns1.yourhostingaccount.com2015-05-15 → 2026-07-29 · 5 obs
● 2015-05-15 16:39:52
● 2020-04-07 10:13:02
○ 2026-06-26 17:50:00
● 2026-07-29 02:08:56
●NSns2.mydomain.com2008-03-18 → 2026-07-29 · 5 obs
○ 2015-05-15 16:39:52
○ 2020-04-07 10:13:02
● 2026-03-08 20:27:02
● 2026-07-29 02:08:56
●NSns2.yourhostingaccount.com2015-05-15 → 2026-07-29 · 5 obs
● 2015-05-15 16:39:52
● 2020-04-07 10:13:02
○ 2026-06-26 17:50:00
● 2026-07-29 02:08:56
●NSns3.mydomain.com2008-03-18 → 2026-07-29 · 5 obs
○ 2015-05-15 16:39:52
○ 2020-04-07 10:13:02
● 2026-03-08 20:27:02
● 2026-07-29 02:08:56
●NSns4.mydomain.com2008-03-18 → 2026-07-29 · 5 obs
○ 2015-05-15 16:39:52
○ 2020-04-07 10:13:02
● 2026-03-08 20:27:02
● 2026-07-29 02:08:56
○MXm1.dnsix.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○MXmx.botspace.com2015-05-15 → 2020-04-07 · 5 obs
● 2015-05-15 16:39:52
● 2020-04-07 10:13:02
○ 2026-06-26 17:50:00
○ 2026-07-29 02:08:56
○A66.150.161.1332008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A66.150.161.1362008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A66.150.161.1412008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A69.25.27.1702008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A69.25.27.1712008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A69.25.27.1722008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A69.25.27.1732008-03-18 → 2008-03-18 · 3 obs
○ 2015-05-15 16:39:52
○ 2026-07-29 02:08:56
○A76.74.137.1652015-05-15 → 2020-04-07 · 5 obs
● 2015-05-15 16:39:52
● 2020-04-07 10:13:02
○ 2026-06-26 17:50:00
○ 2026-07-29 02:08:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| botspace.com | ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com, ns4.mydomain.com | 4 records |
✅ Authoritative Response
Server:172.64.52.99
NS records: ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com, ns4.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for botspace.com (unsigned zone)
⏱️ Timing
Total: 3343ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com...)
Analysis
Name Servers
botspace.com carries NS records listing 6 name servers — ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com and 3 others.
At least some of botspace.com's name servers are shared with other domains, for example austindiver.com, chowdary.net, wetlake.com and two more.
These name servers tend to co-occur with ns1.yourhostingaccount.com, ns2.yourhostingaccount.com, ns4.mydomain.com and 7 other name servers in the same DNS delegations.
Host names that point to one IP address:
ns1.mydomain.com resolves to the IP address 172.64.52.99.
ns2.mydomain.com resolves to the IP address 172.64.53.76.
ns3.mydomain.com resolves to the IP address 172.64.52.99.
ns4.mydomain.com resolves to the IP address 172.64.53.76.
ns1.yourhostingaccount.com resolves to the IP address 65.254.254.102.
ns2.yourhostingaccount.com resolves to the IP address 65.254.254.155.
ns1.mydomain.com and ns3.mydomain.com each have 172.64.52.99 IP addresses.
ns2.mydomain.com and ns4.mydomain.com each have 172.64.53.76 IP addresses.