bubaluscapital.com - dns.ninja
bubaluscapital.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=1785444377 | ||||||
Same first word
bubaluscapital.com |
DNS History
11 records (11 active, 0 former)
●NSjustin.ns.cloudflare.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●NSziggy.ns.cloudflare.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●MXalt1.aspmx.l.google.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●MXalt2.aspmx.l.google.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●MXalt3.aspmx.l.google.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●MXalt4.aspmx.l.google.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●MXaspmx.l.google.com2026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●A104.21.16.2492026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●A172.67.217.862026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●A2606:4700:3036::6815:10f92026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
●A2606:4700:3037::ac43:d9562026-07-14 → 2026-07-30 · 2 obs
● 2026-07-30 21:03:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net... | - |
| bubaluscapital.com | justin.ns.cloudflare.com, ziggy.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.187
NS records: justin.ns.cloudflare.com, ziggy.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bubaluscapital.com (unsigned zone)
⏱️ Timing
Total: 169ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.217.86, 104.21.16.249 |
| AAAA | 2 | 2606:4700:3037::ac43:d956, 2606:4700:3036::6815:10f9 |
| NS | 2 | justin.ns.cloudflare.com, ziggy.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 4 | facebook-domain-verification=vd9dtqoxra6, google-site-verification=4GZ4Qgz_zNgXq-J... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | justin.ns.cloudflare.com dns.cloudflare. |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (justin.ns.cloudflare.com, justin.ns.cloudflare.com, justin.ns.cloudflare.com...)
Analysis
IP Addresses
bubaluscapital.com directs to four IP numbers, which are 104.21.16.249, 172.67.217.86, 2606:4700:3036::6815:10f9 and 2606:4700:3037::ac43:d956.
Among the host names that share IP numbers with bubaluscapital.com are jemarigrup.com, northsidedentures.com.au, taoyuan66.com and two others.
Name Servers
bubaluscapital.com uses two name servers for its delegation: justin.ns.cloudflare.com and ziggy.ns.cloudflare.com.
bubaluscapital.com has the same name server delegation as a number of other domains, such as s(0x616e616c)sunucum.com, cokhos.com, 1run9.com and two more.
There is at least partial name server overlap between bubaluscapital.com and other domains — i-homes.org, dyp.ai, nmfuk.org and two more among them.
These name servers frequently co-occur with the name servers ignat.ns.cloudflare.com and lamar.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
Hostname justin.ns.cloudflare.com directs to 108.162.193.187, 172.64.33.187 and 173.245.59.187 along with 3 other IP addresses.
Hostname ziggy.ns.cloudflare.com directs to 108.162.194.237, 162.159.38.237 and 172.64.34.237 along with 3 other IP addresses.
Mail Servers
Five mail servers handle bubaluscapital.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
bubaluscapital.com shares at least some of its mail servers with other domains — for example ns500671.ns500731.ns500742.ns500671.ns500742.ns500688.ns500704.ns500705.ns500671.ns500705.ns500671.lustychickser.com, ns500768.ns500759.ns500759.ns500698.ns500735.ns500736.ns500735.ns500736.ns500698.ns500576.ns500708.ns500619.ns500698.trackreceptor.com, ns500698.ns500759.ns500759.ns500698.ns500698.ns500736.ns500698.ns500698.ns500736.ns500698.ns500698.ns500708.ns500652.trackreceptor.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 192.178.155.27 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.