🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`usdataforensics.com`

DNSSEC	🔒 Signed (DS record present)
A	23.236.62.147^{🇺🇸 Google23.236.62.0/24}
		PTR	`147.62.236.23.bc.googleusercontent.com`
NS	`ns-cloud-a1.googledomains.com` ⭐
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com`
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`
NS	`ns-cloud-a3.googledomains.com`
		A	2001:4860:4802:36::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a3.googledomains.com`
		A	216.239.36.106^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-a3.googledomains.com`
NS	`ns-cloud-a4.googledomains.com`
		A	2001:4860:4802:38::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a4.googledomains.com`
		A	216.239.38.106^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-a4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4010:c22::1a^{🇫🇮 Google2a00:1450:4010::/48}
			PTR	`yulpptr-in-f26.1e100.net`
		A	172.253.152.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yulpptr-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2404:6800:4000:1027::1b^{🇮🇳 Google2404:6800::/32}
			PTR	`ncboms-in-f27.1e100.net`
		A	192.179.20.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncboms-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-cloud-a1.googledomains.com`cloud-dns-hostmaster@google.com serial=12

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

Same first word

usdataforensics.com

Previous names

Next names

DNS History

24 records (10 active, 14 former)

○NSdns1.name-services.com2008-03-19 → 2017-11-14 · 4 obs

● 2008-03-19 12:51:38
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

○NSdns2.name-services.com2008-03-19 → 2017-11-14 · 4 obs

● 2008-03-19 12:51:38
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

○NSdns3.name-services.com2008-03-19 → 2017-11-14 · 4 obs

● 2008-03-19 12:51:38
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

○NSdns4.name-services.com2008-03-19 → 2017-11-14 · 4 obs

● 2008-03-19 12:51:38
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

○NSdns5.name-services.com2008-03-19 → 2017-11-14 · 4 obs

● 2008-03-19 12:51:38
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

●NSns-cloud-a1.googledomains.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●NSns-cloud-a2.googledomains.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●NSns-cloud-a3.googledomains.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●NSns-cloud-a4.googledomains.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●MXalt1.aspmx.l.google.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●MXalt2.aspmx.l.google.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●MXalt3.aspmx.l.google.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●MXalt4.aspmx.l.google.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

●MXaspmx.l.google.com2026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

○MXeforward3.name-services.com2008-03-19 → 2008-03-19 · 3 obs

● 2008-03-19 12:51:38
○ 2015-06-04 08:42:00
○ 2026-11-10 17:43:58

○MXeforwardct.name-services.com2008-03-19 → 2016-09-13 · 4 obs

● 2008-03-19 12:51:38
● 2016-09-13 23:25:58
○ 2017-11-14 06:20:10
○ 2026-11-10 17:43:58

○MXeforwardct2.name-services.com2015-06-04 → 2016-09-13 · 5 obs

○ 2008-03-19 12:51:38
● 2015-06-04 08:42:00
● 2016-09-13 23:25:58
○ 2017-11-14 06:20:10
○ 2026-11-10 17:43:58

○MXeforwardct3.name-services.com2015-06-04 → 2016-09-13 · 5 obs

○ 2008-03-19 12:51:38
● 2015-06-04 08:42:00
● 2016-09-13 23:25:58
○ 2017-11-14 06:20:10
○ 2026-11-10 17:43:58

○MXmx.usdataforensics.com.cust.a.hostedemail.com2017-11-14 → 2017-11-14 · 4 obs

○ 2016-09-13 23:25:58
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

●A23.236.62.1472026-09-18 → 2026-11-10 · 3 obs

○ 2017-11-14 06:20:10
● 2026-09-18 08:39:32
● 2026-11-10 17:43:58

○A63.251.92.1972008-03-19 → 2008-03-19 · 3 obs

● 2008-03-19 12:51:38
○ 2015-06-04 08:42:00
○ 2026-11-10 17:43:58

○A98.124.198.12015-06-04 → 2015-10-20 · 5 obs

○ 2008-03-19 12:51:38
● 2015-06-04 08:42:00
● 2015-10-20 01:09:56
○ 2016-01-05 10:11:54
○ 2026-11-10 17:43:58

○A98.124.199.12015-06-04 → 2015-06-04 · 4 obs

○ 2008-03-19 12:51:38
● 2015-06-04 08:42:00
○ 2017-11-14 06:20:10
○ 2026-11-10 17:43:58

○A98.124.199.862016-01-05 → 2017-11-14 · 5 obs

○ 2015-10-20 01:09:56
● 2016-01-05 10:11:54
● 2017-11-14 06:20:10
○ 2026-09-18 08:39:32
○ 2026-11-10 17:43:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net...	-
usdataforensics.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.38.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 593ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`23.236.62.147`
NS	4	`ns-cloud-a3.googledomains.com, ns-cloud-a1.googledomains.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-a1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

IP Addresses

usdataforensics.com resolves to just one IP address, 23.236.62.147.

Two other host names, along with hikinghomes.com, themfgproject.com and bnzr.it, also share IP numbers with usdataforensics.com.

Name Servers

The NS records for usdataforensics.com point to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

usdataforensics.com has at least partial name server overlap with other domains, such as protocolloscudo180.com, bdiexperience.com, blacklabelshoppe.com and two others.

ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com all point to exactly two IP numbers each: ns-cloud-a1.googledomains.com → 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com → 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com → 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com → 216.239.38.106 and 2001:4860:4802:38::6a.

Mail Servers

usdataforensics.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between usdataforensics.com and other domains, including treslucy.com, groovetradingtech.it, amica.jp and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 142.251.163.26 and 2607:f8b0:4004:c25::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 172.253.152.26 and 2a00:1450:4010:c22::1a.

alt4.aspmx.l.google.com directs traffic to 192.179.20.27 and 2404:6800:4000:1027::1b.