`anchorstatus.com`

DNSSEC	⚠️ Not signed
NS	`ns-332.awsdns-41.com` ⭐
		A	2600:9000:5301:4c00::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-332.awsdns-41.com`
		A	205.251.193.76^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-332.awsdns-41.com`
NS	`ns-1230.awsdns-25.org`
		A	2600:9000:5304:ce00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1230.awsdns-25.org`
		A	205.251.196.206^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1230.awsdns-25.org`
NS	`ns-1783.awsdns-30.co.uk`
		A	2600:9000:5306:f700::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1783.awsdns-30.co.uk`
		A	205.251.198.247^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1783.awsdns-30.co.uk`
NS	`ns-776.awsdns-33.net`
		A	2600:9000:5303:800::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-776.awsdns-33.net`
		A	205.251.195.8^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-776.awsdns-33.net`
SOA	`ns-332.awsdns-41.com`awsdns-hostmaster@amazon.com serial=1

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

Same first word

anchorstatus.com

DNS History

4 records (4 active, 0 former)

●NSns-1230.awsdns-25.org2026-04-24 → 2026-04-24 · 2 obs

● 2026-04-24 18:25:42
● 2026-04-24 18:25:44

●NSns-1783.awsdns-30.co.uk2026-04-24 → 2026-04-24 · 2 obs

● 2026-04-24 18:25:42
● 2026-04-24 18:25:44

●NSns-332.awsdns-41.com2026-04-24 → 2026-04-24 · 2 obs

● 2026-04-24 18:25:42
● 2026-04-24 18:25:44

●NSns-776.awsdns-33.net2026-04-24 → 2026-04-24 · 2 obs

● 2026-04-24 18:25:42
● 2026-04-24 18:25:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
anchorstatus.com	ns-332.awsdns-41.com, ns-776.awsdns-33.net, ns-1783.awsdns-30.co.uk, ns-1230.awsdns-25.org	2 records

✅ Authoritative Response

Server:205.251.193.76

NS records: ns-332.awsdns-41.com, ns-776.awsdns-33.net, ns-1783.awsdns-30.co.uk, ns-1230.awsdns-25.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for anchorstatus.com (unsigned zone)

⏱️ Timing

Total: 700ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1230.awsdns-25.org, ns-1783.awsdns-30.co.uk...`
SOA	1	`ns-332.awsdns-41.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-332.awsdns-41.com, ns-332.awsdns-41.com)

Analysis

Name Servers

anchorstatus.com is delegated to four name servers: ns-332.awsdns-41.com, ns-776.awsdns-33.net, ns-1230.awsdns-25.org and ns-1783.awsdns-30.co.uk.

anchorstatus.com at least partially shares name servers with other domains, for instance maandoo.com, trektwice.com, foolradio.com, spscards.net and remodeltoday.com.

These name servers are commonly used with ns-944.awsdns-54.net, ns-225.awsdns-28.com, ns1.americaneagle.com, ns2.americaneagle.com, ns-334.awsdns-41.com and ns-1955.awsdns-52.co.uk.

Host names with two IP numbers: ns-332.awsdns-41.com points to 2600:9000:5301:4c00::1 and 205.251.193.76; ns-776.awsdns-33.net points to 2600:9000:5303:800::1 and 205.251.195.8; ns-1230.awsdns-25.org points to 2600:9000:5304:ce00::1 and 205.251.196.206; ns-1783.awsdns-30.co.uk points to 2600:9000:5306:f700::1 and 205.251.198.247.

anchorstatus.com - robtex.com