championhouse.com - robtex.com
championhouse.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.google.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:32::a🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns1.google.com | ||||||
| A | 216.239.32.10🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns1.google.com | ||||||
| NS | ns2.google.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:34::a🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns2.google.com | ||||||
| A | 216.239.34.10🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns2.google.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=1785695852 | ||||||
Same first word
championhouse.com |
DNS History
6 records (2 active, 4 former)
○NSns.ud.net2015-06-26 → 2017-02-13 · 4 obs
● 2017-02-13 09:07:04
○ 2026-02-23 16:43:56
○ 2026-08-02 18:53:22
●NSns1.google.com2026-02-23 → 2026-08-02 · 3 obs
● 2026-02-23 16:43:56
● 2026-08-02 18:53:22
●NSns2.google.com2026-02-23 → 2026-08-02 · 3 obs
● 2026-02-23 16:43:56
● 2026-08-02 18:53:22
○NSns2.ud.net2015-06-26 → 2017-02-13 · 4 obs
● 2017-02-13 09:07:04
○ 2026-02-23 16:43:56
○ 2026-08-02 18:53:22
○MXmail.ud.net2015-06-26 → 2017-02-13 · 4 obs
● 2017-02-13 09:07:04
○ 2026-02-23 16:43:56
○ 2026-08-02 18:53:22
○A68.17.32.32015-06-26 → 2017-02-13 · 4 obs
● 2017-02-13 09:07:04
○ 2026-02-23 16:43:56
○ 2026-08-02 18:53:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| championhouse.com | ns2.google.com, ns1.google.com | 4 records |
✅ Authoritative Response
Server:216.239.32.10
NS records: ns2.google.com, ns1.google.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for championhouse.com (unsigned zone)
⏱️ Timing
Total: 112ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns2.google.com, ns2.google.com, ns1.google.com...)
Analysis
Name Servers
championhouse.com uses two name servers for its delegation: ns1.google.com and ns2.google.com.
championhouse.com shares its NS records with other domains, for example sendjetfast.com, votings-flarenetworks.live, icloud-log.in and two others.
The name servers of championhouse.com overlap at least partially with those of other domains — among them widevinetech.com, 211.14.72.in-addr.arpa, googledeveloperday.com and two more.
These name servers commonly appear alongside the name servers ns3.google.com and ns4.google.com.
The two host names ns1.google.com and ns2.google.com each have a pair of IP addresses: ns1.google.com has 216.239.32.10 and 2001:4860:4802:32::a, and ns2.google.com has 216.239.34.10 and 2001:4860:4802:34::a.