lead-track.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lead-track.com`

DNSSEC	⚠️ Not signed
NS	`ns-494.awsdns-61.com` ⭐
		A	2600:9000:5301:ee00::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-494.awsdns-61.com`
		A	205.251.193.238^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-494.awsdns-61.com`
NS	`ns-1338.awsdns-39.org`
		A	2600:9000:5305:3a00::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1338.awsdns-39.org`
		A	205.251.197.58^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1338.awsdns-39.org`
NS	`ns-1617.awsdns-10.co.uk`
		A	2600:9000:5306:5100::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1617.awsdns-10.co.uk`
		A	205.251.198.81^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1617.awsdns-10.co.uk`
NS	`ns-848.awsdns-42.net`
		A	2600:9000:5303:5000::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-848.awsdns-42.net`
		A	205.251.195.80^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-848.awsdns-42.net`
SOA	`ns-494.awsdns-61.com`awsdns-hostmaster@amazon.com serial=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=1786889544

Previously MX for

lead-track.com

Same first word

lead-track.com

lead-track.de

Similar names

data-clerk.store

deal-track.com

data-clerk.ru

track-lead.com

DNS History

9 records (4 active, 5 former)

●NSns-1338.awsdns-39.org2026-03-19 → 2026-08-16 · 3 obs

○ 2018-10-05 10:49:30
● 2026-03-19 19:01:08
● 2026-08-16 14:13:14

●NSns-1617.awsdns-10.co.uk2026-03-19 → 2026-08-16 · 3 obs

○ 2018-10-05 10:49:30
● 2026-03-19 19:01:08
● 2026-08-16 14:13:14

●NSns-494.awsdns-61.com2026-03-19 → 2026-08-16 · 3 obs

○ 2018-10-05 10:49:30
● 2026-03-19 19:01:08
● 2026-08-16 14:13:14

●NSns-848.awsdns-42.net2026-03-19 → 2026-08-16 · 3 obs

○ 2018-10-05 10:49:30
● 2026-03-19 19:01:08
● 2026-08-16 14:13:14

○NSns1.best-trials.com2015-10-24 → 2018-10-05 · 4 obs

● 2015-10-24 20:49:12
● 2018-10-05 10:49:30
○ 2026-03-19 19:01:08
○ 2026-08-16 14:13:14

○NSns2.best-trials.com2015-10-24 → 2018-10-05 · 6 obs

● 2015-10-24 20:49:12
● 2016-04-14 03:46:02
○ 2017-01-25 14:31:22
● 2018-10-05 10:49:30
○ 2026-03-19 19:01:08
○ 2026-08-16 14:13:14

○MXlead-track.com2015-10-24 → 2018-10-05 · 4 obs

● 2015-10-24 20:49:12
● 2018-10-05 10:49:30
○ 2026-03-19 19:01:08
○ 2026-08-16 14:13:14

○A209.87.144.2472015-10-24 → 2016-04-14 · 4 obs

● 2015-10-24 20:49:12
● 2016-04-14 03:46:02
○ 2017-01-25 14:31:22
○ 2026-08-16 14:13:14

○A209.87.149.652017-01-25 → 2018-10-05 · 5 obs

○ 2016-04-14 03:46:02
● 2017-01-25 14:31:22
● 2018-10-05 10:49:30
○ 2026-03-19 19:01:08
○ 2026-08-16 14:13:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net...	-
lead-track.com	ns-494.awsdns-61.com, ns-848.awsdns-42.net, ns-1617.awsdns-10.co.uk, ns-1338.awsdns-39.org	2 records

✅ Authoritative Response

Server:205.251.198.81

NS records: ns-494.awsdns-61.com, ns-848.awsdns-42.net, ns-1617.awsdns-10.co.uk, ns-1338.awsdns-39.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 297ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1338.awsdns-39.org, ns-1617.awsdns-10.co.uk...`
SOA	1	`ns-494.awsdns-61.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-494.awsdns-61.com, ns-494.awsdns-61.com)

Analysis

Name Servers

The domain lead-track.com is delegated to these four name servers: ns-494.awsdns-61.com, ns-848.awsdns-42.net, ns-1338.awsdns-39.org and ns-1617.awsdns-10.co.uk.

At least some of lead-track.com's name servers are shared with other domains, for example sivumestari.fi, dc312.com, datoutdoors.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-494.awsdns-61.com directs to 205.251.193.238 and 2600:9000:5301:ee00::1; ns-848.awsdns-42.net directs to 205.251.195.80 and 2600:9000:5303:5000::1; ns-1338.awsdns-39.org directs to 205.251.197.58 and 2600:9000:5305:3a00::1; ns-1617.awsdns-10.co.uk directs to 205.251.198.81 and 2600:9000:5306:5100::1.