beastingly.com - dns.ninja
beastingly.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=1783875152 | ||||||
Same first word
beastingly.com |
Similar names
DNS History
20 records (8 active, 12 former)
○NSdns082.d.register.com2016-08-10 → 2017-03-23 · 4 obs
● 2017-03-23 22:20:12
○ 2026-02-28 22:12:46
○ 2026-07-12 16:58:44
●NSdns1.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
○NSdns112.b.register.com2016-08-10 → 2017-03-23 · 4 obs
● 2017-03-23 22:20:12
○ 2026-02-28 22:12:46
○ 2026-07-12 16:58:44
○NSdns113.a.register.com2016-08-10 → 2017-03-23 · 4 obs
● 2017-03-23 22:20:12
○ 2026-02-28 22:12:46
○ 2026-07-12 16:58:44
●NSdns2.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
○NSdns233.c.register.com2016-08-10 → 2017-03-23 · 4 obs
● 2017-03-23 22:20:12
○ 2026-02-28 22:12:46
○ 2026-07-12 16:58:44
●MXeforward1.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
●MXeforward2.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
●MXeforward3.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
●MXeforward4.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
●MXeforward5.registrar-servers.com2026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
○MXmail.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○MXp.webcom.ctmail.com2017-03-23 → 2017-03-23 · 4 obs
● 2017-03-23 22:20:12
○ 2026-02-28 22:12:46
○ 2026-07-12 16:58:44
○MXsender01.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○MXsender02.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○MXsender03.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○MXsender04.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○MXsender05.beastingly.com2016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
○A107.190.168.1652016-08-10 → 2016-08-10 · 3 obs
○ 2017-03-23 22:20:12
○ 2026-07-12 16:58:44
●A192.64.119.1382026-02-28 → 2026-07-12 · 3 obs
● 2026-02-28 22:12:46
● 2026-07-12 16:58:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net... | - |
| beastingly.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for beastingly.com (unsigned zone)
⏱️ Timing
Total: 219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.64.119.138 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
beastingly.com has exactly one IP address — 192.64.119.138.
govomni.com, ppshealthcare.com, xn--reedom-2tb.com plus two other host names have IP numbers in common with beastingly.com.
Name Servers
Two name servers handle the delegation for beastingly.com: dns1.registrar-servers.com and dns2.registrar-servers.com.
The name server configuration of beastingly.com is shared with other domains, for instance buy4wall.com, xn--65bq1c.com, facundovillaveiran.com and two others.
beastingly.com shares at least some of its name servers with domains including moodback.com, kilima.org and videophile.net
These name servers are frequently paired with the name servers dns3.registrar-servers.com and dns4.registrar-servers.com.
dns1.registrar-servers.com and dns2.registrar-servers.com both carry two IP addresses. The A records for dns1.registrar-servers.com are 156.154.132.200 and 2610:a1:1024::200; the A records for dns2.registrar-servers.com are 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
beastingly.com is handled by five mail servers: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
At least some of the mail servers used by beastingly.com are shared with other domains: montanabondingcompany.com, attractiveape.com, yourseoguy.com and two others among them.
These mail servers often appear in conjunction with the mail servers eforward4.registrar-servers.com, eforward5.registrar-servers.com, eforward6.registrar-servers.com and eforward7.registrar-servers.com.
Host names resolving to a single IP address:
The hostname eforward1.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward2.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward3.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward4.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward5.registrar-servers.com resolves to 162.255.118.51.
Three host names point to 162.255.118.51: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
eforward2.registrar-servers.com along with eforward4.registrar-servers.com each resolve to 162.255.118.52 IP addresses.