possiblyhome.com - robtex.com
possiblyhome.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=1786937364 | ||||||
Same first word
possiblyhome.com |
DNS History
6 records (6 active, 0 former)
●A185.158.133.12026-08-14 → 2026-08-17 · 2 obs
● 2026-08-17 03:43:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| possiblyhome.com | ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1hwy.name.com, ns2fln.name.com, ns3fqs.name.com, ns4jnz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for possiblyhome.com (unsigned zone)
⏱️ Timing
Total: 240ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.158.133.1 |
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1hwy.name.com, ns1hwy.name.com, ns2fln.name.com...)
Analysis
IP Addresses
possiblyhome.com has exactly one IP address — 185.158.133.1.
localwebz.com, reangan.app, advanceloanfast.com plus two other host names have IP numbers in common with possiblyhome.com.
Name Servers
Five name servers handle delegation for possiblyhome.com: ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
possiblyhome.com partially shares its NS delegation with several other domains, including vxs6m.com, jagsstudio.com, mvvrv2n.vip and two others.
In DNS configurations, these name servers often share authority with ns4jnz.name.com, ns3fqs.name.com, ns4lpv.name.com and 7 other name servers.
Host names pointing to two IP addresses:
The A records for ns1.name.com return 163.114.216.17 and 2a00:edc0:107::1.
The A records for ns1hwy.name.com return 163.114.216.17 and 2a00:edc0:107::1.
The A records for ns2fln.name.com return 163.114.216.49 and 2402:cf80:107::1.
The A records for ns3fqs.name.com return 163.114.217.17 and 2a00:edc0:107::49.
The A records for ns4jnz.name.com return 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com and ns1hwy.name.com each have 2a00:edc0:107::1 IP addresses.
ns1.name.com and ns1hwy.name.com each have 163.114.216.17 IP addresses.