`washingtonnc.com`

DNSSEC	⚠️ Not signed
NS	`ns1.dotster.com` ⚠️ Not in zone NS records
		A	172.64.52.250^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dotster.com` ⚠️ Not in zone NS records
		A	172.64.53.155^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}

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

Subdomains

mx.washingtonnc.com

Same first word

washingtonnc.ws

washingtonnc.us

washingtonnc.com

washingtonnc.gov

DNS History

11 records (2 active, 9 former)

○NSbns1.beaufortco.com2015-06-11 → 2016-07-03 · 4 obs

● 2015-06-11 23:43:40
● 2016-07-03 17:19:18
○ 2017-03-25 04:02:30
○ 2026-03-26 11:30:18

○NSbns2.beaufortco.com2015-06-11 → 2016-07-03 · 4 obs

● 2015-06-11 23:43:40
● 2016-07-03 17:19:18
○ 2017-03-25 04:02:30
○ 2026-03-26 11:30:18

○NSns1.beaufortco.com2015-06-11 → 2016-07-03 · 4 obs

● 2015-06-11 23:43:40
● 2016-07-03 17:19:18
○ 2017-03-25 04:02:30
○ 2026-03-26 11:30:18

●NSns1.dotster.com2017-03-25 → 2026-03-26 · 3 obs

○ 2016-07-03 17:19:18
● 2017-03-25 04:02:30
● 2026-03-26 11:30:18

●NSns2.dotster.com2017-03-25 → 2026-03-26 · 3 obs

○ 2016-07-03 17:19:18
● 2017-03-25 04:02:30
● 2026-03-26 11:30:18

○MXmx.washingtonnc.com2017-03-25 → 2020-03-01 · 5 obs

○ 2016-07-03 17:19:18
● 2017-03-25 04:02:30
● 2020-03-01 02:02:52
○ 2026-02-18 00:59:00
○ 2026-03-26 11:30:18

○MXspam.beaufortco.com2015-06-11 → 2016-07-03 · 4 obs

● 2015-06-11 23:43:40
● 2016-07-03 17:19:18
○ 2017-03-25 04:02:30
○ 2026-03-26 11:30:18

○A204.117.73.252016-07-03 → 2016-07-03 · 4 obs

○ 2016-03-06 08:52:36
● 2016-07-03 17:19:18
○ 2017-03-25 04:02:30
○ 2026-03-26 11:30:18

○A208.91.197.272026-02-18 → 2026-02-18 · 4 obs

○ 2020-03-01 02:02:52
● 2026-02-18 00:59:00
○ 2026-03-21 11:33:00
○ 2026-03-26 11:30:18

○A66.96.161.1312017-03-25 → 2020-03-01 · 5 obs

○ 2016-07-03 17:19:18
● 2017-03-25 04:02:30
● 2020-03-01 02:02:52
○ 2026-02-18 00:59:00
○ 2026-03-26 11:30:18

○A74.121.227.2532015-06-11 → 2016-03-06 · 4 obs

● 2015-06-11 23:43:40
● 2016-03-06 08:52:36
○ 2016-07-03 17:19:18
○ 2026-03-26 11:30:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
washingtonnc.com	ns1.dotster.com, ns2.dotster.com	2 records

✅ Authoritative Response

Server:172.64.53.155

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for washingtonnc.com (unsigned zone)

⏱️ Timing

Total: 217ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

washingtonnc.com is parent of mx.washingtonnc.com.

Name Servers

washingtonnc.com's delegation is to two name servers ns1.dotster.com and ns2.dotster.com.

washingtonnc.com shares the same name server configuration as other domains, such as iguanaent.com, saltcreekart.org, botster.net, linxsftp4.us and cirt.us.

washingtonnc.com at least partially shares its name servers with other domains, for instance capecorallotsforsale.com, perubank.com, objectgolf.com, sanderd.com and mortell.org.

these name servers are commonly used together with ns1.yourhostingaccount.com, ns2.yourhostingaccount.com, ns1.nameresolve.com and ns2.nameresolve.com.

Host names with a single IP:

ns1.dotster.com resolves to 172.64.52.250.

ns2.dotster.com resolves to 172.64.53.155.

washingtonnc.com - robtex.com