`capitol-district.com`

DNSSEC	⚠️ Not signed
A	66.96.163.199^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
		PTR	`199.163.96.66.static.eigbox.net`
NS	`ns1.mydomain.com` ⭐
		A	172.64.52.99^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.mydomain.com`
		A	172.64.53.76^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx.capitol-district.com` ⭐
		A	66.96.140.88^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`88.140.96.66.static.eigbox.net`
		A	66.96.140.89^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`89.140.96.66.static.eigbox.net`
TXT	`v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all`
SOA	`ns1.mydomain.com`dnsadmin@mydomain.com 2012-12-06 #80

`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.net`nstld@verisign-grs.com serial=1774380302

Previously MX for

capitol-district.com

Subdomains

mx.capitol-district.com

hostmaster.capitol-district.com

Same first word

capitol-district.com

DNS History

9 records (4 active, 5 former)

●NSns1.mydomain.com2018-11-14 → 2026-03-24 · 3 obs

○ 2017-02-08 21:04:08
● 2018-11-14 14:04:52
● 2026-03-24 19:54:24

○NSns1.pipedns.com2015-06-23 → 2017-02-08 · 4 obs

● 2015-06-23 14:15:20
● 2017-02-08 21:04:08
○ 2018-11-14 14:04:52
○ 2026-03-24 19:54:24

●NSns2.mydomain.com2018-11-14 → 2026-03-24 · 3 obs

○ 2017-02-08 21:04:08
● 2018-11-14 14:04:52
● 2026-03-24 19:54:24

○NSns2.pipedns.com2015-06-23 → 2017-02-08 · 4 obs

● 2015-06-23 14:15:20
● 2017-02-08 21:04:08
○ 2018-11-14 14:04:52
○ 2026-03-24 19:54:24

○NSns3.pipedns.com2015-06-23 → 2017-02-08 · 4 obs

● 2015-06-23 14:15:20
● 2017-02-08 21:04:08
○ 2018-11-14 14:04:52
○ 2026-03-24 19:54:24

○MXcapitol-district.com2015-06-23 → 2017-02-08 · 4 obs

● 2015-06-23 14:15:20
● 2017-02-08 21:04:08
○ 2018-11-14 14:04:52
○ 2026-03-24 19:54:24

●MXmx.capitol-district.com2018-11-14 → 2026-03-24 · 3 obs

○ 2017-02-08 21:04:08
● 2018-11-14 14:04:52
● 2026-03-24 19:54:24

○A173.254.28.1092015-06-23 → 2017-02-08 · 4 obs

● 2015-06-23 14:15:20
● 2017-02-08 21:04:08
○ 2018-11-14 14:04:52
○ 2026-03-24 19:54:24

●A66.96.163.1992018-11-14 → 2026-03-24 · 3 obs

○ 2017-02-08 21:04:08
● 2018-11-14 14:04:52
● 2026-03-24 19:54:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
capitol-district.com	ns1.mydomain.com, ns2.mydomain.com	2 records

✅ Authoritative Response

Server:172.64.52.99

NS records: ns1.mydomain.com, ns2.mydomain.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for capitol-district.com (unsigned zone)

⏱️ Timing

Total: 366ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.96.163.199`
NS	2	`ns2.mydomain.com, ns1.mydomain.com`
MX	1	`mx.capitol-district.com (pri: 30)`
TXT	1	`v=spf1 ip4:66.96.128.0/18 include:websit`
SOA	1	`ns1.mydomain.com dnsadmin.mydomain.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.mydomain.com, ns2.mydomain.com)

Analysis

Hierarchy

capitol-district.com is a parent of mx.capitol-district.com and hostmaster.capitol-district.com.

IP Addresses

capitol-district.com resolves to one IP number: 66.96.163.199.

Other host names, for instance medranochipping.com, mccsinc.net, sorokaclawoffice.com, omega4.info and 199.163.96.66.static.eigbox.net share IP numbers with capitol-district.com.

Name Servers

capitol-district.com's delegation uses two name servers: ns1.mydomain.com and ns2.mydomain.com.

capitol-district.com uses the same name server setup as other domains, such as leadmesa.com, fairfieldlimo.net, terravita.life, phadd.net and thegialliance.com.

capitol-district.com at least partially shares name servers with other domains, including joanna.net, wearelower.com, digicide.org, calliopy.com and maccanelli.com.

These name servers are commonly used together with the name servers ns3.mydomain.com, ns1.yourhostingaccount.com, ns2.yourhostingaccount.com and ns4.mydomain.com.

Host names with a single IP address: ns1.mydomain.com points to 172.64.52.99; ns2.mydomain.com points to 172.64.53.76.

Mail Servers

A single mail server handles capitol-district.com, mx.capitol-district.com.

capitol-district.com shares the same mail server setup as other domains, for example hostmaster.capitol-district.com.

The host name mx.capitol-district.com resolves to two IP numbers: 66.96.140.88 and 66.96.140.89.

capitol-district.com - robtex.com