rafibuilds.dev - robtex.com
rafibuilds.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
rafibuilds.com |
rafibuilds.dev |
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-09-04 → 2026-10-31 · 2 obs
● 2026-10-31 10:33:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | 10 records |
| rafibuilds.dev | ns2fkr.name.com, ns4kpx.name.com, ns3cpr.name.com, ns1glr.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns2fkr.name.com, ns4kpx.name.com, ns3cpr.name.com, ns1glr.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
⏱️ Timing
Total: 980ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1glr.name.com, ns2fkr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)
Analysis
IP Addresses
rafibuilds.dev points to a single IP number: 91.195.240.94.
Additional host names — haulprotect90.com, 9857.org, aspen.ceo and two others — share IP numbers with rafibuilds.dev.
Name Servers
Delegation for rafibuilds.dev is to five name servers: ns1.name.com, ns1glr.name.com, ns2fkr.name.com and two others.
There is at least partial name server overlap between rafibuilds.dev and other domains — vvh389vvu3.com, finteli.ai, moncode.ai and two more among them.
These name servers regularly appear alongside ns3cpr.name.com, ns4kpx.name.com, ns1hwy.name.com and 7 other name servers in NS record sets.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1glr.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2fkr.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3cpr.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4kpx.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1glr.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1glr.name.com resolve to 163.114.216.17 IP addresses each.