beadinggem.com - robtex.com
beadinggem.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=1771291435 | ||||||
rank #246504 in the tld
WOT: UNKNOWN (70/100)
Up
mx.beadinggem.com |
Same first word
beadinggem.com |
Similar names
DNS History
11 records (9 active, 2 former)
●NSns1.netfirms.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●NSns1.yourhostingaccount.com2015-06-19 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●NSns2.netfirms.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●NSns2.yourhostingaccount.com2015-06-19 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●MXmx.beadinggem.com2015-06-19 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●A216.239.32.212026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●A216.239.34.212026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●A216.239.36.212026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
●A216.239.38.212026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 12:43:18
○A66.96.149.12015-09-26 → 2017-02-10 · 4 obs
● 2015-09-26 03:47:50
● 2017-02-10 09:51:04
○ 2026-02-27 12:43:18
○A66.96.160.1522015-06-19 → 2015-06-19 · 3 obs
○ 2015-09-26 03:47:50
○ 2026-02-27 12:43:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| beadinggem.com | ns1.netfirms.com, ns2.netfirms.com | 2 records |
✅ Authoritative Response
Server: 65.254.254.157
NS records: ns1.netfirms.com, ns2.netfirms.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for beadinggem.com (unsigned zone)
⏱️ Timing
Total: 127ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 216.239.38.21, 216.239.34.21... |
| NS | 2 | ns2.yourhostingaccount.com, ns1.yourhostingaccount.com |
| MX | 1 | mx.beadinggem.com (pri: 30) |
| TXT | 1 | v=spf1 include:spfa.mailendo.com ~all |
| SOA | 1 | ns1.yourhostingaccount.com admin.yourhos |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.netfirms.com, ns2.netfirms.com)
AI analysis
beadinggem.com is the parent of mx.beadinggem.com.
Four IP numbers are pointed to by beadinggem.com: 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
other host names including *.kajianpustaka.com, sprout.co.in, muck.pl, lazyskills.com and acwinn.com share IP numbers with beadinggem.com.
beadinggem.com is delegated to four name servers: ns1.netfirms.com, ns2.netfirms.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
beadinggem.com at least partially shares name servers with other domains, for instance polhamus.net, shanghaiholistic.com, vandnautobodyrepair.com, millerfamilies.net and provip.ca.
These name servers are commonly used with the following name servers: ns3.mydomain.com, ns4.mydomain.com, ns1.mydomain.com, ns2.mydomain.com, ns1.dotster.com, ns2.dotster.com, ns1.ipower.com, ns2.ipower.com, ns1.verio.com and ns2.verio.com.
Host names with one IP number: ns1.netfirms.com points to 65.254.254.157; ns2.netfirms.com points to 66.96.142.145; ns1.yourhostingaccount.com points to 65.254.254.102; ns2.yourhostingaccount.com points to 65.254.254.155.
beadinggem.com is handled by a single mail server, mx.beadinggem.com.
mx.beadinggem.com resolves to two IP numbers: 66.96.140.76 and 66.96.140.77.