clonefan.dev - robtex.com
clonefan.dev
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-09-19 → 2026-11-21 · 2 obs
● 2026-11-21 22:54:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| clonefan.dev | ns4fpy.name.com, ns2cvx.name.com, ns3gnv.name.com, ns1kpv.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns4fpy.name.com, ns2cvx.name.com, ns3gnv.name.com, ns1kpv.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for clonefan.dev (unsigned zone)
⏱️ Timing
Total: 1099ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1kpv.name.com, ns2cvx.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
clonefan.dev has exactly one IP address — 91.195.240.94.
becomingkale.org, 1familyfoundation.com, thescalingcfo.com plus two other host names have IP numbers in common with clonefan.dev.
Name Servers
Five name servers handle delegation for clonefan.dev: ns1.name.com, ns1kpv.name.com, ns2cvx.name.com and two others.
There is at least partial name server overlap between clonefan.dev and other domains — leeaudionsecurityma.com, paxfishing.com, dimentional.info and two more among them.
These name servers regularly appear alongside ns4fpy.name.com, ns3gnv.name.com, ns3dkz.name.com and 7 other name servers in NS record sets.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2cvx.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gnv.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fpy.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1kpv.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1kpv.name.com resolve to 163.114.216.17 IP addresses each.