leadmark.com.br - dns.ninja

`leadmark.com.br`

DNSSEC	⚠️ Not signed
A	54.158.166.134^{🇺🇸 Amazon54.156.0.0/14 EC2 IAD prefix}
		PTR	`ec2-54-158-166-134.compute-1.amazonaws.com`
NS	`ns-1971.awsdns-54.co.uk` ⭐
		A	2600:9000:5307:b300::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1971.awsdns-54.co.uk`
		A	205.251.199.179^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1971.awsdns-54.co.uk`
NS	`ns-1103.awsdns-09.org`
		A	2600:9000:5304:4f00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1103.awsdns-09.org`
		A	205.251.196.79^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1103.awsdns-09.org`
NS	`ns-251.awsdns-31.com`
		A	2600:9000:5300:fb00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-251.awsdns-31.com`
		A	205.251.192.251^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-251.awsdns-31.com`
NS	`ns-694.awsdns-22.net`
		A	2600:9000:5302:b600::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-694.awsdns-22.net`
		A	205.251.194.182^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-694.awsdns-22.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
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}
			PTR	`lcscld-in-f26.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::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`
TXT	`google-site-verification=rooY5hE9iy_ci92XaQVkibS6Fxi9U60dUj7Jr5eOetk`
SOA	`ns-1971.awsdns-54.co.uk`awsdns-hostmaster@amazon.com serial=1

`com.br`

	DNSSEC	⚠️ Not signed
	NS	`a.dns.br` ⭐ ⚠️ Not in parent delegation
	NS	`b.dns.br` ⚠️ Not in parent delegation
	NS	`c.dns.br` ⚠️ Not in parent delegation
	NS	`d.dns.br` ⚠️ Not in parent delegation
	NS	`e.dns.br` ⚠️ Not in parent delegation
	NS	`f.dns.br` ⚠️ Not in parent delegation
	SOA	`a.dns.br`hostmaster@registro.br serial=2026165326

rank #515882 globally
rank #3866 in the tld
WOT: SAFE (69/100)

Subdomains

ns2.leadmark.com.br

lmcpanelsrv.leadmark.com.br

ns1.leadmark.com.br

Same first word

leadmark.tech

leadmark.gr

leadmark.net

leadmark.com.br

leadmark.com

Similar names

DNS History

15 records (10 active, 5 former)

○NSlm1.tvihostdns.com2016-01-19 → 2016-09-25 · 4 obs

● 2016-01-19 21:00:18
● 2016-09-25 01:09:40
○ 2017-04-20 04:53:14
○ 2026-06-14 14:19:30

○NSlm2.tvihostdns.com2016-01-19 → 2016-09-25 · 4 obs

● 2016-01-19 21:00:18
● 2016-09-25 01:09:40
○ 2017-04-20 04:53:14
○ 2026-06-14 14:19:30

●NSns-1103.awsdns-09.org2017-04-20 → 2026-06-14 · 3 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
● 2026-06-14 14:19:30

●NSns-1971.awsdns-54.co.uk2017-04-20 → 2026-06-14 · 3 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
● 2026-06-14 14:19:30

●NSns-251.awsdns-31.com2017-04-20 → 2026-06-14 · 3 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
● 2026-06-14 14:19:30

●NSns-694.awsdns-22.net2017-04-20 → 2026-06-14 · 3 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
● 2026-06-14 14:19:30

●MXalt1.aspmx.l.google.com2016-01-19 → 2026-06-14 · 2 obs

● 2016-01-19 21:00:18
● 2026-06-14 14:19:30

●MXalt2.aspmx.l.google.com2016-01-19 → 2026-06-14 · 2 obs

● 2016-01-19 21:00:18
● 2026-06-14 14:19:30

●MXalt3.aspmx.l.google.com2016-01-19 → 2026-06-14 · 2 obs

● 2016-01-19 21:00:18
● 2026-06-14 14:19:30

●MXalt4.aspmx.l.google.com2016-01-19 → 2026-06-14 · 2 obs

● 2016-01-19 21:00:18
● 2026-06-14 14:19:30

●MXaspmx.l.google.com2016-01-19 → 2026-06-14 · 2 obs

● 2016-01-19 21:00:18
● 2026-06-14 14:19:30

○A142.4.24.1552016-01-19 → 2016-09-25 · 4 obs

● 2016-01-19 21:00:18
● 2016-09-25 01:09:40
○ 2017-04-20 04:53:14
○ 2026-06-14 14:19:30

○A52.206.158.1342017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
○ 2026-02-23 19:50:06
○ 2026-06-14 14:19:30

○A52.7.23.2382017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-25 01:09:40
● 2017-04-20 04:53:14
○ 2026-02-23 19:50:06
○ 2026-06-14 14:19:30

●A54.158.166.1342026-02-23 → 2026-06-14 · 3 obs

○ 2017-04-20 04:53:14
● 2026-02-23 19:50:06
● 2026-06-14 14:19:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
br	e.dns.br, c.dns.br, b.dns.br, a.dns.br...	-
leadmark.com.br	ns-694.awsdns-22.net, ns-251.awsdns-31.com, ns-1971.awsdns-54.co.uk, ns-1103.awsdns-09.org	-

✅ Authoritative Response

Server:205.251.192.251

NS records: ns-694.awsdns-22.net, ns-251.awsdns-31.com, ns-1971.awsdns-54.co.uk, ns-1103.awsdns-09.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadmark.com.br (unsigned zone)

⏱️ Timing

Total: 1007ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.158.166.134`
NS	4	`ns-1103.awsdns-09.org, ns-1971.awsdns-54.co.uk...`
MX	5	`aspmx.l.google.com (pri: 0), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`google-site-verification=rooY5hE9iy_ci92`
SOA	1	`ns-1971.awsdns-54.co.uk awsdns-hostmaste`

Analysis

Hierarchy

leadmark.com.br sits above ns2.leadmark.com.br, lmcpanelsrv.leadmark.com.br and ns1.leadmark.com.br in the domain hierarchy.

IP Addresses

leadmark.com.br points to a single IP number: 54.158.166.134.

Host names like ec2-54-158-166-134.compute-1.amazonaws.com are further examples that share IP numbers with leadmark.com.br.

Name Servers

leadmark.com.br has four authoritative name servers: ns-251.awsdns-31.com, ns-694.awsdns-22.net, ns-1103.awsdns-09.org and ns-1971.awsdns-54.co.uk.

There is at least partial name server overlap between leadmark.com.br and other domains — laronline.com.ar, veridium-dev.com, evidos.nl and two more among them.

All four hostnames — ns-251.awsdns-31.com, ns-694.awsdns-22.net, ns-1103.awsdns-09.org and ns-1971.awsdns-54.co.uk — resolve to two IP numbers apiece: ns-251.awsdns-31.com to 205.251.192.251 and 2600:9000:5300:fb00::1; ns-694.awsdns-22.net to 205.251.194.182 and 2600:9000:5302:b600::1; ns-1103.awsdns-09.org to 205.251.196.79 and 2600:9000:5304:4f00::1; ns-1971.awsdns-54.co.uk to 205.251.199.179 and 2600:9000:5307:b300::1.

Mail Servers

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

leadmark.com.br shares mail servers — at least in part — with other domains, including ns500759.ns500759.ns500735.ns500698.ns500735.ns500698.ns500735.ns500698.ns500698.ns500708.ns500576.ns500619.tracksymphony.com, capitalempire.net, ns500758.ns500698.ns500759.ns500758.ns500758.ns500759.ns500736.ns500735.ns500736.ns500735.ns500735.ns500735.ns500698.ns500708.ns500576.ns500686.ns500619.trackreceptor.com and two others.

These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com resolves to two addresses: 192.178.155.27 and 2607:f8b0:4004:c1d::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::1a.

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