leadprogroup.com - dns.ninja

`leadprogroup.com`

DNSSEC	⚠️ Not signed
A	68.66.226.121^{🇺🇸 A2HOSTING68.66.224.0/20 A2 Hosting, Inc.}
NS	`ns1.a2hosting.com` ⭐
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
NS	`ns2.a2hosting.com`
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
NS	`ns3.a2hosting.com`
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
NS	`ns4.a2hosting.com`
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c06::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bg-in-f26.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
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}
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 +a +mx +ip4:68.66.226.121 include:spf.a2hosting.com ~all`
SOA	`ns1.a2hosting.com`root@az1-ss105.a2hosting.com 2026-05-30 #1

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

Subdomains

www.leadprogroup.com

Same first word

leadprogroup.com

DNS History

23 records (10 active, 13 former)

○NSdns1.name-services.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○NSdns2.name-services.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○NSdns3.name-services.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○NSdns4.name-services.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○NSdns5.name-services.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

●NSns1.a2hosting.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●NSns2.a2hosting.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●NSns3.a2hosting.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●NSns4.a2hosting.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●MXalt1.aspmx.l.google.com2015-08-15 → 2026-06-28 · 2 obs

● 2015-08-15 01:55:02
● 2026-06-28 03:44:28

●MXalt2.aspmx.l.google.com2015-08-15 → 2026-06-28 · 2 obs

● 2015-08-15 01:55:02
● 2026-06-28 03:44:28

●MXalt3.aspmx.l.google.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●MXalt4.aspmx.l.google.com2026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

●MXaspmx.l.google.com2015-08-15 → 2026-06-28 · 2 obs

● 2015-08-15 01:55:02
● 2026-06-28 03:44:28

○MXaspmx2.googlemail.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○MXaspmx3.googlemail.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○MXaspmx4.googlemail.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○MXaspmx5.googlemail.com2015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○A216.239.32.212015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○A216.239.34.212015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○A216.239.36.212015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

○A216.239.38.212015-08-15 → 2017-06-01 · 4 obs

● 2015-08-15 01:55:02
● 2017-06-01 14:22:40
○ 2026-02-17 15:19:02
○ 2026-06-28 03:44:28

●A68.66.226.1212026-02-17 → 2026-06-28 · 3 obs

○ 2017-06-01 14:22:40
● 2026-02-17 15:19:02
● 2026-06-28 03:44:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
leadprogroup.com	ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com, ns4.a2hosting.com	4 records

✅ Authoritative Response

Server:13.248.158.180

NS records: ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com, ns4.a2hosting.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadprogroup.com (unsigned zone)

⏱️ Timing

Total: 181ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`68.66.226.121`
NS	4	`ns2.a2hosting.com, ns1.a2hosting.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 +a +mx +ip4:68.66.226.121 include`
SOA	1	`ns1.a2hosting.com root.az1-ss105.a2hosti`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com...)

Analysis

Hierarchy

www.leadprogroup.com is delegated beneath leadprogroup.com.

IP Addresses

leadprogroup.com has exactly one IP address — 68.66.226.121.

egraphicsinmotion2.com, averyincorporated.com, mail.sfo.org plus two other host names have IP numbers in common with leadprogroup.com.

Name Servers

Four name servers handle the delegation for leadprogroup.com: ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com and ns4.a2hosting.com.

There is at least partial name server overlap between leadprogroup.com and other domains — onlinefive.com, enviopest.com, ts3cine.com and two more among them.

These name servers regularly appear alongside ns1.a2webhosting.com, ns2.a2webhosting.com, ns1.supercp.com and 3 other name servers in NS record sets.

Four host names, each with one IP address: ns1.a2hosting.com has 13.248.158.180, ns2.a2hosting.com has 75.2.118.134, ns3.a2hosting.com has 76.223.26.245 and ns4.a2hosting.com has 99.83.147.209.

Mail Servers

leadprogroup.com has five mail servers, which are 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 leadprogroup.com are shared with other domains: cemaer.org, ns500731.ns500731.ns500731.ns500742.ns500754.ns500688.ns500688.ns500705.ns500688.ns500649.ns500291.ns500291.ns500291.ns500291.ns500131.lustychickser.com, ns500724.ns500724.ns500737.ns500599.ns500599.ns500724.ns500724.ns500737.ns500737.ns500599.ns500583.ns500599.ns500697.ns500631.www.yummyflingsfinder.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 resolves to two addresses: 142.251.167.27 and 2607:f8b0:4004:c06::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.

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

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.