`legacypd.com`

DNSSEC	⚠️ Not signed
A	52.6.86.175^{🇺🇸 Amazon52.4.0.0/14 EC2 IAD prefix}
		PTR	`ec2-52-6-86-175.compute-1.amazonaws.com`
NS	`ns-cloud-c1.googledomains.com` ⭐
		A	2001:4860:4802:32::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-c4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.26^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-cloud-c1.googledomains.com`dns-admin@google.com serial=36

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

Same first word

legacypd.com

DNS History

10 records (10 active, 0 former)

●NSns-cloud-c1.googledomains.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●NSns-cloud-c2.googledomains.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●NSns-cloud-c3.googledomains.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●NSns-cloud-c4.googledomains.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●MXalt1.aspmx.l.google.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●MXalt2.aspmx.l.google.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●MXalt3.aspmx.l.google.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●MXalt4.aspmx.l.google.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●MXaspmx.l.google.com2015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

●A52.6.86.1752015-07-22 → 2026-04-25 · 2 obs

● 2015-07-22 23:12:02
● 2026-04-25 12:48:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
legacypd.com	ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.36.108

NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for legacypd.com (unsigned zone)

⏱️ Timing

Total: 402ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.6.86.175`
NS	4	`ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com...`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-c1.googledomains.com dns-admin.`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)

Analysis

IP Addresses

legacypd.com points to an IP address: 52.6.86.175.

Other host names, for instance ec2-52-6-86-175.compute-1.amazonaws.com, share IP numbers with legacypd.com.

Name Servers

legacypd.com delegates to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.

legacypd.com at least partially shares name servers with other domains, for instance scalr.dev, hdwnl.com, flashflamez.com, softwater.solutions and gatheringthepieces.com.

These name servers are commonly used with ns1.mirusresearch.com and ns2.mir.us.

Host names with two IP numbers: ns-cloud-c1.googledomains.com points to 2001:4860:4802:32::6c and 216.239.32.108; ns-cloud-c2.googledomains.com points to 2001:4860:4802:34::6c and 216.239.34.108; ns-cloud-c3.googledomains.com points to 2001:4860:4802:36::6c and 216.239.36.108; ns-cloud-c4.googledomains.com points to 2001:4860:4802:38::6c and 216.239.38.108.

Mail Servers

legacypd.com is served by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

legacypd.com shares at least partially some mail servers with other domains, for instance cycapitolhill.com, origopro.com, rholc.club, ges-ups.com and sjcoc.com.