`leadingcommunications.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=1774365702

Same first word

leadingcommunications.com

DNS History

7 records (2 active, 5 former)

○NShidden-master.yahoo.com2015-06-04 → 2017-01-12 · 4 obs

● 2015-06-04 13:18:18
● 2017-01-12 03:54:42
○ 2017-04-02 00:16:28
○ 2026-03-24 15:31:30

●NSns1.turbify.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-04-02 00:16:28
● 2026-03-24 15:31:30

●NSns2.turbify.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-04-02 00:16:28
● 2026-03-24 15:31:30

○NSyns1.yahoo.com2015-06-04 → 2017-01-12 · 4 obs

● 2015-06-04 13:18:18
● 2017-01-12 03:54:42
○ 2017-04-02 00:16:28
○ 2026-03-24 15:31:30

○NSyns2.yahoo.com2015-06-04 → 2017-01-12 · 4 obs

● 2015-06-04 13:18:18
● 2017-01-12 03:54:42
○ 2017-04-02 00:16:28
○ 2026-03-24 15:31:30

○MXmx-biz.mail.am0.yahoodns.net2015-06-04 → 2017-01-12 · 4 obs

● 2015-06-04 13:18:18
● 2017-01-12 03:54:42
○ 2017-04-02 00:16:28
○ 2026-03-24 15:31:30

○A98.138.19.1432015-06-04 → 2017-01-12 · 4 obs

● 2015-06-04 13:18:18
● 2017-01-12 03:54:42
○ 2017-04-02 00:16:28
○ 2026-03-24 15:31:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net...	-
leadingcommunications.com	ns1.turbify.com, ns2.turbify.com	4 records

✅ Authoritative Response

Server:34.195.51.6

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadingcommunications.com (unsigned zone)

⏱️ Timing

Total: 714ms | 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

Two name servers ns1.turbify.com and ns2.turbify.com handle delegation for leadingcommunications.com.

leadingcommunications.com uses the same name server setup as other domains, for example mucmc.org, tunesmm.com, onthereallybrightside.org, kerekindustries.com and duncanpainting.com.

leadingcommunications.com shares name servers with other domains at least partially, for instance soleilmontreal.com, aeronics.in, foamdist.com and roundstoneconsulting.com.

These name servers are often used with the name servers yns1.yahoo.com and yns2.yahoo.com.

Host names with two IP numbers:

ns1.turbify.com points to: 34.195.51.6 and 34.227.186.2

ns2.turbify.com points to: 52.3.46.62 and 52.73.255.93

leadingcommunications.com - robtex.com