chasingpeacocks.com - robtex.com
chasingpeacocks.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.130.190🇺🇸 Amazon3.33.128.0/20 | ||||||
| PTR | a2aa9ff50de748dbe.awsglobalaccelerator.com | ||||||
| A | 15.197.148.33🇺🇸 Amazon15.197.144.0/20 | ||||||
| NS | ns33.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21a1::11🇺🇸 GODADDY-DNS2603:5:21a0::/44 | ||||||
| PTR | ns33.domaincontrol.com | ||||||
| A | 97.74.106.17🇺🇸 GODADDY-DNS97.74.106.0/23 | ||||||
| PTR | ns33.domaincontrol.com | ||||||
| NS | ns34.domaincontrol.com | ||||||
| A | 2603:5:22a1::11🇺🇸 GODADDY-DNS2603:5:22a0::/44 | ||||||
| PTR | ns34.domaincontrol.com | ||||||
| A | 173.201.74.17🇺🇸 GODADDY-DNS173.201.74.0/23 | ||||||
| PTR | ns34.domaincontrol.com | ||||||
| SOA | ns33.domaincontrol.comdns@jomax.net 2023-09-20 #0 | ||||||
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=1774812522 | ||||||
Same first word
chasingpeacocks.com |
DNS History
4 records (4 active, 0 former)
●NSns33.domaincontrol.com2026-03-10 → 2026-03-29 · 2 obs
● 2026-03-29 19:57:54
●NSns34.domaincontrol.com2026-03-10 → 2026-03-29 · 2 obs
● 2026-03-29 19:57:54
●A15.197.148.332026-03-10 → 2026-03-29 · 2 obs
● 2026-03-29 19:57:54
●A3.33.130.1902026-03-10 → 2026-03-29 · 2 obs
● 2026-03-29 19:57:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net... | - |
| chasingpeacocks.com | ns33.domaincontrol.com, ns34.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.106.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chasingpeacocks.com (unsigned zone)
⏱️ Timing
Total: 324ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)
Analysis
IP Addresses
chasingpeacocks.com resolves to two IP numbers: 3.33.130.190 and 15.197.148.33.
Other host names, for instance keepitwet.com, leagueform.com, browneyedbillygoat.com, greatcarbonsense.com and stationhousebooks.com share IP numbers with chasingpeacocks.com.
Name Servers
Two name servers ns33.domaincontrol.com and ns34.domaincontrol.com handle delegation for chasingpeacocks.com.
chasingpeacocks.com uses the same name server setup as other domains, for example hindumas.com, rentaliser.com, linstruth.net, millionaire-university.com and sciphilly.org.
chasingpeacocks.com shares name servers with other domains at least in part, for instance hallcocu.org.
Host names with two IP numbers:
ns33.domaincontrol.com points to: 2603:5:21a1::11 and 97.74.106.17
ns34.domaincontrol.com points to: 2603:5:22a1::11 and 173.201.74.17