🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`valid8id.com`

DNSSEC	⚠️ Not signed
A	13.248.243.5^{🇺🇸 Amazon13.248.240.0/20}
		PTR	`a16e665f42988324c.awsglobalaccelerator.com`
A	76.223.105.230^{🇺🇸 Amazon76.223.96.0/20}
NS	`ns13.domaincontrol.com` ⭐
		A	2603:5:21a0::7^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns13.domaincontrol.com`
		A	97.74.106.7^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns13.domaincontrol.com`
NS	`ns14.domaincontrol.com`
		A	2603:5:22a0::7^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns14.domaincontrol.com`
		A	173.201.74.7^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns14.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f27.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.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`google-site-verification=r7GSkODfPlDH4hZa96YfQ4Ezf7KGtM0XSTT3tyQjIQA`
TXT	`google-site-verification=syVS02O3Zm7hJccJFqpZIBTj25oyswEwE_0EJR34EdQ`
SOA	`ns13.domaincontrol.com`dns@jomax.net 2022-10-21 #0

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

Same first word

valid8id.com

Previous names

Next names

DNS History

15 records (9 active, 6 former)

●NSns13.domaincontrol.com2026-08-19 → 2026-08-19 · 3 obs

○ 2017-08-14 11:37:28
● 2026-08-19 14:46:28
● 2026-08-19 16:48:24

●NSns14.domaincontrol.com2026-08-19 → 2026-08-19 · 3 obs

○ 2017-08-14 11:37:28
● 2026-08-19 14:46:28
● 2026-08-19 16:48:24

○NSns27.domaincontrol.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

○NSns28.domaincontrol.com2017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

●MXalt1.aspmx.l.google.com2017-08-14 → 2026-08-19 · 2 obs

● 2017-08-14 11:37:28
● 2026-08-19 16:48:24

●MXalt2.aspmx.l.google.com2017-08-14 → 2026-08-19 · 2 obs

● 2017-08-14 11:37:28
● 2026-08-19 16:48:24

●MXaspmx.l.google.com2017-08-14 → 2026-08-19 · 2 obs

● 2017-08-14 11:37:28
● 2026-08-19 16:48:24

●MXaspmx2.googlemail.com2017-08-14 → 2026-08-19 · 2 obs

● 2017-08-14 11:37:28
● 2026-08-19 16:48:24

●MXaspmx3.googlemail.com2017-08-14 → 2026-08-19 · 2 obs

● 2017-08-14 11:37:28
● 2026-08-19 16:48:24

●A13.248.243.52026-08-19 → 2026-08-19 · 3 obs

○ 2017-08-14 11:37:28
● 2026-08-19 14:46:28
● 2026-08-19 16:48:24

○A160.153.136.32017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

○A182.50.132.2422017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

○A198.71.232.32017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

○A72.167.191.692017-08-14 → 2017-08-14 · 3 obs

● 2017-08-14 11:37:28
○ 2026-08-19 14:46:28
○ 2026-08-19 16:48:24

●A76.223.105.2302026-08-19 → 2026-08-19 · 3 obs

○ 2017-08-14 11:37:28
● 2026-08-19 14:46:28
● 2026-08-19 16:48:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
valid8id.com	ns13.domaincontrol.com, ns14.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.106.7

NS records: ns13.domaincontrol.com, ns14.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for valid8id.com (unsigned zone)

⏱️ Timing

Total: 267ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.105.230, 13.248.243.5`
NS	2	`ns13.domaincontrol.com, ns14.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	2	`google-site-verification=r7GSkODfPlDH4hZ, google-site-verification=syVS02O3Zm7hJcc`
SOA	1	`ns13.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns13.domaincontrol.com, ns13.domaincontrol.com, ns14.domaincontrol.com...)

Analysis

IP Addresses

valid8id.com points to the IP addresses 13.248.243.5 and 76.223.105.230

Two other host names, along with lxyouththeatre.com, javani.net and ghandarva.com, also share IP numbers with valid8id.com.

Name Servers

Two name servers handle the delegation for valid8id.com: ns13.domaincontrol.com and ns14.domaincontrol.com.

valid8id.com shares its NS records with other domains, for example glorywear.net, etvl.org, arnos.us and two others.

valid8id.com is at least partially co-delegated on name servers with other domains, such as mr77777.com.

ns13.domaincontrol.com and ns14.domaincontrol.com both carry two IP addresses. The A records for ns13.domaincontrol.com are 97.74.106.7 and 2603:5:21a0::7; the A records for ns14.domaincontrol.com are 173.201.74.7 and 2603:5:22a0::7.

Mail Servers

valid8id.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between valid8id.com and other domains, including wadeheating.com, vitsoe.net, drcatalina.com and two others.

These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com resolves to two addresses: 142.251.163.26 and 2607:f8b0:4004:c09::1b.

alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.27 IP addresses.