`incidentmitigation.com`

DNSSEC	⚠️ Not signed
NS	`ns35.domaincontrol.com` ⭐
		A	2603:5:21b1::12^{🇺🇸 GODADDY-DNS2603:5:21b0::/44}
			PTR	`ns35.domaincontrol.com`
		A	97.74.107.18^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns35.domaincontrol.com`
NS	`ns36.domaincontrol.com`
		A	2603:5:22b1::12^{🇺🇸 GODADDY-DNS2603:5:22b0::/44}
			PTR	`ns36.domaincontrol.com`
		A	173.201.75.18^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns36.domaincontrol.com`
SOA	`ns35.domaincontrol.com`dns@jomax.net 2026-01-28 #6

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

Previously MX for

incidentmitigation.com

Subdomains

mx.incidentmitigation.com

Same first word

incidentmitigation.com

DNS History

9 records (2 active, 7 former)

○NSns1.hostcentric.com2015-07-24 → 2017-10-12 · 4 obs

● 2015-07-24 12:36:10
● 2017-10-12 09:22:24
○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

○NSns2.hostcentric.com2015-07-24 → 2017-10-12 · 4 obs

● 2015-07-24 12:36:10
● 2017-10-12 09:22:24
○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

●NSns35.domaincontrol.com2026-03-07 → 2026-05-12 · 3 obs

○ 2017-10-12 09:22:24
● 2026-03-07 13:40:02
● 2026-05-12 11:44:06

●NSns36.domaincontrol.com2026-03-07 → 2026-05-12 · 3 obs

○ 2017-10-12 09:22:24
● 2026-03-07 13:40:02
● 2026-05-12 11:44:06

○MXincidentmitigation.com2026-03-07 → 2026-05-12 · 2 obs

○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

○MXmx.incidentmitigation.com2015-07-24 → 2017-10-12 · 4 obs

● 2015-07-24 12:36:10
● 2017-10-12 09:22:24
○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

○A185.183.35.1352026-03-07 → 2026-05-12 · 2 obs

○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

○A65.254.227.2242016-07-09 → 2017-10-12 · 5 obs

○ 2016-03-14 13:51:52
● 2016-07-09 10:12:06
● 2017-10-12 09:22:24
○ 2026-03-07 13:40:02
○ 2026-05-12 11:44:06

○A65.254.228.1002015-07-24 → 2016-03-14 · 4 obs

● 2015-07-24 12:36:10
● 2016-03-14 13:51:52
○ 2016-07-09 10:12:06
○ 2026-05-12 11:44:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net...	-
incidentmitigation.com	ns35.domaincontrol.com, ns36.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.75.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for incidentmitigation.com (unsigned zone)

⏱️ Timing

Total: 740ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns35.domaincontrol.com, ns36.domaincontrol.com`
SOA	1	`ns35.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

Hierarchy

incidentmitigation.com is the parent of mx.incidentmitigation.com.

Name Servers

incidentmitigation.com is delegated to two name servers: ns35.domaincontrol.com and ns36.domaincontrol.com.

incidentmitigation.com uses the same name server setup as other domains such as redi.cash, denismadjar.com, expediare.com, beaconlive.com and legalonlinelottery.net.

incidentmitigation.com shares name servers with other domains at least partially, for example bitracks.com.

Host names with two IP numbers:

ns35.domaincontrol.com points to 2603:5:21b1::12 and 97.74.107.18; ns36.domaincontrol.com points to 2603:5:22b1::12 and 173.201.75.18.

incidentmitigation.com - robtex.com