bitkub.work - dns.ninja
bitkub.work
work
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nic.work ⭐ | ||||||
| NS | b.nic.work | ||||||
| NS | c.nic.work | ||||||
| NS | x.nic.work | ||||||
| NS | y.nic.work | ||||||
| NS | z.nic.work | ||||||
| SOA | a.nic.workadmin@tldns.godaddy serial=1786276880 | ||||||
Same first word
Similar names
bukbit.com |
kubbit.com |
bitbuk.com |
bbtiku.com |
kubbti.ru |
bbutik.com |
bukitb.info |
tubbik.com |
bbutik.com.tr |
bbutik.ru |
bubkit.com |
DNS History
6 records (6 active, 0 former)
●A75.126.104.2302026-04-21 → 2026-08-09 · 2 obs
● 2026-08-09 12:28:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| work | a.nic.work, b.nic.work, c.nic.work, x.nic.work... | 12 records |
| bitkub.work | ns4dfh.name.com, ns3bfm.name.com, ns1ntw.name.com, ns2clp.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns4dfh.name.com, ns3bfm.name.com, ns1ntw.name.com, ns2clp.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bitkub.work (unsigned zone)
⏱️ Timing
Total: 601ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.104.230 |
| NS | 4 | ns1ntw.name.com, ns2clp.name.com... |
| TXT | 1 | v=spf1 ~all |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (a.nic.work, a.nic.work, b.nic.work...)
Analysis
IP Addresses
bitkub.work points to a single IP number: 75.126.104.230.
Additional host names — lezda.com, laymail.com, 117.ipplanet.com and two others — share IP numbers with bitkub.work.
Name Servers
Delegation for bitkub.work is to five name servers: ns1.name.com, ns1ntw.name.com, ns2clp.name.com and two others.
There is at least partial name server overlap between bitkub.work and other domains — authlive.org, isade.ch, zero.tel and two more among them.
These name servers regularly appear alongside ns4dfh.name.com, ns3bfm.name.com, ns1cnb.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.
ns1ntw.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2clp.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3bfm.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4dfh.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1ntw.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1ntw.name.com resolve to 163.114.216.17 IP addresses each.