bitkubinfinity.com - dns.ninja
bitkubinfinity.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=1784994987 | ||||||
Same first word
DNS History
6 records (6 active, 0 former)
●A75.126.100.102026-04-22 → 2026-07-25 · 2 obs
● 2026-07-25 15:59:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net... | - |
| bitkubinfinity.com | ns1ksz.name.com, ns2fhn.name.com, ns3fqs.name.com, ns4jnz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1ksz.name.com, ns2fhn.name.com, ns3fqs.name.com, ns4jnz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitkubinfinity.com (unsigned zone)
⏱️ Timing
Total: 157ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.100.10 |
| NS | 4 | ns1ksz.name.com, ns2fhn.name.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1ksz.name.com, ns1ksz.name.com, ns2fhn.name.com...)
Analysis
IP Addresses
bitkubinfinity.com resolves to one IP address: 75.126.100.10.
www.dragonbikes.co.uk, nextmoney.com, mgusvq.yosrikassed.com and two other host names share IP numbers with bitkubinfinity.com.
Name Servers
bitkubinfinity.com has five name servers, which are ns1.name.com, ns1ksz.name.com, ns2fhn.name.com and two others.
bitkubinfinity.com partially shares its NS delegation with several other domains, including indiadecors.com, parroquiaprovidenciapr.com, tentativename.com and two others.
In DNS configurations, these name servers often share authority with ns3fqs.name.com, ns4jnz.name.com, ns1hwy.name.com and 7 other name servers.
Hostnames that resolve to two IP addresses:
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.
ns2fhn.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.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.