lead-connection.com - dns.ninja

`lead-connection.com`

DNSSEC	⚠️ Not signed
A	13.248.243.5^{🇺🇸 Amazon13.248.240.0/20}
		PTR	`a16e665f42988324c.awsglobalaccelerator.com`
A	76.223.105.230^{🇺🇸 Amazon76.223.96.0/20}
NS	`ns31.domaincontrol.com` ⭐
		A	2603:5:2191::10^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns31.domaincontrol.com`
		A	97.74.105.16^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns31.domaincontrol.com`
NS	`ns32.domaincontrol.com`
		A	2603:5:2291::10^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns32.domaincontrol.com`
		A	173.201.73.16^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns32.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c0b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bj-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=17t6Fv0o1AoYSjNYqkG7YjGFgqj3ayXF2RjLysVi2AM`
TXT	`v=spf1 include:dc-aa8e722993._spfm.lead-connection.com ~all`
SOA	`ns31.domaincontrol.com`dns@jomax.net 2023-10-17 #3

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

Same first word

lead-connection.com

DNS History

25 records (9 active, 16 former)

○NSns1.wiredtree.com2009-01-14 → 2009-01-14 · 3 obs

● 2009-01-14 21:42:08
○ 2015-11-10 08:35:56
○ 2026-08-11 00:03:00

○NSns2.wiredtree.com2009-01-14 → 2009-01-14 · 3 obs

● 2009-01-14 21:42:08
○ 2015-11-10 08:35:56
○ 2026-08-11 00:03:00

●NSns31.domaincontrol.com2026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

●NSns32.domaincontrol.com2026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

○NSns43.domaincontrol.com2018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○NSns44.domaincontrol.com2018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

●MXalt1.aspmx.l.google.com2018-08-24 → 2026-08-11 · 3 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
● 2026-08-11 00:03:00

●MXalt2.aspmx.l.google.com2018-08-24 → 2026-08-11 · 3 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
● 2026-08-11 00:03:00

●MXalt3.aspmx.l.google.com2026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

●MXalt4.aspmx.l.google.com2026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

●MXaspmx.l.google.com2018-08-24 → 2026-08-11 · 3 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
● 2026-08-11 00:03:00

○MXaspmx2.googlemail.com2018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○MXaspmx3.googlemail.com2018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○MXmail.lead-connection.com2009-01-14 → 2009-01-14 · 3 obs

● 2009-01-14 21:42:08
○ 2015-11-10 08:35:56
○ 2026-08-11 00:03:00

●A13.248.243.52026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

○A184.168.221.412018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A184.168.221.442018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A209.188.86.2282009-01-14 → 2009-01-14 · 3 obs

● 2009-01-14 21:42:08
○ 2015-11-10 08:35:56
○ 2026-08-11 00:03:00

○A50.63.202.412018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A50.63.202.492018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A50.63.202.512018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A50.63.202.542018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A50.63.202.552018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

○A50.63.202.632018-08-24 → 2018-08-24 · 4 obs

○ 2015-11-10 08:35:56
● 2018-08-24 18:04:08
○ 2026-03-12 13:42:36
○ 2026-08-11 00:03:00

●A76.223.105.2302026-03-12 → 2026-08-11 · 3 obs

○ 2018-08-24 18:04:08
● 2026-03-12 13:42:36
● 2026-08-11 00:03:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
lead-connection.com	ns31.domaincontrol.com, ns32.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.73.16

NS records: ns31.domaincontrol.com, ns32.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 982ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.105.230, 13.248.243.5`
NS	2	`ns31.domaincontrol.com, ns32.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=17t6Fv0o1AoYSjN, v=spf1 include:dc-aa8e722993._spfm.lead-`
SOA	1	`ns31.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns31.domaincontrol.com, ns31.domaincontrol.com, ns32.domaincontrol.com...)

Analysis

IP Addresses

lead-connection.com directs to two IP numbers, 13.248.243.5 and 76.223.105.230

hktech.co.in, upho-ld-logi.godaddysites.com, djlancereynolds.com plus two other host names have IP numbers in common with lead-connection.com.

Name Servers

lead-connection.com is delegated to two name servers: ns31.domaincontrol.com and ns32.domaincontrol.com.

The name server configuration of lead-connection.com is shared with other domains, for instance sneez.com, lsu.photos, maxairinc.net and two others.

ns31.domaincontrol.com and ns32.domaincontrol.com each resolve to two IP addresses: ns31.domaincontrol.com points to 97.74.105.16 and 2603:5:2191::10, while ns32.domaincontrol.com points to 173.201.73.16 and 2603:5:2291::10.

Mail Servers

Mail for lead-connection.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by lead-connection.com are shared with other domains: zakarija.com, 1stcapfin.com, foodguides.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com points to 64.233.180.27 and 2607:f8b0:4004:c0b::1a.

alt1.aspmx.l.google.com points to 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1b.