forensicupdate.com - dns.ninja

`forensicupdate.com`

DNSSEC	⚠️ Not signed
NS	`ns1.mydomain.com` ⭐
		A	172.64.52.99^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.mydomain.com`
		A	172.64.53.76^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx.mydomain.com` ⭐
		A	66.96.140.64^{🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc.}
			PTR	`64.140.96.66.static.eigbox.net`
		A	66.96.140.65^{🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc.}
			PTR	`65.140.96.66.static.eigbox.net`
MX	`mx.forensicupdate.com`⁽³⁰⁾
		A	66.96.140.182^{🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc.}
			PTR	`182.140.96.66.static.eigbox.net`
		A	66.96.140.183^{🇺🇸 EIG-2987366.96.128.0/18 Newfold Digital, Inc.}
			PTR	`183.140.96.66.static.eigbox.net`
SOA	`ns1.mydomain.com`dnsadmin@mydomain.com 2016-01-09 #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=1786437424

Subdomains

mx.forensicupdate.com

Same first word

forensicupdate.com

DNS History

6 records (4 active, 2 former)

●NSns1.mydomain.com2015-05-19 → 2026-08-11 · 2 obs

● 2015-05-19 12:45:04
● 2026-08-11 08:48:04

●NSns2.mydomain.com2015-05-19 → 2026-08-11 · 2 obs

● 2015-05-19 12:45:04
● 2026-08-11 08:48:04

●MXmx.forensicupdate.com2016-01-13 → 2026-08-11 · 3 obs

○ 2015-10-21 19:19:28
● 2016-01-13 23:32:50
● 2026-08-11 08:48:04

●MXmx.mydomain.com2015-05-19 → 2026-08-11 · 6 obs

● 2015-05-19 12:45:04
● 2015-10-21 19:19:28
○ 2016-01-13 23:32:50
○ 2017-06-06 08:28:34
● 2026-03-26 20:58:08
● 2026-08-11 08:48:04

○A66.96.149.12016-04-14 → 2017-06-06 · 4 obs

○ 2016-01-13 23:32:50
● 2016-04-14 10:07:24
● 2017-06-06 08:28:34
○ 2026-08-11 08:48:04

○A66.96.163.1362015-05-19 → 2016-01-13 · 4 obs

● 2015-05-19 12:45:04
● 2016-01-13 23:32:50
○ 2016-04-14 10:07:24
○ 2026-08-11 08:48:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
forensicupdate.com	ns1.mydomain.com, ns2.mydomain.com	2 records

✅ Authoritative Response

Server:172.64.53.76

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for forensicupdate.com (unsigned zone)

⏱️ Timing

Total: 2054ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.96.149.1`
NS	2	`ns2.mydomain.com, ns1.mydomain.com`
MX	2	`mx.forensicupdate.com (pri: 30), mx.mydomain.com (pri: 10)`
SOA	1	`ns1.mydomain.com dnsadmin.mydomain.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

mx.forensicupdate.com is a subdomain of forensicupdate.com.

Name Servers

The NS records for forensicupdate.com delegate to ns1.mydomain.com and ns2.mydomain.com.

The name server configuration of forensicupdate.com is shared with other domains, for instance kimor.com, westernwatersolutions.com, califoniataxlaw.com and two others.

The name servers of forensicupdate.com overlap at least partially with those of other domains — among them magneticsonlinestore.com, bestrust.org, bamagram.com and two more.

These name servers commonly co-occur with the name servers ns3.mydomain.com, ns4.mydomain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.

Both ns1.mydomain.com and ns2.mydomain.com have a single IP address each — ns1.mydomain.com resolves to 172.64.52.99 while ns2.mydomain.com resolves to 172.64.53.76.

Mail Servers

forensicupdate.com uses two mail servers, mx.forensicupdate.com and mx.mydomain.com.

At least some of the mail servers used by forensicupdate.com are shared with other domains: fm-cps.org, accs-blog.hebrewbooks.org, linguacentres.com and two others among them.

It is common to find these mail servers paired with the mail servers aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com, as well as two others.

mx.forensicupdate.com resolves to 66.96.140.182 and 66.96.140.183. Likewise, mx.mydomain.com resolves to 66.96.140.64 and 66.96.140.65 — two IP addresses apiece.