leadelephant.com - dns.ninja

`leadelephant.com`

DNSSEC	⚠️ Not signed
A	34.249.196.164^{🇮🇪 Amazon34.248.0.0/13 EC2 DUB prefix}
		PTR	`ec2-34-249-196-164.eu-west-1.compute.amazonaws.com`
A	108.132.219.4^{🇮🇪 Amazon108.128.0.0/13 EC2 DUB prefix}
NS	`ns-1106.awsdns-10.org` ⭐
		A	2600:9000:5304:5200::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1106.awsdns-10.org`
		A	205.251.196.82^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1106.awsdns-10.org`
NS	`ns-2030.awsdns-61.co.uk`
		A	2600:9000:5307:ee00::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-2030.awsdns-61.co.uk`
		A	205.251.199.238^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-2030.awsdns-61.co.uk`
NS	`ns-327.awsdns-40.com`
		A	2600:9000:5301:4700::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-327.awsdns-40.com`
		A	205.251.193.71^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-327.awsdns-40.com`
NS	`ns-642.awsdns-16.net`
		A	2600:9000:5302:8200::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-642.awsdns-16.net`
		A	205.251.194.130^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-642.awsdns-16.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c2d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ry-in-f26.1e100.net`
		A	172.253.115.27^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.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::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.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=jigg2XHcO0LgOif8_u14aDWKVGtd4lUAVF7zADwFvVI`
TXT	`v=spf1 a mx include:spf.autopilothq.com ~all`
SOA	`ns-1106.awsdns-10.org`awsdns-hostmaster@amazon.com serial=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=1785650322

⚠️ On DNS blocklist: multi, pro, pro.plus, ultimate

Subdomains

tracker.leadelephant.com

www.leadelephant.com

Same first word

leadelephant.nl

leadelephant.com

DNS History

20 records (11 active, 9 former)

●NSns-1106.awsdns-10.org2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

●NSns-2030.awsdns-61.co.uk2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

●NSns-327.awsdns-40.com2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

●NSns-642.awsdns-16.net2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

○NSns0.nl2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

○NSns11.net2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

○NSns5.be2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

●MXalt1.aspmx.l.google.com2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

●MXalt2.aspmx.l.google.com2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

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

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

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

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

●MXaspmx.l.google.com2026-02-17 → 2026-08-02 · 3 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
● 2026-08-02 06:07:26

○MXfallbackmx.spamexperts.eu2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

○MXlastmx.spamexperts.net2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

○MXmx.spamexperts.com2015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

●A108.132.219.42026-08-02 → 2026-08-02 · 3 obs

○ 2026-02-17 08:11:16
● 2026-08-02 03:53:30
● 2026-08-02 06:07:26

○A149.210.160.1602015-08-17 → 2020-02-29 · 4 obs

● 2015-08-17 13:58:02
● 2020-02-29 17:16:44
○ 2026-02-17 08:11:16
○ 2026-08-02 06:07:26

●A34.249.196.1642026-08-02 → 2026-08-02 · 3 obs

○ 2026-02-17 08:11:16
● 2026-08-02 03:53:30
● 2026-08-02 06:07:26

○A52.17.250.32026-02-17 → 2026-02-17 · 4 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
○ 2026-08-02 03:53:30
○ 2026-08-02 06:07:26

○A52.211.75.1812026-02-17 → 2026-02-17 · 4 obs

○ 2020-02-29 17:16:44
● 2026-02-17 08:11:16
○ 2026-08-02 03:53:30
○ 2026-08-02 06:07:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
leadelephant.com	ns-642.awsdns-16.net, ns-327.awsdns-40.com, ns-1106.awsdns-10.org, ns-2030.awsdns-61.co.uk	2 records

✅ Authoritative Response

Server:205.251.194.130

NS records: ns-642.awsdns-16.net, ns-327.awsdns-40.com, ns-1106.awsdns-10.org, ns-2030.awsdns-61.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadelephant.com (unsigned zone)

⏱️ Timing

Total: 331ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`108.132.219.4, 34.249.196.164`
NS	4	`ns-1106.awsdns-10.org, ns-2030.awsdns-61.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=jigg2XHcO0LgOif, v=spf1 a mx include:spf.autopilothq.com`
SOA	1	`ns-1106.awsdns-10.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-327.awsdns-40.com, ns-327.awsdns-40.com)

Analysis

Hierarchy

tracker.leadelephant.com and www.leadelephant.com each fall under leadelephant.com as their parent domain.

IP Addresses

leadelephant.com has two IP addresses: 34.249.196.164 and 108.132.219.4

Among others, leadinfo.org, leadinfo.be, leadinfo.ru and leadinfo.de resolve to the same IP numbers as leadelephant.com.

Name Servers

The NS records for leadelephant.com point to four name servers: ns-327.awsdns-40.com, ns-642.awsdns-16.net, ns-1106.awsdns-10.org and ns-2030.awsdns-61.co.uk.

At least some of leadelephant.com's name servers are shared with other domains, for example acquizition.biz, fan.me, bigfoot-studio.link and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-327.awsdns-40.com directs to 205.251.193.71 and 2600:9000:5301:4700::1; ns-642.awsdns-16.net directs to 205.251.194.130 and 2600:9000:5302:8200::1; ns-1106.awsdns-10.org directs to 205.251.196.82 and 2600:9000:5304:5200::1; ns-2030.awsdns-61.co.uk directs to 205.251.199.238 and 2600:9000:5307:ee00::1.

Mail Servers

Five mail servers handle leadelephant.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between leadelephant.com and other domains, including jecweb.co.jp, ns500754.ns500742.ns500742.ns500742.ns500754.ns500731.ns500688.ns500671.ns500704.ns500705.ns500688.ns500291.ns500291.ns500153.tenderladiesbz.com, ns500734.ns500693.ns500734.ns500734.ns500693.ns500699.ns500693.ns500699.ns500588.ns500588.ns500683.ns500588.ns500588.ns500683.ns500110.dtrkdll.com and two others.

alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c2d::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

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

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

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