connected.buzz - dns.ninja
connected.buzz
buzz
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns1.dns.nic.buzz ⭐ | ||||||
| NS | a.nic.buzz | ||||||
| NS | b.nic.buzz | ||||||
| NS | c.nic.buzz | ||||||
| NS | ns2.dns.nic.buzz | ||||||
| NS | ns3.dns.nic.buzz | ||||||
| SOA | ns1.dns.nic.buzzadmin@tldns.godaddy serial=1780903956 | ||||||
Same first word
Similar names
DNS History
10 records (8 active, 2 former)
○NSns1.afternic.com2016-12-11 → 2017-08-18 · 4 obs
● 2017-08-18 12:34:36
○ 2026-03-14 17:16:50
○ 2026-06-08 07:37:52
●NSns33.domaincontrol.com2026-03-14 → 2026-06-08 · 3 obs
● 2026-03-14 17:16:50
● 2026-06-08 07:37:52
●NSns34.domaincontrol.com2026-03-14 → 2026-06-08 · 3 obs
● 2026-03-14 17:16:50
● 2026-06-08 07:37:52
●MXalt1.aspmxl.google.com2026-03-14 → 2026-06-08 · 2 obs
● 2026-06-08 07:37:52
●MXalt2.aspmx.l.google.com2026-03-14 → 2026-06-08 · 2 obs
● 2026-06-08 07:37:52
●MXalt3.aspmx.l.google.com2026-03-14 → 2026-06-08 · 2 obs
● 2026-06-08 07:37:52
●MXalt4.aspmx.l.google.com2026-03-14 → 2026-06-08 · 2 obs
● 2026-06-08 07:37:52
●MXaspmx.l.google.com2026-03-14 → 2026-06-08 · 2 obs
● 2026-06-08 07:37:52
○A184.168.221.1042016-12-11 → 2017-08-18 · 4 obs
● 2017-08-18 12:34:36
○ 2026-03-14 17:16:50
○ 2026-06-08 07:37:52
●A199.34.228.752026-03-14 → 2026-06-08 · 3 obs
● 2026-03-14 17:16:50
● 2026-06-08 07:37:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| buzz | ns3.dns.nic.buzz, c.nic.buzz, ns1.dns.nic.buzz, a.nic.buzz... | 12 records |
| connected.buzz | ns33.domaincontrol.com, ns34.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.106.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for connected.buzz (unsigned zone)
⏱️ Timing
Total: 469ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.34.228.75 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmxl.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=9NIgJF96vBV80Il |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (a.nic.buzz, b.nic.buzz, c.nic.buzz...)
Analysis
IP Addresses
connected.buzz resolves to one IP address: 199.34.228.75.
industrialescaperooms.com, wendyfine.com, kamaya.com and two other host names share IP numbers with connected.buzz.
Name Servers
connected.buzz uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.
connected.buzz uses the same name servers as several other domains — among them dga-ev.com, diamonsb.com, heroesandfantasies.com and two more.
The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
connected.buzz has 5 mail servers — alt1.aspmxl.google.com, aspmx.l.google.com, alt2.aspmx.l.google.com and two more.
connected.buzz has at least partial mail server overlap with other domains such as pittoreski.com, ns500698.ns500758.ns500698.ns500758.ns500698.ns500698.ns500736.ns500698.ns500736.ns500735.ns500576.ns500708.trackreceptor.com, ns500758.ns500698.ns500758.ns500698.ns500735.ns500735.ns500698.ns500735.ns500735.ns500736.ns500735.ns500708.ns500698.ns500652.ns500576.trackreceptor.com and two more.
These mail servers are often used together with the mail servers alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and six other.
aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com all point to exactly two IP numbers each: aspmx.l.google.com → 192.178.223.27 and 2a00:1450:4009:c0f::1b; alt2.aspmx.l.google.com → 192.178.213.27 and 2a00:1450:4013:c1e::1b; alt3.aspmx.l.google.com → 142.251.127.26 and 2a00:1450:4001:c21::1b; alt4.aspmx.l.google.com → 142.250.147.27 and 2a00:1450:4025:c01::1b.