beatdata.com - dns.ninja
beatdata.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns2.afternic.com ⭐ | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | ns1.afternic.com | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns2.afternic.comdns@jomax.net serial=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=1785047517 | ||||||
Same first word
beatdata.com |
Similar names
databeat.io |
betadata.ai |
betadata.com |
databeta.in |
betadata.dev |
databeat.net |
tebadata.com |
databeta.io |
betadata.se |
betadata.eu |
databeat.co.in |
databeat.com |
etabdata.com |
DNS History
20 records (4 active, 16 former)
○NSlaunch1.spaceship.net2026-06-13 → 2026-06-13 · 4 obs
○ 2026-05-29 10:43:24
● 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○NSlaunch2.spaceship.net2026-06-13 → 2026-06-13 · 4 obs
○ 2026-05-29 10:43:24
● 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
●NSns1.afternic.com2026-04-09 → 2026-07-26 · 4 obs
● 2026-04-09 09:58:00
○ 2026-05-29 10:43:24
● 2026-07-26 06:42:12
○NSns1.atom.com2026-05-29 → 2026-05-29 · 4 obs
● 2026-05-29 10:43:24
○ 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○NSns1.sapin.arvixe.com2015-06-05 → 2015-10-23 · 4 obs
● 2015-10-23 10:55:02
○ 2019-03-05 18:59:54
○ 2026-07-26 06:42:12
○NSns1.undeveloped.com2019-03-05 → 2019-03-05 · 4 obs
● 2019-03-05 18:59:54
○ 2026-04-09 09:58:00
○ 2026-07-26 06:42:12
●NSns2.afternic.com2026-04-09 → 2026-07-26 · 4 obs
● 2026-04-09 09:58:00
○ 2026-05-29 10:43:24
● 2026-07-26 06:42:12
○NSns2.atom.com2026-05-29 → 2026-05-29 · 4 obs
● 2026-05-29 10:43:24
○ 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○NSns2.sapin.arvixe.com2015-06-05 → 2015-10-23 · 4 obs
● 2015-10-23 10:55:02
○ 2019-03-05 18:59:54
○ 2026-07-26 06:42:12
○NSns2.undeveloped.com2019-03-05 → 2019-03-05 · 4 obs
● 2019-03-05 18:59:54
○ 2026-04-09 09:58:00
○ 2026-07-26 06:42:12
○MXmail.beatdata.com2015-06-05 → 2015-10-23 · 4 obs
● 2015-10-23 10:55:02
○ 2019-03-05 18:59:54
○ 2026-07-26 06:42:12
○MXmail2.beatdata.com2015-06-05 → 2015-10-23 · 4 obs
● 2015-10-23 10:55:02
○ 2019-03-05 18:59:54
○ 2026-07-26 06:42:12
○MXmx.beatdata.com2019-03-05 → 2019-03-05 · 4 obs
● 2019-03-05 18:59:54
○ 2026-04-09 09:58:00
○ 2026-07-26 06:42:12
●A13.248.169.482026-04-09 → 2026-07-26 · 4 obs
● 2026-04-09 09:58:00
○ 2026-05-29 10:43:24
● 2026-07-26 06:42:12
○A2a05:d014:9da:8c10:306e:3e07:a16f:a5522019-03-05 → 2019-03-05 · 3 obs
○ 2026-04-09 09:58:00
○ 2026-07-26 06:42:12
○A44.232.173.2492026-06-13 → 2026-06-13 · 4 obs
○ 2026-05-29 10:43:24
● 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○A52.20.84.622026-05-29 → 2026-05-29 · 4 obs
● 2026-05-29 10:43:24
○ 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○A52.40.42.1132026-06-13 → 2026-06-13 · 4 obs
○ 2026-05-29 10:43:24
● 2026-06-13 23:29:16
○ 2026-07-26 06:42:12
○A52.58.78.162019-03-05 → 2019-03-05 · 3 obs
○ 2026-04-09 09:58:00
○ 2026-07-26 06:42:12
●A76.223.54.1462026-04-09 → 2026-07-26 · 4 obs
● 2026-04-09 09:58:00
○ 2026-05-29 10:43:24
● 2026-07-26 06:42:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, d.gtld-servers.net... | - |
| beatdata.com | ns1.afternic.com, ns2.afternic.com | 4 records |
✅ Authoritative Response
Server:173.201.66.69
NS records: ns1.afternic.com, ns2.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for beatdata.com (unsigned zone)
⏱️ Timing
Total: 220ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns2.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)
Analysis
IP Addresses
beatdata.com has two IP addresses: 13.248.169.48 and 76.223.54.146
77w7.com, manhattanexterminating.com, capitalstrong.xyz and two other host names share IP numbers with beatdata.com.
Name Servers
DNS delegation for beatdata.com points to two name servers: ns1.afternic.com and ns2.afternic.com.
beatdata.com uses the same name servers as several other domains — among them cryses.com, expensivelife.com, salevic.com and two more.
There is at least partial name server overlap between beatdata.com and other domains — credift.com, worki.net, schedulercli.com and two more among them.
It is common to find these name servers alongside the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-urj2ap2akmgcchkhharttb.ns101.verify.hn, verification-ebko7hoqoyqcm4wvfhcuax.ns101.verify.hn and two others.
ns1.afternic.com directs to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com directs to 173.201.66.69 and 2603:5:2226::45. Each host name carries two IP addresses.