`visitcapitoldistrict.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.visitcapitoldistrict.com` ⭐
		A	66.96.140.180^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`180.140.96.66.static.eigbox.net`
		A	66.96.140.181^{🇺🇸 EIG-2987366.96.128.0/18 Endurance International Group, Inc}
			PTR	`181.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 2016-02-01 #42

`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=1771291435

Subdomains

hostmaster.visitcapitoldistrict.com

Same first word

visitcapitoldistrict.com

DNS History

4 records (4 active, 0 former)

●NSns1.mydomain.com2016-02-29 → 2026-03-24 · 2 obs

● 2016-02-29 07:23:44
● 2026-03-24 07:48:58

●NSns2.mydomain.com2016-02-29 → 2026-03-24 · 2 obs

● 2016-02-29 07:23:44
● 2026-03-24 07:48:58

●MXmx.visitcapitoldistrict.com2016-02-29 → 2026-03-24 · 2 obs

● 2016-02-29 07:23:44
● 2026-03-24 07:48:58

●A66.96.163.1992016-02-29 → 2026-03-24 · 2 obs

● 2016-02-29 07:23:44
● 2026-03-24 07:48:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
visitcapitoldistrict.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 visitcapitoldistrict.com (unsigned zone)

⏱️ Timing

Total: 197ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.96.163.199`
NS	2	`ns2.mydomain.com, ns1.mydomain.com`
MX	1	`mx.visitcapitoldistrict.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

The parent of hostmaster.visitcapitoldistrict.com is visitcapitoldistrict.com.

IP Addresses

visitcapitoldistrict.com points to IP number: 66.96.163.199.

Other host names such as sordobueno.com, holopy.com, capitol-district.com, larrymartinpainting.com and hostmaster.thealabamaelephant.com share IPs with visitcapitoldistrict.com.

Name Servers

visitcapitoldistrict.com is delegated to two name servers: ns1.mydomain.com and ns2.mydomain.com.

visitcapitoldistrict.com shares the same name server setup as oohoo.biz, bobspoolcenter.com, colorlatina.org, discoverytv.us and erosmoon.com.

visitcapitoldistrict.com at least partially shares name servers with other domains, for instance charpak.net, strony.ca, littlejacksmoonwalkrental.com, plumb-heat.com and microdorm.com.

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

Host names with a single IP:

ns1.mydomain.com points to 172.64.52.99.

ns2.mydomain.com points to 172.64.53.76.

Mail Servers

visitcapitoldistrict.com is handled by a single mail server, mx.visitcapitoldistrict.com.

The mail server setup for visitcapitoldistrict.com mirrors that of other domains, for instance hostmaster.visitcapitoldistrict.com.

mx.visitcapitoldistrict.com points to two IPs: 66.96.140.180 and 66.96.140.181.

visitcapitoldistrict.com - robtex.com