lead2connect.com - dns.ninja

`lead2connect.com`

DNSSEC	⚠️ Not signed
A	162.159.140.166^{Cloudflare162.159.128.0/19 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`jule.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3aaf^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jule.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0af^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jule.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20af^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jule.ns.cloudflare.com`
		A	108.162.192.175^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jule.ns.cloudflare.com`
		A	172.64.32.175^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jule.ns.cloudflare.com`
		A	173.245.58.175^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jule.ns.cloudflare.com`
NS	`ned.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bd2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ned.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1d2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ned.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21d2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ned.ns.cloudflare.com`
		A	108.162.193.210^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ned.ns.cloudflare.com`
		A	172.64.33.210^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ned.ns.cloudflare.com`
		A	173.245.59.210^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ned.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	`google-gws-recovery-domain-verification=54722081`
TXT	`google-gws-recovery-domain-verification=59887187`
TXT	`google-site-verification=tWqxz4ZY8OhV0X3UK2KlvczP1QCpihj5YEuVMSuq8y4`
TXT	`neo-verification=OYfeDFggXd`
TXT	`v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCSLAMzp1eyeygY9oviiKX+V...`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`jule.ns.cloudflare.com`dns@cloudflare.com serial=2407449606

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

Subdomains

www.lead2connect.com

Same first word

lead2connect.com

Similar names

connect2lead.com

DNS History

19 records (6 active, 13 former)

●NSjule.ns.cloudflare.com2026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

●NSned.ns.cloudflare.com2026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

○NSns33.domaincontrol.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○NSns34.domaincontrol.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○NSns71.domaincontrol.com2015-08-07 → 2016-06-20 · 4 obs

● 2015-08-07 04:42:22
● 2016-06-20 23:15:14
○ 2017-02-07 04:37:44
○ 2026-07-31 14:50:12

○NSns72.domaincontrol.com2015-08-07 → 2016-06-20 · 4 obs

● 2015-08-07 04:42:22
● 2016-06-20 23:15:14
○ 2017-02-07 04:37:44
○ 2026-07-31 14:50:12

○MXalt1.aspmx.l.google.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○MXalt2.aspmx.l.google.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○MXaspmx.l.google.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○MXaspmx2.googlemail.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○MXaspmx3.googlemail.com2018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

○MXmailstore1.secureserver.net2015-08-07 → 2016-06-20 · 4 obs

● 2015-08-07 04:42:22
● 2016-06-20 23:15:14
○ 2017-02-07 04:37:44
○ 2026-07-31 14:50:12

●MXroute1.mx.cloudflare.net2026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

●MXroute2.mx.cloudflare.net2026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

●MXroute3.mx.cloudflare.net2026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

○MXsmtp.secureserver.net2015-08-07 → 2016-06-20 · 4 obs

● 2015-08-07 04:42:22
● 2016-06-20 23:15:14
○ 2017-02-07 04:37:44
○ 2026-07-31 14:50:12

●A162.159.140.1662026-02-24 → 2026-07-31 · 3 obs

○ 2018-09-26 11:06:10
● 2026-02-24 22:24:04
● 2026-07-31 14:50:12

○A184.168.221.382015-08-07 → 2016-06-20 · 4 obs

● 2015-08-07 04:42:22
● 2016-06-20 23:15:14
○ 2017-02-07 04:37:44
○ 2026-07-31 14:50:12

○A35.176.138.822018-09-26 → 2018-09-26 · 4 obs

○ 2017-02-07 04:37:44
● 2018-09-26 11:06:10
○ 2026-02-24 22:24:04
○ 2026-07-31 14:50:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
lead2connect.com	ned.ns.cloudflare.com, jule.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.210

NS records: ned.ns.cloudflare.com, jule.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lead2connect.com (unsigned zone)

⏱️ Timing

Total: 209ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.159.140.166`
NS	2	`jule.ns.cloudflare.com, ned.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 16), route3.mx.cloudflare.net (pri: 16)...`
TXT	6	`google-gws-recovery-domain-verification=, google-gws-recovery-domain-verification=...`
SOA	1	`jule.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

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

Analysis

Hierarchy

lead2connect.com is the parent zone for www.lead2connect.com.

IP Addresses

lead2connect.com points to a single IP number: 162.159.140.166.

Additional host names — aemira.com, homecareoperations.com, dynasty5.com and two others — share IP numbers with lead2connect.com.

Name Servers

lead2connect.com has two authoritative name servers — jule.ns.cloudflare.com and ned.ns.cloudflare.com.

lead2connect.com shares its name server setup with other domains, including 2supruga.ru, ethical-clothing.com, danieladecastro.es and two others.

lead2connect.com partially shares its NS delegation with several other domains, including dftlwl.com, dlaverickonline.com, 88839888.com and two others.

These name servers are frequently paired with the name servers josephine.ns.cloudflare.com, harlan.ns.cloudflare.com, beau.ns.cloudflare.com and two others.

Host names with 6 IP numbers:

jule.ns.cloudflare.com points to 108.162.192.175, 172.64.32.175, 173.245.58.175 and 3 other IP addresses.

ned.ns.cloudflare.com points to 108.162.193.210, 172.64.33.210, 173.245.59.210 and 3 other IP addresses.

Mail Servers

lead2connect.com uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

lead2connect.com shares mail servers — at least in part — with other domains, including homelifehubpro.com, glowik.pl, kaba-gaida.com and two others.

Host names with 6 IP numbers:

route1.mx.cloudflare.net points to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net points to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net points to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.