dctchambers.com - dns.ninja
dctchambers.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=1783655682 | ||||||
Subdomains
mustang.dctchambers.com |
Same first word
dctchambers.com |
DNS History
9 records (8 active, 1 former)
●MXalt1.aspmx.l.google.com2015-06-20 → 2026-07-10 · 2 obs
● 2026-07-10 04:10:02
●MXalt2.aspmx.l.google.com2015-06-20 → 2026-07-10 · 2 obs
● 2026-07-10 04:10:02
●MXaspmx.l.google.com2015-06-20 → 2026-07-10 · 2 obs
● 2026-07-10 04:10:02
●MXaspmx2.googlemail.com2015-06-20 → 2026-07-10 · 2 obs
● 2026-07-10 04:10:02
●MXaspmx3.googlemail.com2015-06-20 → 2026-07-10 · 2 obs
● 2026-07-10 04:10:02
●A208.109.20.542026-02-27 → 2026-07-10 · 3 obs
● 2026-02-27 19:47:08
● 2026-07-10 04:10:02
○A64.207.139.982015-06-20 → 2017-11-16 · 4 obs
● 2017-11-16 12:22:10
○ 2026-02-27 19:47:08
○ 2026-07-10 04:10:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, g.gtld-servers.net, e.gtld-servers.net, m.gtld-servers.net... | - |
| dctchambers.com | ns1.hover.com, ns2.hover.com | 4 records |
✅ Authoritative Response
Server:64.98.148.13
NS records: ns1.hover.com, ns2.hover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dctchambers.com (unsigned zone)
⏱️ Timing
Total: 1089ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.109.20.54 |
| NS | 2 | ns2.hover.com, ns1.hover.com |
| MX | 5 | aspmx2.googlemail.com (pri: 30), aspmx.l.google.com (pri: 10)... |
| TXT | 3 | v=spf1 mx include:_spf.google.com includ, MS=ms26455292... |
| SOA | 1 | ns1.hover.com dnsmaster.hover.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.hover.com, ns1.hover.com, ns2.hover.com...)
Analysis
Hierarchy
The domain mustang.dctchambers.com falls under the parent dctchambers.com.
IP Addresses
dctchambers.com has exactly one IP address — 208.109.20.54.
peckernet.org, kylepennell.com, mail.estadopuro.com.co plus two other host names have IP numbers in common with dctchambers.com.
Name Servers
dctchambers.com uses two name servers for its delegation: ns1.hover.com and ns2.hover.com.
The name server configuration of dctchambers.com is shared with other domains, for instance mechio.com, unspoken.org, videogamecats.com and two others.
dctchambers.com shares at least some of its name servers with domains including joyscream.com, rogercavanagh.com and qmtu.com
These name servers tend to be used in conjunction with the name servers ns3.hover.com.
The two host names ns1.hover.com and ns2.hover.com each have a pair of IP addresses: ns1.hover.com has 216.40.47.26 and 2604:4000:0:d:216:40:47:26, and ns2.hover.com has 64.98.148.13 and 2604:4000:2800:d:64:99:148:13.
Mail Servers
Five mail servers handle dctchambers.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by dctchambers.com are shared with other domains: ns500742.ns500754.ns500671.ns500754.ns500731.ns500671.ns500671.ns500742.ns500678.ns500291.ns500671.lusty(0x736c7574)z.com, ns500693.ns500734.ns500734.ns500699.ns500693.ns500693.ns500693.ns500699.ns500693.ns500588.ns500588.ns500693.ns500578.ns500110.dtrkdll.com, ns500742.ns500671.ns500671.ns500671.ns500754.ns500704.ns500649.ns500291.ns500666.ns500131.lustychickser.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c0b::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.