leadgem.co - dns.ninja

`leadgem.co`

DNSSEC	⚠️ Not signed
NS	`ns-1255.awsdns-28.org` ⭐
		A	2600:9000:5304:e700::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1255.awsdns-28.org`
		A	205.251.196.231^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1255.awsdns-28.org`
NS	`ns-1588.awsdns-06.co.uk`
		A	2600:9000:5306:3400::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1588.awsdns-06.co.uk`
		A	205.251.198.52^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1588.awsdns-06.co.uk`
NS	`ns-35.awsdns-04.com`
		A	2600:9000:5300:2300::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-35.awsdns-04.com`
		A	205.251.192.35^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-35.awsdns-04.com`
NS	`ns-853.awsdns-42.net`
		A	2600:9000:5303:5500::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-853.awsdns-42.net`
		A	205.251.195.85^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-853.awsdns-42.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c21::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f26.1e100.net`
		A	2607:f8b0:4004:c21::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pe-in-f27.1e100.net`
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-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`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
		A	192.178.218.26^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f26.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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
MX	`mxa.mailgun.org`⁽¹⁰⁾
		A	34.149.254.5^{🇺🇸 Google34.148.0.0/14}
			PTR	`5.254.149.34.bc.googleusercontent.com`
MX	`mxb.mailgun.org`⁽¹⁰⁾
		A	34.36.182.139^{🇺🇸 Google34.32.0.0/11}
			PTR	`139.182.36.34.bc.googleusercontent.com`
SOA	`ns-1255.awsdns-28.org`awsdns-hostmaster@amazon.com serial=1

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759714929

Same first word

leadgem.co

leadgem.com

leadgem.net

Similar names

algdeem.com

gemdeal.com

megadle.ru

gelamed.com

megaled.com

ledmega.com

megaled.pl

madglee.com

edelmag.cl

megadel.es

amledge.com

dalemeg.com

megaled.net

megaled.com.cn

edelmag.com

megaled.cn

megaled.ca

megadel.org

medlega.com

megadel.com

ledgame.com

gelamed.de

magedel.ru

madeleg.com

eagledm.com

gameled.com

gemdale.com

gamedle.wtf

gemdale.net

gelamed.ru

ledemag.ro

medegal.com

delmage.com

megaled.ru

delagem.com

galemed.com

gamedel.com

gemdale.eu

gleamed.com.de

megaled.fr

gemedal.com

edelmag.net

deeglam.com

galemed.com.tw

adlegem.de

eaglemd.com

megaled.de

megaled.nl

DNS History

19 records (12 active, 7 former)

○NSns-1163.awsdns-17.org2020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

●NSns-1255.awsdns-28.org2026-03-04 → 2026-07-24 · 3 obs

○ 2020-01-03 12:38:10
● 2026-03-04 13:05:54
● 2026-07-24 11:41:24

●NSns-1588.awsdns-06.co.uk2026-03-04 → 2026-07-24 · 3 obs

○ 2020-01-03 12:38:10
● 2026-03-04 13:05:54
● 2026-07-24 11:41:24

○NSns-2025.awsdns-61.co.uk2020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

●NSns-35.awsdns-04.com2026-03-04 → 2026-07-24 · 3 obs

○ 2020-01-03 12:38:10
● 2026-03-04 13:05:54
● 2026-07-24 11:41:24

○NSns-57.awsdns-07.com2020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

○NSns-850.awsdns-42.net2020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

●NSns-853.awsdns-42.net2026-03-04 → 2026-07-24 · 3 obs

○ 2020-01-03 12:38:10
● 2026-03-04 13:05:54
● 2026-07-24 11:41:24

●MXalt1.aspmx.l.google.com2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXalt2.aspmx.l.google.com2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXalt3.aspmx.l.google.com2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXalt4.aspmx.l.google.com2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXaspmx.l.google.com2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXmxa.mailgun.org2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXmxb.mailgun.org2020-01-03 → 2026-07-24 · 2 obs

● 2020-01-03 12:38:10
● 2026-07-24 11:41:24

●MXsmtp.google.com2026-03-04 → 2026-07-24 · 3 obs

○ 2020-01-03 12:38:10
● 2026-03-04 13:05:54
● 2026-07-24 11:41:24

○A18.188.71.1002020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

○A3.130.179.592020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

○A3.14.202.822020-01-03 → 2020-01-03 · 3 obs

● 2020-01-03 12:38:10
○ 2026-03-04 13:05:54
○ 2026-07-24 11:41:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	-
leadgem.co	ns-35.awsdns-04.com, ns-853.awsdns-42.net, ns-1255.awsdns-28.org, ns-1588.awsdns-06.co.uk	-

✅ Authoritative Response

Server:205.251.195.85

NS records: ns-35.awsdns-04.com, ns-853.awsdns-42.net, ns-1255.awsdns-28.org, ns-1588.awsdns-06.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadgem.co (unsigned zone)

⏱️ Timing

Total: 590ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1255.awsdns-28.org, ns-1588.awsdns-06.co.uk...`
MX	8	`aspmx.l.google.com (pri: 1), smtp.google.com (pri: 1)...`
SOA	1	`ns-1255.awsdns-28.org awsdns-hostmaster.`

Analysis

Name Servers

leadgem.co has four authoritative name servers: ns-35.awsdns-04.com, ns-853.awsdns-42.net, ns-1255.awsdns-28.org and ns-1588.awsdns-06.co.uk.

leadgem.co has at least partial name server overlap with other domains, such as threerings.org.uk, f-log-assistant.grammarly.io, c.cdpprdus.thenorthface.com and two others.

ns-35.awsdns-04.com, ns-853.awsdns-42.net, ns-1255.awsdns-28.org and ns-1588.awsdns-06.co.uk all point to exactly two IP numbers each: ns-35.awsdns-04.com → 205.251.192.35 and 2600:9000:5300:2300::1; ns-853.awsdns-42.net → 205.251.195.85 and 2600:9000:5303:5500::1; ns-1255.awsdns-28.org → 205.251.196.231 and 2600:9000:5304:e700::1; ns-1588.awsdns-06.co.uk → 205.251.198.52 and 2600:9000:5306:3400::1.

Mail Servers

Mail for leadgem.co is routed through 8 mail servers, including smtp.google.com, mxa.mailgun.org, mxb.mailgun.org and 5 other.

leadgem.co shares mail servers — at least in part — with other domains, including ns500699.ns500734.ns500734.ns500693.ns500693.ns500734.ns500693.ns500693.ns500683.ns500693.ns500683.ns500112.dtrkdll.com, ns500671.ns500742.ns500754.ns500731.ns500731.ns500742.ns500688.ns500678.ns500291.ns500666.ns500291.ns500291.ns500131.lustychickser.com, ns500671.ns500742.ns500754.ns500742.ns500754.ns500731.ns500731.ns500688.ns500671.ns500678.ns500671.ns500131.lustychickser.com and two others.

These mail servers are frequently used alongside mail servers aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and 4 other.

Host names with 9 IP numbers:

smtp.google.com resolves to 64.233.180.26, 64.233.180.27, 173.194.45.26 and 6 other IP addresses.

Host names with two IP numbers:

aspmx.l.google.com points to 142.250.31.27 and 2607:f8b0:4004:c09::1a.

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

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

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

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

Host names pointing to a single IP address:

mxa.mailgun.org points to 34.149.254.5.

mxb.mailgun.org points to 34.36.182.139.