bubug.me - dns.ninja
bubug.me
me
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.me ⭐ | ||||||
| NS | a2.nic.me | ||||||
| NS | b0.nic.me | ||||||
| NS | b2.nic.me | ||||||
| NS | c0.nic.me | ||||||
| SOA | a0.nic.mehostmaster@donuts.email serial=1785324711 | ||||||
Same first word
bubug.me |
Similar names
DNS History
7 records (6 active, 1 former)
●NSns1.name.com2026-04-12 → 2026-07-29 · 3 obs
● 2026-04-12 22:58:00
● 2026-07-29 12:03:12
○A69.64.147.2422016-09-11 → 2017-05-18 · 4 obs
● 2017-05-18 00:29:54
○ 2019-07-04 09:27:38
○ 2026-07-29 12:03:12
●A91.195.240.822019-07-04 → 2026-07-29 · 3 obs
● 2019-07-04 09:27:38
● 2026-07-29 12:03:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| me | c0.nic.me, b2.nic.me, a0.nic.me, a2.nic.me... | - |
| bubug.me | ns3qty.name.com, ns1dhq.name.com, ns2knz.name.com, ns4fmw.name.com | - |
✅ Authoritative Response
Server:163.114.216.49
NS records: ns3qty.name.com, ns1dhq.name.com, ns2knz.name.com, ns4fmw.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bubug.me (unsigned zone)
⏱️ Timing
Total: 2021ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.82 |
| NS | 4 | ns1dhq.name.com, ns2knz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
bubug.me has exactly one IP address — 91.195.240.82.
simulform.net, m.ddfzydd.motorcycleridingsunglasses.com, markjacobrobinson.net plus two other host names have IP numbers in common with bubug.me.
Name Servers
Five name servers handle delegation for bubug.me: ns1.name.com, ns1dhq.name.com, ns2knz.name.com and two others.
There is at least partial name server overlap between bubug.me and other domains — backlinkfast.com, namespacer.net, rsistemas.net and two more among them.
These name servers regularly appear alongside ns4fmw.name.com, ns3qty.name.com, ns1cnb.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.
ns1dhq.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2knz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3qty.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fmw.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1dhq.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1dhq.name.com resolve to 163.114.216.17 IP addresses each.