`chicagocomputers.com`

DNSSEC	⚠️ Not signed
A	67.217.39.196^{🇺🇸 AS2245867.217.39.0/24}
NS	`ns1.mynex.net` ⭐
		A	67.217.39.194^{🇺🇸 AS2245867.217.39.0/24}
NS	`ns2.mynex.net`
		A	67.217.39.195^{🇺🇸 AS2245867.217.39.0/24}
MX	`chicagocomputers-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:f907::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm1pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f90a::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn8pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f90c::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr03cu00100.inbound.protection.outlook.com`
		A	40.93.192.1^{🇺🇸 Microsoft40.80.0.0/12}
			PTR	`mail-dm5pr02cu00201.inbound.protection.outlook.com`
		A	52.101.8.46^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr05cu00406.inbound.protection.outlook.com`
		A	52.101.10.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr05cu00302.inbound.protection.outlook.com`
		A	52.101.41.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01702.inbound.protection.outlook.com`
TXT	`v=spf1 include:secureserver.net -all`
TXT	`NETORGFT6626064.onmicrosoft.com`
SOA	`ns1.mynex.net`root@localhost 2026-03-04 #1

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

Same first word

chicagocomputers.com

DNS History

14 records (4 active, 10 former)

●NSns1.mynex.net2026-03-16 → 2026-03-17 · 3 obs

○ 2018-01-21 12:51:44
● 2026-03-16 09:16:22
● 2026-03-17 21:35:46

○NSns1052.ui-dns.biz2018-01-21 → 2018-01-21 · 4 obs

○ 2017-01-08 20:15:10
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

○NSns1052.ui-dns.com2018-01-21 → 2018-01-21 · 4 obs

○ 2017-01-08 20:15:10
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

○NSns1052.ui-dns.de2018-01-21 → 2018-01-21 · 4 obs

○ 2017-01-08 20:15:10
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

○NSns1052.ui-dns.org2018-01-21 → 2018-01-21 · 4 obs

○ 2017-01-08 20:15:10
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

●NSns2.mynex.net2026-03-16 → 2026-03-17 · 3 obs

○ 2018-01-21 12:51:44
● 2026-03-16 09:16:22
● 2026-03-17 21:35:46

○NSns27.1and1.com2015-05-29 → 2017-01-08 · 5 obs

○ 2008-03-20 04:22:34
● 2015-05-29 17:42:56
● 2017-01-08 20:15:10
○ 2018-01-21 12:51:44
○ 2026-03-17 21:35:46

○NSns28.1and1.com2015-05-29 → 2017-01-08 · 5 obs

○ 2008-03-20 04:22:34
● 2015-05-29 17:42:56
● 2017-01-08 20:15:10
○ 2018-01-21 12:51:44
○ 2026-03-17 21:35:46

●MXchicagocomputers-com.mail.protection.outlook.com2026-03-16 → 2026-03-17 · 3 obs

○ 2018-01-21 12:51:44
● 2026-03-16 09:16:22
● 2026-03-17 21:35:46

○MXmx00.1and1.com2015-05-29 → 2018-01-21 · 5 obs

○ 2008-03-20 04:22:34
● 2015-05-29 17:42:56
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

○MXmx01.1and1.com2015-05-29 → 2018-01-21 · 5 obs

○ 2008-03-20 04:22:34
● 2015-05-29 17:42:56
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

○A216.250.120.2412017-01-08 → 2018-01-21 · 5 obs

○ 2016-05-07 03:01:18
● 2017-01-08 20:15:10
● 2018-01-21 12:51:44
○ 2026-03-16 09:16:22
○ 2026-03-17 21:35:46

●A67.217.39.1962026-03-16 → 2026-03-17 · 3 obs

○ 2018-01-21 12:51:44
● 2026-03-16 09:16:22
● 2026-03-17 21:35:46

○A74.208.26.572015-05-29 → 2016-05-07 · 5 obs

○ 2008-03-20 04:22:34
● 2015-05-29 17:42:56
● 2016-05-07 03:01:18
○ 2017-01-08 20:15:10
○ 2026-03-17 21:35:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
chicagocomputers.com	ns2.mynex.net, ns1.mynex.net	-

✅ Authoritative Response

Server: 67.217.39.195

NS records: ns2.mynex.net, ns1.mynex.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for chicagocomputers.com (unsigned zone)

⏱️ Timing

Total: 4450ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`67.217.39.196`
NS	2	`ns2.mynex.net, ns1.mynex.net`
MX	1	`chicagocomputers-com.mail.protection.out`
TXT	2	`NETORGFT6626064.onmicrosoft.com, v=spf1 include:secureserver.net -all`
SOA	1	`ns1.mynex.net root.localhost`

Analysis

IP Addresses

chicagocomputers.com points to an IP address: 67.217.39.196.

other host names include infrastructure-defense.com, bobsyeruncle.com, tritanservicesllc.com, h06.mynex.net and airmakerinc.com; they share IP numbers with chicagocomputers.com.

Name Servers

Two name servers ns1.mynex.net and ns2.mynex.net handle the delegation for chicagocomputers.com.

chicagocomputers.com shares the same name server setup as other domains, for instance imcsolutions.com, usaindustrialsupply.net, scs-inc.com, snugglebear.org and gorillacompositepanels.net.

chicagocomputers.com at least partially shares name servers with other domains, such as 207.39.217.67.in-addr.arpa, infrastructure-defense.com and 201.39.217.67.in-addr.arpa.

These name servers are commonly used alongside prime.mynex.net.

Host names with one IP:

ns1.mynex.net points to: 67.217.39.194

ns2.mynex.net points to: 67.217.39.195

Mail Servers

chicagocomputers.com is handled by a single mail server, chicagocomputers-com.mail.protection.outlook.com.

Hostname chicagocomputers-com.mail.protection.outlook.com resolves to eight IP numbers: 2a01:111:f403:c922::2, 2a01:111:f403:f907::1, 2a01:111:f403:f90a::1, 2a01:111:f403:f90c::, 40.93.192.1, 52.101.8.46, 52.101.10.18 and 52.101.41.26.

chicagocomputers.com - robtex.com