`readingsymphony.com`

DNSSEC	⚠️ Not signed
NS	`dns1.amaserver.com` ⚠️ Not in zone NS records
		A	34.192.210.1^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-192-210-1.compute-1.amazonaws.com`
NS	`dns2.amaserver.com` ⚠️ Not in zone NS records
		A	52.14.239.52^{🇺🇸 Amazon52.14.0.0/16 EC2 CMH prefix}
			PTR	`ec2-52-14-239-52.us-east-2.compute.amazonaws.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.net`nstld@verisign-grs.com serial=1774676982

WOT: SAFE (71/100)

Same first word

readingsymphony.org

readingsymphony.com

DNS History

10 records (2 active, 8 former)

●NSdns1.amaserver.com2026-02-18 → 2026-03-28 · 3 obs

○ 2017-02-10 09:28:22
● 2026-02-18 20:39:52
● 2026-03-28 06:19:20

●NSdns2.amaserver.com2026-02-18 → 2026-03-28 · 3 obs

○ 2017-02-10 09:28:22
● 2026-02-18 20:39:52
● 2026-03-28 06:19:20

○NSns3.fast.net2007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 22:36:38
○ 2015-07-08 16:47:54
○ 2026-03-28 06:19:20

○NSreisns1.readingeagle.com2015-07-08 → 2017-02-10 · 5 obs

○ 2007-10-28 22:36:38
● 2015-07-08 16:47:54
● 2017-02-10 09:28:22
○ 2026-02-18 20:39:52
○ 2026-03-28 06:19:20

○NSreisns2.readingeagle.com2015-07-08 → 2017-02-10 · 5 obs

○ 2007-10-28 22:36:38
● 2015-07-08 16:47:54
● 2017-02-10 09:28:22
○ 2026-02-18 20:39:52
○ 2026-03-28 06:19:20

○NSreisns3.readingeagle.com2015-07-08 → 2017-02-10 · 5 obs

○ 2007-10-28 22:36:38
● 2015-07-08 16:47:54
● 2017-02-10 09:28:22
○ 2026-02-18 20:39:52
○ 2026-03-28 06:19:20

○MXpost2.fast.net2007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 22:36:38
○ 2015-07-08 16:47:54
○ 2026-03-28 06:19:20

○MXrelay.readingeagle.com2007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 22:36:38
○ 2015-07-08 16:47:54
○ 2026-03-28 06:19:20

○A107.1.36.1822015-07-08 → 2017-02-10 · 5 obs

○ 2007-10-28 22:36:38
● 2015-07-08 16:47:54
● 2017-02-10 09:28:22
○ 2026-02-18 20:39:52
○ 2026-03-28 06:19:20

○A206.245.146.552007-10-28 → 2007-10-28 · 3 obs

● 2007-10-28 22:36:38
○ 2015-07-08 16:47:54
○ 2026-03-28 06:19:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
readingsymphony.com	dns1.amaserver.com, dns2.amaserver.com	2 records

✅ Authoritative Response

Server:34.192.210.1

NS records: dns1.amaserver.com, dns2.amaserver.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for readingsymphony.com (unsigned zone)

⏱️ Timing

Total: 100ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns1.amaserver.com, dns2.amaserver.com)

Analysis

Name Servers

readingsymphony.com has two name servers: dns1.amaserver.com and dns2.amaserver.com.

readingsymphony.com shares the same name server setup as other domains, for example montanahottub.com, rhettdawn.com, prospectorsling.io, deseretmediagroup.com and datatechdesigns.com.

readingsymphony.com shares some name servers with other domains, for example markhultgren.name, the-marketing-solution.com, reputationreach.com, digitaldesignpros.com and repfend.com.

these name servers are often used with ns3.rapifyserver.com, ns4.rapifyserver.com, ns1.wpgatewayserver.com, ns2.wpgatewayserver.com, dns1.icertified.net, dns2.icertified.net, ns3.amaserver.com, ns4.amaserver.com, ns1.amaserver.com and ns2.amaserver.com.

Host names with a single IP:

dns1.amaserver.com points to 34.192.210.1

dns2.amaserver.com points to 52.14.239.52

readingsymphony.com - robtex.com