`waverlyimplement.com`

DNSSEC	⚠️ Not signed
NS	`ns1.turbify.com` ⚠️ Not in zone NS records
		A	34.195.51.6^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-195-51-6.compute-1.amazonaws.com`
		A	34.227.186.2^{🇺🇸 Amazon34.224.0.0/12 EC2 Region prefix}
			PTR	`ec2-34-227-186-2.compute-1.amazonaws.com`
NS	`ns2.turbify.com` ⚠️ Not in zone NS records
		A	52.3.46.62^{🇺🇸 Amazon52.2.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-3-46-62.compute-1.amazonaws.com`
		A	52.73.255.93^{🇺🇸 Amazon52.72.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-73-255-93.compute-1.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=1775152277

Same first word

waverlyimplement.com

DNS History

10 records (2 active, 8 former)

○NSdns1.tratx.com2015-07-20 → 2016-07-22 · 4 obs

● 2015-07-20 18:50:22
● 2016-07-22 02:52:58
○ 2017-03-31 21:05:34
○ 2026-04-02 17:52:08

○NSdns2.tratx.com2015-07-20 → 2016-07-22 · 4 obs

● 2015-07-20 18:50:22
● 2016-07-22 02:52:58
○ 2017-03-31 21:05:34
○ 2026-04-02 17:52:08

●NSns1.turbify.com2026-03-24 → 2026-04-02 · 3 obs

○ 2017-03-31 21:05:34
● 2026-03-24 00:12:14
● 2026-04-02 17:52:08

●NSns2.turbify.com2026-03-24 → 2026-04-02 · 3 obs

○ 2017-03-31 21:05:34
● 2026-03-24 00:12:14
● 2026-04-02 17:52:08

○NSns41.domaincontrol.com2017-03-31 → 2017-03-31 · 4 obs

○ 2016-07-22 02:52:58
● 2017-03-31 21:05:34
○ 2026-03-24 00:12:14
○ 2026-04-02 17:52:08

○NSns42.domaincontrol.com2017-03-31 → 2017-03-31 · 4 obs

○ 2016-07-22 02:52:58
● 2017-03-31 21:05:34
○ 2026-03-24 00:12:14
○ 2026-04-02 17:52:08

○MXmailstore1.secureserver.net2017-03-31 → 2017-03-31 · 3 obs

● 2017-03-31 21:05:34
○ 2026-03-24 00:12:14
○ 2026-04-02 17:52:08

○MXsmtp.secureserver.net2017-03-31 → 2017-03-31 · 3 obs

● 2017-03-31 21:05:34
○ 2026-03-24 00:12:14
○ 2026-04-02 17:52:08

○A184.168.221.92017-03-31 → 2017-03-31 · 4 obs

○ 2016-07-22 02:52:58
● 2017-03-31 21:05:34
○ 2026-03-24 00:12:14
○ 2026-04-02 17:52:08

○A72.32.112.1582015-07-20 → 2016-07-22 · 4 obs

● 2015-07-20 18:50:22
● 2016-07-22 02:52:58
○ 2017-03-31 21:05:34
○ 2026-04-02 17:52:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net...	-
waverlyimplement.com	ns1.turbify.com, ns2.turbify.com	4 records

✅ Authoritative Response

Server:52.3.46.62

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for waverlyimplement.com (unsigned zone)

⏱️ Timing

Total: 164ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.turbify.com, ns1.turbify.com, ns2.turbify.com...)

Analysis

Name Servers

waverlyimplement.com is delegated to two name servers ns1.turbify.com and ns2.turbify.com.

waverlyimplement.com shares the same name server setup as other domains, for instance acemortonlumber.com, fornoni.org, rwbcontracting.com, easyflexibility.com and mripa.net.

waverlyimplement.com at least partially shares name servers with other domains, for instance cuisinemachinecatering.com, vicbarcelona.com, inspecjapan.com, plantmedic.net and wholesale-linens.com.

these name servers are often used together with yns2.yahoo.com, yns1.yahoo.com, ns8.san.yahoo.com and ns9.san.yahoo.com.

Host names with two IP numbers:

The host name ns1.turbify.com points to 34.195.51.6 and 34.227.186.2; the host name ns2.turbify.com points to 52.3.46.62 and 52.73.255.93.

waverlyimplement.com - robtex.com