`leadcounts.com`

DNSSEC	⚠️ Not signed
NS	`ns1.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns2.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns3.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns4.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns5.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns6.performanetwork.com` ⚠️ Not in zone NS records
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`

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

WOT: SAFE (8/100)

Same first word

leadcounts.com

Similar names

DNS History

15 records (6 active, 9 former)

●NSns1.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

○NSns1.shiftcode.com2015-07-08 → 2020-02-17 · 4 obs

● 2015-07-08 02:17:44
● 2020-02-17 21:33:40
○ 2026-04-25 06:27:18
○ 2026-06-09 08:57:26

●NSns2.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

●NSns3.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

●NSns4.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

●NSns5.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

●NSns6.performanetwork.com2026-04-25 → 2026-06-09 · 3 obs

○ 2020-02-17 21:33:40
● 2026-04-25 06:27:18
● 2026-06-09 08:57:26

○MXcp13-tx.privatesystems.net2020-02-17 → 2020-02-17 · 4 obs

○ 2017-03-14 17:39:42
● 2020-02-17 21:33:40
○ 2026-04-25 06:27:18
○ 2026-06-09 08:57:26

○MXmail.leadcounts.com2015-07-08 → 2017-03-14 · 4 obs

● 2015-07-08 02:17:44
● 2017-03-14 17:39:42
○ 2020-02-17 21:33:40
○ 2026-06-09 08:57:26

○A104.243.43.1402015-11-10 → 2015-11-10 · 4 obs

○ 2015-07-08 02:17:44
● 2015-11-10 08:36:06
○ 2016-02-27 00:57:14
○ 2026-06-09 08:57:26

○A144.202.20.1902020-02-17 → 2020-02-17 · 4 obs

○ 2017-03-14 17:39:42
● 2020-02-17 21:33:40
○ 2026-04-25 06:27:18
○ 2026-06-09 08:57:26

○A45.58.114.1952015-07-08 → 2015-07-08 · 3 obs

● 2015-07-08 02:17:44
○ 2015-11-10 08:36:06
○ 2026-06-09 08:57:26

○A45.58.114.2312016-02-27 → 2016-02-27 · 4 obs

○ 2015-11-10 08:36:06
● 2016-02-27 00:57:14
○ 2016-06-23 04:42:06
○ 2026-06-09 08:57:26

○A45.58.114.2412017-03-14 → 2017-03-14 · 4 obs

○ 2016-06-23 04:42:06
● 2017-03-14 17:39:42
○ 2020-02-17 21:33:40
○ 2026-06-09 08:57:26

○A45.58.118.42016-06-23 → 2016-06-23 · 4 obs

○ 2016-02-27 00:57:14
● 2016-06-23 04:42:06
○ 2017-03-14 17:39:42
○ 2026-06-09 08:57:26

🔍 DNS Trace

Analysis

Name Servers

leadcounts.com is served by 6 authoritative name servers: ns1.performanetwork.com, ns2.performanetwork.com, ns3.performanetwork.com and three additional ones.

These name servers are frequently paired with the name servers ns4.performanetwork.com, ns5.performanetwork.com and ns6.performanetwork.com.

Host names resolving to 4 IP numbers:

ns1.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns2.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns3.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns4.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns5.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns6.performanetwork.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

Multiple host names resolve to 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb, among them ns1.performanetwork.com, ns2.performanetwork.com, ns3.performanetwork.com and three others.

Multiple host names resolve to 2600:1f18:4ae:c606:78d4:4260:db4e:aeee, among them ns1.performanetwork.com, ns2.performanetwork.com, ns3.performanetwork.com and three others.

Multiple host names resolve to 13.223.25.84, among them ns1.performanetwork.com, ns2.performanetwork.com, ns3.performanetwork.com and three others.

Multiple host names resolve to 54.243.117.197, among them ns1.performanetwork.com, ns2.performanetwork.com, ns3.performanetwork.com and three others.

leadcounts.com - dns.ninja

leadcounts.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

Analysis

Name Servers

`leadcounts.com`

`com`