leadxp.com - dns.ninja

`leadxp.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-d1.googledomains.com` ⭐
		A	2001:4860:4802:32::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-d4.googledomains.com`
SOA	`ns-cloud-d1.googledomains.com`cloud-dns-hostmaster@google.com serial=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=1781461035

Same first word

leadxp.com

Similar names

alexpd.com

plexda.com

adplex.net

adplex.pl

dexpal.com

adplex.ie

dalpex.com

leapxd.net

xpdeal.com

padelx.com

daplex.rs

explad.com

alexdp.com

epdlax.com

paldex.com

adplex.com

pladex.ru

dxleap.com

paxdel.com

alpdex.com

padlex.com

pledax.com

adplex.co.jp

xpedal.com

plaxed.com

leapxd.com

xplead.com

pladex.com

daplex.net

pedalx.com

peldax.com

daplex.com

plexad.com

lapdex.com

xpadel.com

daplex.ru

delpax.com

ledpax.co

leadpx.com

dexpla.com

alpdex.com.br

DNS History

14 records (4 active, 10 former)

●NSns-cloud-d1.googledomains.com2026-03-10 → 2026-06-14 · 3 obs

○ 2017-05-27 06:25:40
● 2026-03-10 14:56:58
● 2026-06-14 18:24:02

●NSns-cloud-d2.googledomains.com2026-03-10 → 2026-06-14 · 3 obs

○ 2017-05-27 06:25:40
● 2026-03-10 14:56:58
● 2026-06-14 18:24:02

●NSns-cloud-d3.googledomains.com2026-03-10 → 2026-06-14 · 3 obs

○ 2017-05-27 06:25:40
● 2026-03-10 14:56:58
● 2026-06-14 18:24:02

●NSns-cloud-d4.googledomains.com2026-03-10 → 2026-06-14 · 3 obs

○ 2017-05-27 06:25:40
● 2026-03-10 14:56:58
● 2026-06-14 18:24:02

○NSns-us.1and1-dns.com2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○NSns-us.1and1-dns.de2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○NSns-us.1and1-dns.org2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○NSns-us.1and1-dns.us2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○MXmx00.1and1.com2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○MXmx01.1and1.com2015-05-21 → 2017-05-27 · 4 obs

● 2015-05-21 03:20:58
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○A216.250.121.1052016-09-14 → 2017-05-27 · 5 obs

○ 2016-04-03 16:25:08
● 2016-09-14 23:37:18
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○A2607:f1c0:1000:1061:3820:aae4:a20a:280d2016-09-14 → 2017-05-27 · 5 obs

○ 2016-04-03 16:25:08
● 2016-09-14 23:37:18
● 2017-05-27 06:25:40
○ 2026-03-10 14:56:58
○ 2026-06-14 18:24:02

○A2607:f1c0:1000:1061:e967:d0e5:aed6:80282015-05-21 → 2016-04-03 · 4 obs

● 2015-05-21 03:20:58
● 2016-04-03 16:25:08
○ 2016-09-14 23:37:18
○ 2026-06-14 18:24:02

○A74.208.42.2412015-05-21 → 2016-04-03 · 4 obs

● 2015-05-21 03:20:58
● 2016-04-03 16:25:08
○ 2016-09-14 23:37:18
○ 2026-06-14 18:24:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
leadxp.com	ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.34.109

NS records: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 326ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com...`
SOA	1	`ns-cloud-d1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-d1.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com...)

Analysis

Name Servers

The authoritative name servers for leadxp.com are ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.

leadxp.com has at least partial name server overlap with other domains, such as ironhorsesafety.net, spaceycowboy.com, iounica.com and two others.

It is common to see these name servers used together with name servers ns1.mirusresearch.com and ns2.mir.us.

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com all point to exactly two IP numbers each: ns-cloud-d1.googledomains.com → 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com → 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com → 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com → 216.239.38.109 and 2001:4860:4802:38::6d.