`plannedcommunityguide.com`

DNSSEC	⚠️ Not signed
A	162.241.218.202^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
		PTR	`box5588.bluehost.com`
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`mail.plannedcommunityguide.com` ⭐
		A	162.241.218.202^{🇺🇸 ORACLE-OCI-31898162.241.216.0/22 Google}
			PTR	`box5588.bluehost.com`
TXT	`v=spf1 +a +mx +ip4:69.195.124.105 ?all`
SOA	`ns1.bluehost.com`root@box5588.bluehost.com 2022-10-18 #0

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

Subdomains

mail.plannedcommunityguide.com

Same first word

plannedcommunityguide.com

DNS History

5 records (4 active, 1 former)

●NSns1.bluehost.com2015-07-03 → 2026-03-27 · 2 obs

● 2015-07-03 13:47:08
● 2026-03-27 17:46:40

●NSns2.bluehost.com2015-07-03 → 2026-03-27 · 2 obs

● 2015-07-03 13:47:08
● 2026-03-27 17:46:40

●MXmail.plannedcommunityguide.com2015-07-03 → 2026-03-27 · 2 obs

● 2015-07-03 13:47:08
● 2026-03-27 17:46:40

●A162.241.218.2022020-03-02 → 2026-03-27 · 3 obs

○ 2017-03-15 09:29:50
● 2020-03-02 23:22:22
● 2026-03-27 17:46:40

○A69.195.124.1052015-07-03 → 2017-03-15 · 4 obs

● 2015-07-03 13:47:08
● 2017-03-15 09:29:50
○ 2020-03-02 23:22:22
○ 2026-03-27 17:46:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net...	-
plannedcommunityguide.com	ns1.bluehost.com, ns2.bluehost.com	2 records

✅ Authoritative Response

Server:162.159.24.80

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for plannedcommunityguide.com (unsigned zone)

⏱️ Timing

Total: 299ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.218.202`
NS	2	`ns2.bluehost.com, ns1.bluehost.com`
MX	1	`mail.plannedcommunityguide.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:69.195.124.105 ?all`
SOA	1	`ns1.bluehost.com root.box5588.bluehost.c`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)

Analysis

Hierarchy

plannedcommunityguide.com is a parent of mail.plannedcommunityguide.com.

IP Addresses

plannedcommunityguide.com points to a single IP number: 162.241.218.202.

Other host names, for instance furies.net, phconta.com, mail.miapace.com, mail.jeffem.org and galaxyglassandmirror.ca share IP numbers with plannedcommunityguide.com.

Name Servers

Delegation for plannedcommunityguide.com rests with two name servers, ns1.bluehost.com and ns2.bluehost.com.

plannedcommunityguide.com shares the same name server setup as other domains, including synappse.com, power-logon.biz, saltminded.com, kimsoil.com and nwinblad.com.

plannedcommunityguide.com partially shares name servers with other domains, for instance asmfinc.com, fb.com.tw, desantispaintersvenice.com and maxco.com.ec.

These name servers are commonly used with ns1.hostmonster.com and ns2.hostmonster.com.

Host names with one IP number: ns1.bluehost.com points to 162.159.24.80; ns2.bluehost.com points to 162.159.25.175.

Mail Servers

plannedcommunityguide.com is handled by a single mail server, mail.plannedcommunityguide.com.

mail.plannedcommunityguide.com points to a single IP: 162.241.218.202.

plannedcommunityguide.com - robtex.com