`informmedengage.com`

DNSSEC	⚠️ Not signed
A	65.242.240.117^{🇺🇸 AS70165.240.0.0/13 MCI Communications Services, LLC d/b/a Verizon Business}
NS	`ns1.dmonesource.com` ⭐
		A	65.220.97.203^{🇺🇸 AS70165.192.0.0/11 MCI Communications Services, LLC d/b/a Verizon Business}
NS	`ns2.dmonesource.com`
		A	65.220.97.204^{🇺🇸 AS70165.192.0.0/11 MCI Communications Services, LLC d/b/a Verizon Business}
MX	`mail.informmedengage.com` ⭐
TXT	`v=spf1 ip4:65.242.240.117 -all`
TXT	`google-site-verification=oXkQwZXd6o8JBZJlzPnUSRu2awvEL-iikbC5OXBdpUI`
TXT	`spf2.0/pra ip4:65.242.240.117 -all`
SOA	`ns1.dmonesource.com`hostmaster@dmonesource.com serial=5

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

Same first word

informmedengage.com

DNS History

9 records (4 active, 5 former)

○NSdns1.idp365.net2018-08-30 → 2018-08-30 · 3 obs

● 2018-08-30 05:11:40
○ 2026-04-07 10:10:20
○ 2026-04-14 05:12:56

○NSdns2.idp365.net2018-08-30 → 2018-08-30 · 3 obs

● 2018-08-30 05:11:40
○ 2026-04-07 10:10:20
○ 2026-04-14 05:12:56

○NSdns3.idp365.net2018-08-30 → 2018-08-30 · 3 obs

● 2018-08-30 05:11:40
○ 2026-04-07 10:10:20
○ 2026-04-14 05:12:56

●NSns1.dmonesource.com2026-04-07 → 2026-04-14 · 3 obs

○ 2018-08-30 05:11:40
● 2026-04-07 10:10:20
● 2026-04-14 05:12:56

●NSns2.dmonesource.com2026-04-07 → 2026-04-14 · 3 obs

○ 2018-08-30 05:11:40
● 2026-04-07 10:10:20
● 2026-04-14 05:12:56

○MXmail.idp365.net2018-08-30 → 2018-08-30 · 3 obs

● 2018-08-30 05:11:40
○ 2026-04-07 10:10:20
○ 2026-04-14 05:12:56

●MXmail.informmedengage.com2026-04-07 → 2026-04-14 · 3 obs

○ 2018-08-30 05:11:40
● 2026-04-07 10:10:20
● 2026-04-14 05:12:56

○A217.19.248.1322018-08-30 → 2018-08-30 · 3 obs

● 2018-08-30 05:11:40
○ 2026-04-07 10:10:20
○ 2026-04-14 05:12:56

●A65.242.240.1172026-04-07 → 2026-04-14 · 3 obs

○ 2018-08-30 05:11:40
● 2026-04-07 10:10:20
● 2026-04-14 05:12:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net...	-
informmedengage.com	ns1.dmonesource.com, ns2.dmonesource.com	2 records

✅ Authoritative Response

Server:65.220.97.203

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for informmedengage.com (unsigned zone)

⏱️ Timing

Total: 3479ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`65.242.240.117`
NS	2	`ns1.dmonesource.com, ns2.dmonesource.com`
MX	1	`mail.informmedengage.com (pri: 20)`
TXT	3	`google-site-verification=oXkQwZXd6o8JBZJ, spf2.0/pra ip4:65.242.240.117 -all...`
SOA	1	`ns1.dmonesource.com hostmaster.dmonesour`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

informmedengage.com points to a single IP: 65.242.240.117.

Name Servers

informmedengage.com's delegation is to two name servers ns1.dmonesource.com and ns2.dmonesource.com.

informmedengage.com shares the same name server configuration as other domains, such as 152.68.119.63.in-addr.arpa, pentonmeddir.com, forbesdigit.com, mtgmediadirect.com and 96.159.217.65.in-addr.arpa.

informmedengage.com at least partially shares its name servers with other domains, for instance 101.36.252.208.in-addr.arpa, 1105broadcast.com, forbesmediamag.com, ubmtech-direct.com and informareachmed.com.

Host names with a single IP:

ns1.dmonesource.com resolves to 65.220.97.203.

ns2.dmonesource.com resolves to 65.220.97.204.

Mail Servers

informmedengage.com is served by a single mail server, mail.informmedengage.com.

informmedengage.com - robtex.com