`tulsaplanning.org`

DNSSEC	⚠️ Not signed
A	23.235.198.21^{🇺🇸 IMH-IAD23.235.196.0/22 IMH-East}
		PTR	`ecbiz226.inmotionhosting.com`
NS	`ns1.tulsaconnect.com` ⭐
		A	65.38.18.194^{🇺🇸 AS2274765.38.0.0/19 65.38.0.0/19}
			PTR	`ns1.tulsaconnect.com`
NS	`ns2.tulsaconnect.com`
		A	67.214.107.58^{🇺🇸 AS2274767.214.96.0/20 67.214.96.0/20}
			PTR	`ns2.tulsaconnect.com`
MX	`mx1.tulsaconnect.com` ⭐
		A	65.39.216.12^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx3.emailarray.com`
		A	65.39.216.33^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx4.emailarray.com`
		A	65.39.216.37^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx5.emailarray.com`
		A	65.39.216.41^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx0.emailarray.com`
		A	65.39.216.91^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx6.emailarray.com`
MX	`mx2.tulsaconnect.com` ⭐
		A	65.39.216.33^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx4.emailarray.com`
		A	65.39.216.37^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx5.emailarray.com`
		A	65.39.216.41^{🇨🇦 APTUM65.39.216.0/22 Peer1 Route Object}
			PTR	`mx0.emailarray.com`
TXT	`v=spf1 include:tulsaconnect.com ~all`
SOA	`ns1.tulsaconnect.com`dnsadmin@tulsaconnect.com serial=20247805

`org`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.org.afilias-nst.info` ⭐ ⚠️ Not in parent delegation
	NS	`a2.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`c0.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`d0.org.afilias-nst.org`
	SOA	`a0.org.afilias-nst.info`hostmaster@donuts.email serial=1778431972

tulsaplanning.org

5 records (5 active, 0 former)

●NSns1.tulsaconnect.com2026-04-12 → 2026-05-10 · 2 obs

● 2026-04-12 11:00:32
● 2026-05-10 17:08:10

●NSns2.tulsaconnect.com2026-04-12 → 2026-05-10 · 2 obs

● 2026-04-12 11:00:32
● 2026-05-10 17:08:10

●MXmx1.tulsaconnect.com2026-04-12 → 2026-05-10 · 2 obs

● 2026-04-12 11:00:32
● 2026-05-10 17:08:10

●MXmx2.tulsaconnect.com2026-04-12 → 2026-05-10 · 2 obs

● 2026-04-12 11:00:32
● 2026-05-10 17:08:10

●A23.235.198.212026-04-12 → 2026-05-10 · 2 obs

● 2026-04-12 11:00:32
● 2026-05-10 17:08:10

Zone	Nameservers	Glue
org	b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org	-
tulsaplanning.org	ns2.tulsaconnect.com, ns1.tulsaconnect.com	-

Server:67.214.107.58

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

⚠️ Insecure (no DNSSEC)

No DS record for tulsaplanning.org (unsigned zone)

Total: 659ms | Queries: -

Type	Count	Sample Data
A	1	`23.235.198.21`
NS	2	`ns1.tulsaconnect.com, ns2.tulsaconnect.com`
MX	2	`mx1.tulsaconnect.com (pri: 10), mx2.tulsaconnect.com (pri: 10)`
TXT	1	`v=spf1 include:tulsaconnect.com ~all`
SOA	1	`ns1.tulsaconnect.com dnsadmin.tulsaconne`

tulsaplanning.org resolves to a single IP: 23.235.198.21.

Other host names, for instance rayonex.com, pottercompanies.com, retiredgsc.org, artminds.rtsranger.com and ontwinlakes.com share IP numbers with tulsaplanning.org.

tulsaplanning.org has two name servers: ns1.tulsaconnect.com and ns2.tulsaconnect.com.

tulsaplanning.org shares the same name server setup as other domains, for example custommedals.com, tulsaboards.org, tgovonline.org, mbo4.net and pet-adopt.org.

tulsaplanning.org shares some name servers with other domains, for example rogerscounty.org, dcs-us.com, bmcletterservice.info, tulsataxlaw.com and cityoftulsa.org.

These name servers are commonly used together with ns2.familynet.net and ns.familynet.net.

Host names with a single IP:

tulsaplanning.org is served by two mail servers: mx1.tulsaconnect.com and mx2.tulsaconnect.com.

tulsaplanning.org shares the mail server setup with other domains, for example okmag.com, nexusfundraising.com, sponsoredtuition.com, deltamfg.com and bluestarrchurch.com.

tulsaplanning.org shares some mail servers with other domains, at least partially; for instance istips.net, calefamily.com, chamberweblink.com, okcgold.com and parksidetulsa.org.