`planforcegroup.com`

DNSSEC	⚠️ Not signed
A	35.196.129.95^{🇺🇸 Google35.196.128.0/20}
		PTR	`95.129.196.35.bc.googleusercontent.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	`planforcegroup-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c801::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:c927::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn8pr05cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr04cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr03cu00100.inbound.protection.outlook.com`
		A	52.101.8.44^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm5pr04cu00104.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.11.9^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr02cu00101.inbound.protection.outlook.com`
		A	52.101.11.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr03cu00202.inbound.protection.outlook.com`
TXT	`v=spf1 ip4:107.181.169.82 ip4:23.83.212.46 ip4:63.231.177.190 include:spf.pro...`
TXT	`MS=ms58374113`
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=125071409

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

Same first word

planforcegroup.com

DNS History

14 records (4 active, 10 former)

○NSdns010.d.register.com2016-03-13 → 2019-04-12 · 5 obs

○ 2016-01-25 17:58:10
● 2016-03-13 10:59:48
● 2019-04-12 13:33:46
○ 2026-02-25 19:31:14
○ 2026-03-28 18:18:12

○NSdns027.a.register.com2016-03-13 → 2019-04-12 · 5 obs

○ 2016-01-25 17:58:10
● 2016-03-13 10:59:48
● 2019-04-12 13:33:46
○ 2026-02-25 19:31:14
○ 2026-03-28 18:18:12

○NSdns080.b.register.com2016-03-13 → 2019-04-12 · 5 obs

○ 2016-01-25 17:58:10
● 2016-03-13 10:59:48
● 2019-04-12 13:33:46
○ 2026-02-25 19:31:14
○ 2026-03-28 18:18:12

●NSdns101.register.com2026-02-25 → 2026-03-28 · 3 obs

○ 2019-04-12 13:33:46
● 2026-02-25 19:31:14
● 2026-03-28 18:18:12

●NSdns102.register.com2026-02-25 → 2026-03-28 · 3 obs

○ 2019-04-12 13:33:46
● 2026-02-25 19:31:14
● 2026-03-28 18:18:12

○NSdns131.c.register.com2016-03-13 → 2019-04-12 · 5 obs

○ 2016-01-25 17:58:10
● 2016-03-13 10:59:48
● 2019-04-12 13:33:46
○ 2026-02-25 19:31:14
○ 2026-03-28 18:18:12

○NSns1.insourcedns.com2015-06-03 → 2016-01-25 · 4 obs

● 2015-06-03 21:40:44
● 2016-01-25 17:58:10
○ 2016-03-13 10:59:48
○ 2026-03-28 18:18:12

○NSns2.insourcedns.com2015-06-03 → 2016-01-25 · 4 obs

● 2015-06-03 21:40:44
● 2016-01-25 17:58:10
○ 2016-03-13 10:59:48
○ 2026-03-28 18:18:12

●MXplanforcegroup-com.mail.protection.outlook.com2016-03-13 → 2026-03-28 · 3 obs

○ 2016-01-25 17:58:10
● 2016-03-13 10:59:48
● 2026-03-28 18:18:12

○MXsmtp1.mke.securence.com2015-06-03 → 2016-01-25 · 4 obs

● 2015-06-03 21:40:44
● 2016-01-25 17:58:10
○ 2016-03-13 10:59:48
○ 2026-03-28 18:18:12

○MXsmtp1.msp.securence.com2015-06-03 → 2016-01-25 · 4 obs

● 2015-06-03 21:40:44
● 2016-01-25 17:58:10
○ 2016-03-13 10:59:48
○ 2026-03-28 18:18:12

○A107.181.169.802019-04-12 → 2019-04-12 · 4 obs

○ 2016-09-10 10:10:50
● 2019-04-12 13:33:46
○ 2026-02-25 19:31:14
○ 2026-03-28 18:18:12

●A35.196.129.952026-02-25 → 2026-03-28 · 3 obs

○ 2019-04-12 13:33:46
● 2026-02-25 19:31:14
● 2026-03-28 18:18:12

○A50.28.63.292015-06-03 → 2016-09-10 · 4 obs

● 2015-06-03 21:40:44
● 2016-09-10 10:10:50
○ 2019-04-12 13:33:46
○ 2026-03-28 18:18:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
planforcegroup.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.25.158

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for planforcegroup.com (unsigned zone)

⏱️ Timing

Total: 270ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.196.129.95`
NS	2	`dns102.register.com, dns101.register.com`
MX	1	`planforcegroup-com.mail.protection.outlo`
TXT	2	`v=spf1 ip4:107.181.169.82 ip4:23.83.212., MS=ms58374113`
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

planforcegroup.com points to a single IP address: 35.196.129.95.

Other host names such as fifthwalldesig.wpengine.com, uptownvfw.org, www.wildbirdstore.com, permacindustries.com and distinctivecabinet.com share IP numbers with planforcegroup.com.

Name Servers

planforcegroup.com is delegated to two name servers: dns101.register.com and dns102.register.com.

planforcegroup.com uses the same name server setup as other domains, including (0x736578)ybuns.net, iguidancecounselor.com, mdrenocpa.org, jrfconnect.com and bluegreenowner.com.

Hostnames with a single IP

dns101.register.com resolves to: 162.159.24.117.

dns102.register.com resolves to: 162.159.25.158.

Mail Servers

The mail server for planforcegroup.com is planforcegroup-com.mail.protection.outlook.com.

planforcegroup-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c801::1, 2a01:111:f403:c927::1, 2a01:111:f403:f901::, 2a01:111:f403:f913::, 52.101.8.44, 52.101.9.11, 52.101.11.9 and 52.101.11.10.

planforcegroup.com - robtex.com