midmainechamber.com - dns.ninja

`midmainechamber.com`

DNSSEC	⚠️ Not signed
A	162.211.83.226^{🇺🇸 PRIVATESYSTEMS162.211.80.0/22 PrivateSystems Networks MD}
NS	`ns39.domaincontrol.com` ⭐
		A	2603:5:21d1::14^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns39.domaincontrol.com`
		A	97.74.109.20^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns39.domaincontrol.com`
NS	`ns40.domaincontrol.com`
		A	2603:5:22d1::14^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns40.domaincontrol.com`
		A	173.201.77.20^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns40.domaincontrol.com`
MX	`midmainechamber-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00505.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c903::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr02cu00503.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr03cu00401.inbound.protection.outlook.com`
		A	52.101.9.20^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl0pr02cu00604.inbound.protection.outlook.com`
		A	52.101.9.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00205.inbound.protection.outlook.com`
		A	52.101.10.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr03cu00202.inbound.protection.outlook.com`
		A	52.101.50.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00605.inbound.protection.outlook.com`
TXT	`MS=ms88872180`
TXT	`v=spf1 include:spf.protection.outlook.com ip4:162.255.162.231 ip4:162.255.162...`
TXT	`google-site-verification=IEM9tEMEsbcbQTueMkQF2pSQPIb35OgKQwmWjpQvqqw`
SOA	`ns39.domaincontrol.com`dns@jomax.net 2024-11-26 #4

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

WOT: UNKNOWN (68/100)

Previously MX for

midmainechamber.com

Same first word

midmainechamber.com

DNS History

11 records (4 active, 7 former)

○NSns1.secure.net2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 05:08:46
○ 2015-06-16 17:23:20
○ 2026-08-13 10:41:32

○NSns2.secure.net2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 05:08:46
○ 2015-06-16 17:23:20
○ 2026-08-13 10:41:32

●NSns39.domaincontrol.com2015-06-16 → 2026-08-13 · 3 obs

○ 2007-11-13 05:08:46
● 2015-06-16 17:23:20
● 2026-08-13 10:41:32

●NSns40.domaincontrol.com2015-06-16 → 2026-08-13 · 3 obs

○ 2007-11-13 05:08:46
● 2015-06-16 17:23:20
● 2026-08-13 10:41:32

○MXin.sjc.mx.trendmicro.com2015-06-16 → 2015-06-16 · 4 obs

○ 2007-11-13 05:08:46
● 2015-06-16 17:23:20
○ 2015-10-30 11:54:56
○ 2026-08-13 10:41:32

●MXmidmainechamber-com.mail.protection.outlook.com2015-10-30 → 2026-08-13 · 3 obs

○ 2015-06-16 17:23:20
● 2015-10-30 11:54:56
● 2026-08-13 10:41:32

○MXmidmainechamber.com2007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 05:08:46
○ 2015-06-16 17:23:20
○ 2026-08-13 10:41:32

○A128.121.100.172007-11-13 → 2007-11-13 · 3 obs

● 2007-11-13 05:08:46
○ 2015-06-16 17:23:20
○ 2026-08-13 10:41:32

○A162.144.65.1852015-06-16 → 2016-07-13 · 5 obs

○ 2007-11-13 05:08:46
● 2015-06-16 17:23:20
● 2016-07-13 07:25:32
○ 2017-04-04 08:17:42
○ 2026-08-13 10:41:32

○A162.211.80.1092017-04-04 → 2017-11-02 · 5 obs

○ 2016-07-13 07:25:32
● 2017-04-04 08:17:42
● 2017-11-02 01:11:06
○ 2026-03-16 08:39:04
○ 2026-08-13 10:41:32

●A162.211.83.2262026-03-16 → 2026-08-13 · 3 obs

○ 2017-11-02 01:11:06
● 2026-03-16 08:39:04
● 2026-08-13 10:41:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, h.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net...	-
midmainechamber.com	ns39.domaincontrol.com, ns40.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.77.20

NS records: ns39.domaincontrol.com, ns40.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for midmainechamber.com (unsigned zone)

⏱️ Timing

Total: 140ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.211.83.226`
NS	2	`ns39.domaincontrol.com, ns40.domaincontrol.com`
MX	1	`midmainechamber-com.mail.protection.outl`
TXT	3	`MS=ms88872180, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns39.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns39.domaincontrol.com, ns39.domaincontrol.com, ns40.domaincontrol.com...)

Analysis

IP Addresses

midmainechamber.com resolves to just one IP address, 162.211.83.226.

Host names such as midmaineb2b.com and ns2.a2zcomputing4.com share IP numbers with midmainechamber.com.

Name Servers

midmainechamber.com is delegated to two name servers: ns39.domaincontrol.com and ns40.domaincontrol.com.

midmainechamber.com shares its NS records with other domains, for example shipvisitor.com, studiolou.org, righttheearth.com and two others.

ns39.domaincontrol.com and ns40.domaincontrol.com each resolve to two IP addresses: ns39.domaincontrol.com points to 97.74.109.20 and 2603:5:21d1::14, while ns40.domaincontrol.com points to 173.201.77.20 and 2603:5:22d1::14.

Mail Servers

The sole mail server for midmainechamber.com is midmainechamber-com.mail.protection.outlook.com.

With 8 IP addresses total, midmainechamber-com.mail.protection.outlook.com resolves to 52.101.9.20, 52.101.9.21, 52.101.10.2 and 5 others.