crcbuzz.com - dns.ninja
crcbuzz.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 77.247.179.90🇳🇱 NFORCE77.247.176.0/21 NFOrce Entertainment BV - route 77.247.176.0/21 | ||||||
| NS | ns1.badgerdns.com ⭐ | ||||||
| A | 208.115.240.174🇺🇸 Limestone Networks208.115.192.0/18 Inc. 400 S. Akard Street Dallas, TX 75202 US =20 | ||||||
| PTR | 174-240-115-208.static.reverse.lstn.net | ||||||
| NS | ns2.badgerdns.com | ||||||
| A | 77.247.179.81🇳🇱 NFORCE77.247.176.0/21 NFOrce Entertainment BV - route 77.247.176.0/21 | ||||||
| SOA | ns1.badgerdns.comadmin@crcbuzz.com 2026-07-27 #6 | ||||||
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=1785505222 | ||||||
Same first word
crcbuzz.com |
DNS History
24 records (3 active, 21 former)
○NSdpns1.dnsnameserver.org2015-08-25 → 2016-09-11 · 4 obs
● 2016-09-11 07:10:42
○ 2016-12-02 10:11:36
○ 2026-07-31 13:59:56
○NSdpns2.dnsnameserver.org2015-08-25 → 2016-09-11 · 4 obs
● 2016-09-11 07:10:42
○ 2016-12-02 10:11:36
○ 2026-07-31 13:59:56
○NSdpns3.dnsnameserver.org2015-08-25 → 2016-09-11 · 4 obs
● 2016-09-11 07:10:42
○ 2016-12-02 10:11:36
○ 2026-07-31 13:59:56
○NSdpns4.dnsnameserver.org2015-08-25 → 2016-09-11 · 4 obs
● 2016-09-11 07:10:42
○ 2016-12-02 10:11:36
○ 2026-07-31 13:59:56
●NSns1.badgerdns.com2026-02-21 → 2026-07-31 · 3 obs
● 2026-02-21 11:58:48
● 2026-07-31 13:59:56
○NSns1.hostresolver.com2026-02-21 → 2026-07-31 · 2 obs
○ 2026-07-31 13:59:56
○NSns111373.ztomy.com2016-12-02 → 2017-10-05 · 5 obs
● 2016-12-02 10:11:36
● 2017-10-05 05:32:56
○ 2026-02-21 11:58:48
○ 2026-07-31 13:59:56
●NSns2.badgerdns.com2026-02-21 → 2026-07-31 · 3 obs
● 2026-02-21 11:58:48
● 2026-07-31 13:59:56
○NSns2.hostresolver.com2026-02-21 → 2026-07-31 · 2 obs
○ 2026-07-31 13:59:56
○NSns211373.ztomy.com2016-12-02 → 2017-10-05 · 5 obs
● 2016-12-02 10:11:36
● 2017-10-05 05:32:56
○ 2026-02-21 11:58:48
○ 2026-07-31 13:59:56
○A141.8.226.252016-12-02 → 2017-02-08 · 5 obs
● 2016-12-02 10:11:36
● 2017-02-08 08:22:34
○ 2017-07-06 14:12:18
○ 2026-07-31 13:59:56
○A199.191.50.732017-07-06 → 2017-10-05 · 5 obs
● 2017-07-06 14:12:18
● 2017-10-05 05:32:56
○ 2026-02-21 11:58:48
○ 2026-07-31 13:59:56
○A208.87.150.502015-08-25 → 2016-09-11 · 4 obs
● 2016-09-11 07:10:42
○ 2016-12-02 10:11:36
○ 2026-07-31 13:59:56
○A212.92.105.272026-02-21 → 2026-07-31 · 2 obs
○ 2026-07-31 13:59:56
○A216.245.197.442026-07-12 → 2026-07-12 · 4 obs
● 2026-07-12 04:05:56
○ 2026-07-12 09:31:06
○ 2026-07-31 13:59:56
○A216.245.197.452026-04-07 → 2026-04-07 · 4 obs
● 2026-04-07 21:55:42
○ 2026-04-08 05:50:06
○ 2026-07-31 13:59:56
○A216.245.197.462026-03-29 → 2026-07-09 · 10 obs
● 2026-03-29 17:25:08
○ 2026-03-30 19:19:46
○ 2026-03-31 14:32:18
● 2026-04-04 19:19:18
○ 2026-04-05 06:42:42
○ 2026-04-15 15:03:42
● 2026-07-09 15:53:52
○ 2026-07-12 04:05:56
○ 2026-07-31 13:59:56
○A77.247.179.822026-02-21 → 2026-03-28 · 6 obs
● 2026-02-21 11:58:48
○ 2026-03-12 06:45:22
● 2026-03-28 12:31:02
○ 2026-03-29 17:25:08
○ 2026-07-31 13:59:56
○A77.247.179.832026-03-12 → 2026-03-30 · 7 obs
● 2026-03-12 06:45:22
○ 2026-03-28 12:31:02
○ 2026-03-29 17:25:08
● 2026-03-30 19:19:46
○ 2026-03-31 14:32:18
○ 2026-07-31 13:59:56
○A77.247.179.852026-04-10 → 2026-04-10 · 4 obs
● 2026-04-10 09:29:46
○ 2026-04-15 15:03:42
○ 2026-07-31 13:59:56
○A77.247.179.862026-04-08 → 2026-04-08 · 4 obs
● 2026-04-08 05:50:06
○ 2026-04-10 09:29:46
○ 2026-07-31 13:59:56
○A77.247.179.882026-07-12 → 2026-07-12 · 4 obs
● 2026-07-12 09:31:06
○ 2026-07-15 05:43:16
○ 2026-07-31 13:59:56
●A77.247.179.902026-07-31 → 2026-07-31 · 2 obs
● 2026-07-31 13:59: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... | - |
| crcbuzz.com | ns1.badgerdns.com, ns2.badgerdns.com | 2 records |
✅ Authoritative Response
Server:208.115.240.174
NS records: ns1.badgerdns.com, ns2.badgerdns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for crcbuzz.com (unsigned zone)
⏱️ Timing
Total: 242ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.245.197.43 |
| NS | 2 | ns1.badgerdns.com, ns2.badgerdns.com |
| SOA | 1 | ns1.badgerdns.com admin.crcbuzz.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.badgerdns.com, ns2.badgerdns.com)
Analysis
IP Addresses
crcbuzz.com points to a single IP number: 77.247.179.90.
Additional host names — bvsoccer.org, 99c3fc6dfa2e8b49345c.pipiapps.com, trivago.us and two others — share IP numbers with crcbuzz.com.
Name Servers
crcbuzz.com is served by two delegated name servers, ns1.badgerdns.com and ns2.badgerdns.com.
crcbuzz.com shares its name server setup with other domains, including fh326.com, loinsden.com, texaslottory.com and two others.
Both ns1.badgerdns.com and ns2.badgerdns.com have a single IP address each — ns1.badgerdns.com resolves to 208.115.240.174 while ns2.badgerdns.com resolves to 77.247.179.81.