`lead-flashing.com`

DNSSEC	⚠️ Not signed
A	3.33.152.147^{🇺🇸 Amazon3.33.144.0/20}
		PTR	`a4ec4c6ea1c92e2e6.awsglobalaccelerator.com`
A	15.197.142.173^{🇺🇸 Amazon15.197.128.0/20}
NS	`ns31.domaincontrol.com` ⭐
		A	2603:5:2191::10^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns31.domaincontrol.com`
		A	97.74.105.16^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns31.domaincontrol.com`
NS	`ns32.domaincontrol.com`
		A	2603:5:2291::10^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns32.domaincontrol.com`
		A	173.201.73.16^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns32.domaincontrol.com`
SOA	`ns31.domaincontrol.com`dns@jomax.net 2024-03-06 #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=1783411821

Same first word

lead-flashing.com

DNS History

7 records (4 active, 3 former)

○NSns.123-reg.co.uk2015-05-10 → 2016-07-25 · 4 obs

● 2015-05-10 20:57:56
● 2016-07-25 16:47:28
○ 2026-04-19 13:28:42
○ 2026-07-07 08:10:50

○NSns2.123-reg.co.uk2015-05-10 → 2016-07-25 · 4 obs

● 2015-05-10 20:57:56
● 2016-07-25 16:47:28
○ 2026-04-19 13:28:42
○ 2026-07-07 08:10:50

●NSns31.domaincontrol.com2026-04-19 → 2026-07-07 · 3 obs

○ 2016-07-25 16:47:28
● 2026-04-19 13:28:42
● 2026-07-07 08:10:50

●NSns32.domaincontrol.com2026-04-19 → 2026-07-07 · 3 obs

○ 2016-07-25 16:47:28
● 2026-04-19 13:28:42
● 2026-07-07 08:10:50

●A15.197.142.1732026-04-19 → 2026-07-07 · 3 obs

○ 2017-03-30 12:25:30
● 2026-04-19 13:28:42
● 2026-07-07 08:10:50

●A3.33.152.1472026-04-19 → 2026-07-07 · 3 obs

○ 2017-03-30 12:25:30
● 2026-04-19 13:28:42
● 2026-07-07 08:10:50

○A94.136.40.822015-05-10 → 2017-03-30 · 4 obs

● 2015-05-10 20:57:56
● 2017-03-30 12:25:30
○ 2026-04-19 13:28:42
○ 2026-07-07 08:10:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, f.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net...	-
lead-flashing.com	ns31.domaincontrol.com, ns32.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.105.16

NS records: ns31.domaincontrol.com, ns32.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lead-flashing.com (unsigned zone)

⏱️ Timing

Total: 1239ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.142.173, 3.33.152.147`
NS	2	`ns31.domaincontrol.com, ns32.domaincontrol.com`
SOA	1	`ns31.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns31.domaincontrol.com, ns31.domaincontrol.com, ns32.domaincontrol.com...)

Analysis

IP Addresses

lead-flashing.com has two IP addresses: 3.33.152.147 and 15.197.142.173

homesingoleta.com, topcriminallawyer.ca, joemontagueinsurance.com plus two other host names have IP numbers in common with lead-flashing.com.

Name Servers

DNS delegation for lead-flashing.com points to two name servers: ns31.domaincontrol.com and ns32.domaincontrol.com.

The name server configuration of lead-flashing.com is shared with other domains, for instance fvalley.org, ditmangroup.com, feteevents.com and two others.

lead-flashing.com has partial name server overlap with other domains, including wiz-apps.com.

ns31.domaincontrol.com directs to 97.74.105.16 and 2603:5:2191::10. ns32.domaincontrol.com directs to 173.201.73.16 and 2603:5:2291::10. Each host name carries two IP addresses.

lead-flashing.com - robtex.com