validclick.com - dns.ninja

`validclick.com`

DNSSEC	⚠️ Not signed
NS	`ns1-02.azure-dns.com` ⚠️ Not in zone NS records
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns15.inuvo.com` ⚠️ Not in zone NS records
		A	64.106.255.90^{🇺🇸 DATAPIPE-SEA64.106.248.0/21 NETBLK-DATAPIPE-SJC-3 DataPipe}
			PTR	`ns15.inuvo.com`
NS	`ns16.inuvo.com` ⚠️ Not in zone NS records
		A	66.70.55.134^{🇺🇸 DATAPIPE-SEA66.70.52.0/22 GoGrid/ServePath}
NS	`ns2-02.azure-dns.net` ⚠️ Not in zone NS records
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org` ⚠️ Not in zone NS records
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info` ⚠️ Not in zone NS records
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`

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

⚠️ On DNS blocklist: light, multi, popupads, pro, pro.mini, pro.plus, pro.plus.mini, ultimate, ultimate.mini
WOT: UNKNOWN (23/100)

Subdomains

assets.validclick.com

tracking.validclick.com

feed.validclick.com

admin.validclick.com

mobi.validclick.com

Same first word

validclick.com

validclick.net

validclick.co.uk

DNS History

10 records (6 active, 4 former)

●NSns1-02.azure-dns.com2017-03-23 → 2026-08-03 · 3 obs

○ 2016-07-10 17:05:42
● 2017-03-23 05:32:02
● 2026-08-03 00:30:00

●NSns15.inuvo.com2015-06-15 → 2026-08-03 · 5 obs

● 2015-06-15 06:20:28
● 2016-07-10 17:05:42
○ 2017-03-23 05:32:02
● 2026-02-18 09:58:24
● 2026-08-03 00:30:00

●NSns16.inuvo.com2015-06-15 → 2026-08-03 · 5 obs

● 2015-06-15 06:20:28
● 2016-07-10 17:05:42
○ 2017-03-23 05:32:02
● 2026-02-18 09:58:24
● 2026-08-03 00:30:00

●NSns2-02.azure-dns.net2017-03-23 → 2026-08-03 · 3 obs

○ 2016-07-10 17:05:42
● 2017-03-23 05:32:02
● 2026-08-03 00:30:00

●NSns3-02.azure-dns.org2017-03-23 → 2026-08-03 · 3 obs

○ 2016-07-10 17:05:42
● 2017-03-23 05:32:02
● 2026-08-03 00:30:00

●NSns4-02.azure-dns.info2017-03-23 → 2026-08-03 · 3 obs

○ 2016-07-10 17:05:42
● 2017-03-23 05:32:02
● 2026-08-03 00:30:00

○MXvalidclick-com.mail.eo.outlook.com2015-06-15 → 2017-03-23 · 4 obs

● 2015-06-15 06:20:28
● 2017-03-23 05:32:02
○ 2026-02-18 09:58:24
○ 2026-08-03 00:30:00

○MXvalidclick-com.mail.protection.outlook.com2026-02-18 → 2026-02-18 · 4 obs

○ 2017-03-23 05:32:02
● 2026-02-18 09:58:24
○ 2026-07-30 18:51:32
○ 2026-08-03 00:30:00

○A35.185.45.562026-02-18 → 2026-02-18 · 4 obs

○ 2017-03-23 05:32:02
● 2026-02-18 09:58:24
○ 2026-07-30 18:51:32
○ 2026-08-03 00:30:00

○A65.39.205.612015-06-15 → 2017-03-23 · 4 obs

● 2015-06-15 06:20:28
● 2017-03-23 05:32:02
○ 2026-02-18 09:58:24
○ 2026-08-03 00:30:00

🔍 DNS Trace

Analysis

Hierarchy

validclick.com is the parent of assets.validclick.com, tracking.validclick.com, feed.validclick.com, admin.validclick.com and mobi.validclick.com.

Name Servers

validclick.com delegates authority to 6 name servers: ns1-02.azure-dns.com, ns15.inuvo.com, ns16.inuvo.com plus 3 other.

validclick.com has at least partial name server overlap with other domains, such as modecontracts.com, 190.172.in-addr.arpa, loyalty-cloud.net and two others.

These name servers tend to appear together with the name servers ns3-02.azure-dns.org, ns4-02.azure-dns.info and ns2-02.azure-dns.net.

Hosts with two IP numbers each:

ns1-02.azure-dns.com directs traffic to 13.107.236.2 and 2603:1061:0:700::2.

ns4-02.azure-dns.info directs traffic to 208.84.5.2 and 2620:1ec:bda:700::2.

ns2-02.azure-dns.net directs traffic to 150.171.21.2 and 2620:1ec:8ec:700::2.

ns3-02.azure-dns.org directs traffic to 204.14.183.2 and 2a01:111:4000:700::2.

Hosts that resolve to one IP address:

ns15.inuvo.com has the IP address 64.106.255.90.

ns16.inuvo.com has the IP address 66.70.55.134.