`reynoldsllc.com`

DNSSEC	⚠️ Not signed
A	127.0.0.1
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=201641905

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

reynoldsllc.com

5 records (5 active, 0 former)

●NSns1.tulsaconnect.com2016-06-29 → 2026-05-10 · 2 obs

● 2016-06-29 13:53:50
● 2026-05-10 08:19:24

●NSns2.tulsaconnect.com2016-06-29 → 2026-05-10 · 2 obs

● 2016-06-29 13:53:50
● 2026-05-10 08:19:24

●MXmx1.tulsaconnect.com2016-06-29 → 2026-05-10 · 2 obs

● 2016-06-29 13:53:50
● 2026-05-10 08:19:24

●MXmx2.tulsaconnect.com2016-06-29 → 2026-05-10 · 2 obs

● 2016-06-29 13:53:50
● 2026-05-10 08:19:24

●A127.0.0.12016-06-29 → 2026-05-10 · 2 obs

● 2016-06-29 13:53:50
● 2026-05-10 08:19:24

Zone	Nameservers	Glue
com	b.gtld-servers.net, d.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net...	-
reynoldsllc.com	ns1.tulsaconnect.com, ns2.tulsaconnect.com	2 records

Server:65.38.18.194

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

⚠️ Insecure (no DNSSEC)

No DS record for reynoldsllc.com (unsigned zone)

Total: 452ms | Queries: -

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

Total: 2

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

reynoldsllc.com points to an IP address: 127.0.0.1.

other host names include 254b.com, hk5.edge.bgp.center, immo-weilheim.de, toolnshop.com and wordishimpedor.cyou; they share IP numbers with reynoldsllc.com.

Two name servers ns1.tulsaconnect.com and ns2.tulsaconnect.com handle the delegation for reynoldsllc.com.

reynoldsllc.com shares the same name server setup as other domains, for instance tulsaparks.net, ossaa.com, lyndacurtin.com, isystant.com and tulsaplanning.org.

reynoldsllc.com shares name servers with other domains at least partially, for instance tpibillingsolutions.com, olim.co.il, mackenergy.com and cityoftulsa.net.

Host names with one IP:

reynoldsllc.com is handled by two mail servers: mx1.tulsaconnect.com and mx2.tulsaconnect.com.

reynoldsllc.com uses the same mail server setup as other domains, for instance cartecauto.com, datapointpro.com, omegaemr.com, 211oklahomahelpline.org and epethealth.com.

reynoldsllc.com shares at least partially some mail servers with other domains, for instance istips.us, eauclairebusiness.com, anchor-stone.com, istips.net and calefamily.com.