ns1.beatingbets.com - robtex.com
ns1.beatingbets.com
| DNSSEC | โ ๏ธ Not signed | ||||||
| A | 92.205.229.98๐ฉ๐ช GODADDY-SXB92.205.224.0/19 | ||||||
| PTR | 98.229.205.92.host.secureserver.net | ||||||
beatingbets.com
| DNSSEC | โ ๏ธ Not signed | ||||||
| A | 92.205.229.98๐ฉ๐ช GODADDY-SXB92.205.224.0/19 | ||||||
| NS | ns1.cprapid.com โญ | ||||||
| NS | n1.beatingbets.com โ ๏ธ Not in zone NS records | ||||||
| NS | n2.beatingbets.com โ ๏ธ Not in zone NS records | ||||||
| NS | ns1.beatingbets.com โ ๏ธ Not in parent delegation | ||||||
| NS | ns2.beatingbets.com โ ๏ธ Not in parent delegation | ||||||
| MX | beatingbets.com โญ | ||||||
| TXT | google-site-verification=Rs4hD2HI-YueYcpk46eef_KjgSVDA_4hxI9SAGTdKTE | ||||||
| TXT | v=spf1 +a +mx +ip4:92.205.31.151 +ip4:92.205.229.98 +include:secureserver.net... | ||||||
| SOA | ns1.cprapid.comroot@151.31.205.92.host.secureserver.net 2026-02-19 #1 | ||||||
NS for
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
โA92.205.229.982026-03-24 โ 2026-03-25 ยท 2 obs
โ 2026-03-24 10:30:10
โ 2026-03-25 01:02:52
โ 2026-03-25 01:02:52
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net... | - |
| beatingbets.com | n1.beatingbets.com, n2.beatingbets.com | 2 records |
โ Authoritative Response
Server:92.205.229.98
NS records: n1.beatingbets.com, n2.beatingbets.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for beatingbets.com (unsigned zone)
โฑ๏ธ Timing
Total: 302ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 92.205.229.98 |
๐ Glue Records Collected
Total: 2
In-bailiwick: 2 (n1.beatingbets.com, n2.beatingbets.com)
Analysis
Name Server Role
ns1.beatingbets.com serves as the name server for beatingbets.com.
ns2.beatingbets.com, n1.beatingbets.com and n2.beatingbets.com commonly serve as name servers alongside ns1.beatingbets.com.
IP Addresses
ns1.beatingbets.com maps to IP address 92.205.229.98.
Other host names, for example beatingbets.com, 98.229.205.92.host.secureserver.net and ns2.beatingbets.com share the same IP as ns1.beatingbets.com.