🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`lead2knowledge.com`

DNSSEC	⚠️ Not signed
NS	`merlin.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3bcd^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`merlin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1cd^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`merlin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21cd^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`merlin.ns.cloudflare.com`
		A	108.162.193.205^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`merlin.ns.cloudflare.com`
		A	172.64.33.205^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`merlin.ns.cloudflare.com`
		A	173.245.59.205^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`merlin.ns.cloudflare.com`
NS	`sneh.ns.cloudflare.com`
		A	2606:4700:50::a29f:26a2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sneh.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2a2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sneh.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22a2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sneh.ns.cloudflare.com`
		A	108.162.194.162^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sneh.ns.cloudflare.com`
		A	162.159.38.162^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sneh.ns.cloudflare.com`
		A	172.64.34.162^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sneh.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁷⁷⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁸⁷⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`merlin.ns.cloudflare.com`dns@cloudflare.com serial=2416411592

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

Same first word

lead2knowledge.com

Previous names

Next names

DNS History

14 records (5 active, 9 former)

●NSmerlin.ns.cloudflare.com2026-08-20 → 2026-10-05 · 3 obs

○ 2019-12-20 21:02:18
● 2026-08-20 16:37:44
● 2026-10-05 13:08:14

○NSns1.ipage.com2017-03-13 → 2017-03-13 · 4 obs

○ 2015-10-16 22:40:16
● 2017-03-13 12:51:36
○ 2019-12-20 21:02:18
○ 2026-10-05 13:08:14

○NSns2.ipage.com2017-03-13 → 2017-03-13 · 4 obs

○ 2015-10-16 22:40:16
● 2017-03-13 12:51:36
○ 2019-12-20 21:02:18
○ 2026-10-05 13:08:14

○NSns67.domaincontrol.com2015-06-02 → 2015-06-02 · 3 obs

● 2015-06-02 11:47:02
○ 2015-10-16 22:40:16
○ 2026-10-05 13:08:14

○NSns68.domaincontrol.com2015-06-02 → 2015-06-02 · 3 obs

● 2015-06-02 11:47:02
○ 2015-10-16 22:40:16
○ 2026-10-05 13:08:14

●NSsneh.ns.cloudflare.com2026-08-20 → 2026-10-05 · 3 obs

○ 2019-12-20 21:02:18
● 2026-08-20 16:37:44
● 2026-10-05 13:08:14

○MXmailstore1.secureserver.net2015-06-02 → 2015-06-02 · 3 obs

● 2015-06-02 11:47:02
○ 2015-10-16 22:40:16
○ 2026-10-05 13:08:14

○MXmx.lead2knowledge.com2017-03-13 → 2017-03-13 · 4 obs

○ 2015-10-16 22:40:16
● 2017-03-13 12:51:36
○ 2019-12-20 21:02:18
○ 2026-10-05 13:08:14

●MXroute1.mx.cloudflare.net2026-08-20 → 2026-10-05 · 3 obs

○ 2019-12-20 21:02:18
● 2026-08-20 16:37:44
● 2026-10-05 13:08:14

●MXroute2.mx.cloudflare.net2026-08-20 → 2026-10-05 · 3 obs

○ 2019-12-20 21:02:18
● 2026-08-20 16:37:44
● 2026-10-05 13:08:14

●MXroute3.mx.cloudflare.net2026-08-20 → 2026-10-05 · 3 obs

○ 2019-12-20 21:02:18
● 2026-08-20 16:37:44
● 2026-10-05 13:08:14

○MXsmtp.secureserver.net2015-06-02 → 2015-06-02 · 3 obs

● 2015-06-02 11:47:02
○ 2015-10-16 22:40:16
○ 2026-10-05 13:08:14

○A184.168.221.502015-06-02 → 2015-06-02 · 3 obs

● 2015-06-02 11:47:02
○ 2015-10-16 22:40:16
○ 2026-10-05 13:08:14

○A66.96.147.1442017-03-13 → 2017-03-13 · 4 obs

○ 2015-10-16 22:40:16
● 2017-03-13 12:51:36
○ 2019-12-20 21:02:18
○ 2026-10-05 13:08:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net...	-
lead2knowledge.com	merlin.ns.cloudflare.com, sneh.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.162

NS records: merlin.ns.cloudflare.com, sneh.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lead2knowledge.com (unsigned zone)

⏱️ Timing

Total: 1606ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`merlin.ns.cloudflare.com, sneh.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 61), route3.mx.cloudflare.net (pri: 77)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`merlin.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (merlin.ns.cloudflare.com, merlin.ns.cloudflare.com, merlin.ns.cloudflare.com...)

Analysis

Name Servers

lead2knowledge.com is served by two delegated name servers, merlin.ns.cloudflare.com and sneh.ns.cloudflare.com.

The name server configuration of lead2knowledge.com is shared with other domains, for instance szastral.com, masdailydose.com, storhausbrands.com and two others.

The name servers of lead2knowledge.com overlap at least partially with those of other domains — among them saffronsindian.co.uk, thelittlecornercafe.com, beasocialsuperhero.com and two more.

These name servers commonly appear in combination with the name servers chan.ns.cloudflare.com.

Hosts with 6 IP addresses each:

merlin.ns.cloudflare.com carries IP addresses 108.162.193.205, 172.64.33.205 and 173.245.59.205, with 3 other addresses beyond those.

sneh.ns.cloudflare.com carries IP addresses 108.162.194.162, 162.159.38.162 and 172.64.34.162, with 3 other addresses beyond those.

Mail Servers

Mail for lead2knowledge.com is routed through three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by lead2knowledge.com are shared with other domains: jast.app, stackingprotocol.com, lebensmittelpfad.de and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net carries IP addresses 162.159.205.11, 162.159.205.12 and 162.159.205.13, with 3 other addresses beyond those.

route2.mx.cloudflare.net carries IP addresses 162.159.205.17, 162.159.205.18 and 162.159.205.19, with 3 other addresses beyond those.

route3.mx.cloudflare.net carries IP addresses 162.159.205.23, 162.159.205.24 and 162.159.205.25, with 3 other addresses beyond those.

lead2knowledge.com - robtex.com