cachekeeper.net - robtex.com
cachekeeper.net
net
| DNSSEC | ⚠️ Not signed | ||||||
| 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=1795239973 | ||||||
Same first word
Previous names
cachegop.net |
cachegorilla.net |
cachegrid.net |
cacheguard.net |
cachehaven.net |
cachehelpdesk.net |
cachehit.net |
cachehollow.net |
cachehomes.net |
cachehub.net |
cacheia.net |
cacheila.net |
cacheinc.net |
cacheit.net |
Next names
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-10-24 → 2026-11-21 · 2 obs
● 2026-11-21 06:13:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| cachekeeper.net | ns1ksz.name.com, ns2btz.name.com, ns3qtx.name.com, ns4fmx.name.com | - |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1ksz.name.com, ns2btz.name.com, ns3qtx.name.com, ns4fmx.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cachekeeper.net (unsigned zone)
⏱️ Timing
Total: 1064ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1ksz.name.com, ns2btz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
cachekeeper.net points to a single IP number: 91.195.240.94.
Additional host names — romkaring.com, rahnama.studio, 365hauy.poker and two others — share IP numbers with cachekeeper.net.
Name Servers
Delegation for cachekeeper.net is to five name servers: ns1.name.com, ns1ksz.name.com, ns2btz.name.com and two others.
cachekeeper.net has at least partial name server overlap with other domains, such as mo-contract.com, corporatedigitalcard.com, bidtot.com and two others.
ns4fmx.name.com, ns3qtx.name.com and ns3fqs.name.com — plus 7 other name servers — are commonly paired with these name servers.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1ksz.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2btz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3qtx.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fmx.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1ksz.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1ksz.name.com resolve to 163.114.216.17 IP addresses each.