plannedsecurityservices.com - dns.ninja

`plannedsecurityservices.com`

DNSSEC	⚠️ Not signed
A	205.178.189.131^{🇺🇸 Jacksonville205.178.189.0/24 5335 Gate Parkway Jacksonville FL 32256 United States}
		PTR	`wf.networksolutions.com`
NS	`dns101.register.com` ⭐
		A	162.159.24.117^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`dns102.register.com`
		A	162.159.25.158^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`alt2.aspmx.l.google.com` ⭐
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com` ⭐
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`aspmx3.googlemail.com` ⭐
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
TXT	`google-site-verification=ELVchfg6UNIHsTuhmRHmT5j4Kxupmq6r5ysmm8yyQDs`
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=121041407

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

Same first word

plannedsecurityservices.com

DNS History

14 records (8 active, 6 former)

○NSdns064.a.register.com2015-08-09 → 2016-08-07 · 4 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2016-08-07 15:26:34
○ 2026-07-01 08:23:20

●NSdns101.register.com2026-07-01 → 2026-07-01 · 2 obs

○ 2016-08-07 15:26:34
● 2026-07-01 08:23:20

●NSdns102.register.com2026-07-01 → 2026-07-01 · 2 obs

○ 2016-08-07 15:26:34
● 2026-07-01 08:23:20

○NSdns125.b.register.com2015-08-09 → 2016-08-07 · 4 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2016-08-07 15:26:34
○ 2026-07-01 08:23:20

○NSdns223.c.register.com2015-08-09 → 2016-08-07 · 4 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2016-08-07 15:26:34
○ 2026-07-01 08:23:20

○NSdns249.d.register.com2015-08-09 → 2016-08-07 · 4 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2016-08-07 15:26:34
○ 2026-07-01 08:23:20

●MXalt1.aspmx.l.google.com2015-08-09 → 2026-07-01 · 3 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2026-07-01 08:23:20

●MXalt2.aspmx.l.google.com2015-08-09 → 2026-07-01 · 3 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2026-07-01 08:23:20

●MXaspmx.l.google.com2015-08-09 → 2026-07-01 · 3 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2026-07-01 08:23:20

●MXaspmx2.googlemail.com2015-08-09 → 2026-07-01 · 3 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2026-07-01 08:23:20

●MXaspmx3.googlemail.com2015-08-09 → 2026-07-01 · 3 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
● 2026-07-01 08:23:20

●A205.178.189.1312026-07-01 → 2026-07-01 · 2 obs

○ 2016-08-07 15:26:34
● 2026-07-01 08:23:20

○A69.64.86.2472015-11-19 → 2016-08-07 · 4 obs

○ 2015-08-09 09:47:30
● 2015-11-19 04:08:48
● 2016-08-07 15:26:34
○ 2026-07-01 08:23:20

○A98.129.229.2002015-08-09 → 2015-08-09 · 4 obs

○ 2008-03-19 20:59:10
● 2015-08-09 09:47:30
○ 2015-11-19 04:08:48
○ 2026-07-01 08:23:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net, i.gtld-servers.net...	-
plannedsecurityservices.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.24.117

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for plannedsecurityservices.com (unsigned zone)

⏱️ Timing

Total: 369ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`205.178.189.131`
NS	2	`dns102.register.com, dns101.register.com`
MX	5	`aspmx.l.google.com (pri: 10), aspmx3.googlemail.com (pri: 5)...`
TXT	1	`google-site-verification=ELVchfg6UNIHsTu`
SOA	1	`DNS101.REGISTER.com root.REGISTER.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

IP Addresses

plannedsecurityservices.com resolves to one IP address: 205.178.189.131.

ynmnewyork.com, womenspirit.com, hugheshubbard.info and two other host names share IP numbers with plannedsecurityservices.com.

Name Servers

The NS records for plannedsecurityservices.com delegate to dns101.register.com and dns102.register.com.

plannedsecurityservices.com uses the same name servers as several other domains — among them cornerstonepm.com, rapbay.com, heelersolutions.com and two more.

plannedsecurityservices.com and other domains like aviationpartnersafrica.com share at least a portion of their name servers.

dns101.register.com directs to 162.159.24.117 and dns102.register.com directs to 162.159.25.158; each host name points to exactly one IP number.

Mail Servers

plannedsecurityservices.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

plannedsecurityservices.com has at least partial mail server overlap with other domains such as ns500698.ns500698.ns500759.ns500735.ns500735.ns500735.ns500652.ns500619.trackreceptor.com, satyanandayoga.gr, fslegal.com.au and two more.

These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Hostnames that resolve to two IP addresses:

The A records for aspmx2.googlemail.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.

The A records for aspmx3.googlemail.com return 172.253.116.27 and 2a00:1450:400b:c02::1a.

The A records for aspmx.l.google.com return 64.233.180.27 and 2607:f8b0:4004:c21::1a.

The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1a.

The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx2.googlemail.com and alt1.aspmx.l.google.com each have 2800:3f0:4003:c0f::1a IP addresses.

aspmx2.googlemail.com and alt1.aspmx.l.google.com each have 108.177.123.27 IP addresses.

aspmx3.googlemail.com and alt2.aspmx.l.google.com each have 172.253.116.27 IP addresses.