buzzerbot.com - dns.ninja
buzzerbot.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.afternic.com ⭐ | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.afternic.comdns@jomax.net serial=1 | ||||||
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=1781464420 | ||||||
Same first word
buzzerbot.com |
DNS History
14 records (4 active, 10 former)
○NSns-1306.awsdns-35.org2015-10-24 → 2016-12-10 · 4 obs
● 2016-12-10 13:10:06
○ 2026-03-16 12:43:58
○ 2026-06-14 19:23:56
○NSns-1680.awsdns-18.co.uk2015-10-24 → 2016-12-10 · 4 obs
● 2016-12-10 13:10:06
○ 2026-03-16 12:43:58
○ 2026-06-14 19:23:56
○NSns-406.awsdns-50.com2015-10-24 → 2016-12-10 · 4 obs
● 2016-12-10 13:10:06
○ 2026-03-16 12:43:58
○ 2026-06-14 19:23:56
○NSns-628.awsdns-14.net2015-10-24 → 2016-12-10 · 4 obs
● 2016-12-10 13:10:06
○ 2026-03-16 12:43:58
○ 2026-06-14 19:23:56
●NSns1.afternic.com2026-03-16 → 2026-06-14 · 3 obs
● 2026-03-16 12:43:58
● 2026-06-14 19:23:56
●NSns2.afternic.com2026-03-16 → 2026-06-14 · 3 obs
● 2026-03-16 12:43:58
● 2026-06-14 19:23:56
○MX.2026-03-16 → 2026-06-14 · 2 obs
○ 2026-06-14 19:23:56
●A13.248.169.482026-03-16 → 2026-06-14 · 3 obs
● 2026-03-16 12:43:58
● 2026-06-14 19:23:56
○A54.231.114.1852016-11-29 → 2016-11-29 · 4 obs
● 2016-11-29 10:56:04
○ 2016-12-10 13:10:06
○ 2026-06-14 19:23:56
○A54.231.13.1802016-04-16 → 2016-04-16 · 3 obs
○ 2016-11-03 13:10:00
○ 2026-06-14 19:23:56
○A54.231.40.1852016-11-24 → 2016-11-24 · 4 obs
● 2016-11-24 04:42:26
○ 2016-11-29 10:56:04
○ 2026-06-14 19:23:56
○A54.231.49.1222016-12-10 → 2016-12-10 · 4 obs
● 2016-12-10 13:10:06
○ 2026-03-16 12:43:58
○ 2026-06-14 19:23:56
○A54.231.72.1292016-11-03 → 2016-11-03 · 4 obs
● 2016-11-03 13:10:00
○ 2016-11-24 04:42:26
○ 2026-06-14 19:23:56
●A76.223.54.1462026-03-16 → 2026-06-14 · 3 obs
● 2026-03-16 12:43:58
● 2026-06-14 19:23:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| buzzerbot.com | ns1.afternic.com, ns2.afternic.com | 4 records |
✅ Authoritative Response
Server:173.201.66.69
NS records: ns1.afternic.com, ns2.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for buzzerbot.com (unsigned zone)
⏱️ Timing
Total: 1276ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns2.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)
Analysis
IP Addresses
buzzerbot.com has two IP addresses: 13.248.169.48 and 76.223.54.146
s-lotgacor.xyz, www.quickdine.com, seating.solutions plus two other host names have IP numbers in common with buzzerbot.com.
Name Servers
The NS records for buzzerbot.com delegate to ns1.afternic.com and ns2.afternic.com.
The name server configuration of buzzerbot.com is shared with other domains, for instance ns.mekla.com, photopassion.com, bz2.www.datinghabits.com and two others.
There is at least partial name server overlap between buzzerbot.com and other domains — hungry(0x7075737379).com, oneverse.net, woov.xyz and two more among them.
These name servers tend to appear in combination with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-urj2ap2akmgcchkhharttb.ns101.verify.hn, verification-kqnr5ht7z8pnvuelk6t645.ns101.verify.hn and verification-bntdckkvmvwfw4wkkqshzt.ns101.verify.hn.
ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. Likewise, ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45 — two IP addresses apiece.