leaduser.net - dns.ninja

`leaduser.net`

DNSSEC	⚠️ Not signed
A	62.149.128.151^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
		PTR	`mxd6.aruba.it`
A	62.149.128.154^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
A	62.149.128.157^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
A	62.149.128.160^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
A	62.149.128.163^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
A	62.149.128.166^{🇮🇹 ARUBA-ASN62.149.128.0/19 Aruba S.p.A. Network}
NS	`dns2.technorail.com` ⭐
		A	2a00:6d42:3:2096::f:1^{🇮🇹 ARUBA-ASN2a00:6d42::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns2.technorail.com`
		A	95.110.136.8^{🇮🇹 ARUBA-ASN95.110.136.0/21 Aruba S.p.A. Network}
			PTR	`dns2.technorail.com`
NS	`dns.technorail.com`
		A	2a00:6d40:2:2082::f:1^{🇮🇹 ARUBA-ASN2a00:6d40::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns.technorail.com`
		A	94.177.210.13^{🇮🇹 ARUBA-ASN94.177.208.0/22 Aruba S.p.A. Network}
			PTR	`dns.technorail.com`
NS	`dns3.arubadns.net`
		A	2a00:6d41:3:206e::f:1^{🇮🇹 ARUBA-ASN2a00:6d41::/32 Aruba S.p.A. IPv6 Network}
			PTR	`dns3.arubadns.net`
		A	95.110.220.5^{🇮🇹 ARUBA-ASN95.110.192.0/18 Aruba S.p.A. Network}
			PTR	`dns3.arubadns.net`
NS	`dns4.arubadns.cz`
		A	2001:15e8:104:4::d8ee^{🇨🇿 INTERNET-CZ2001:15e8::/32}
			PTR	`dns4.arubadns.cz`
		A	81.2.216.238^{🇨🇿 INTERNET-CZ81.2.192.0/18 INTERNET CZ, a.s.}
			PTR	`dns4.arubadns.cz`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c2d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ry-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-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::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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=RzJ8rUgTBTvUb6Cu_ZA--d1c4hCmWn2pBB2Dm5rlcE0`
SOA	`dns.technorail.com`hostmaster@leaduser.net serial=1

`net`

	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=1785282917

Same first word

leaduser.net

leaduser.it

Similar names

DNS History

18 records (15 active, 3 former)

●NSdns.technorail.com2016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●NSdns2.technorail.com2016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●NSdns3.arubadns.net2016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●NSdns4.arubadns.cz2016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

○NSns1.world4you.at2007-10-15 → 2007-10-15 · 3 obs

● 2007-10-15 06:45:28
○ 2015-10-10 12:35:30
○ 2026-07-28 23:55:40

○NSns2.world4you.at2007-10-15 → 2007-10-15 · 3 obs

● 2007-10-15 06:45:28
○ 2015-10-10 12:35:30
○ 2026-07-28 23:55:40

●MXalt1.aspmx.l.google.com2016-04-01 → 2026-07-28 · 2 obs

● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●MXalt2.aspmx.l.google.com2016-04-01 → 2026-07-28 · 2 obs

● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●MXalt3.aspmx.l.google.com2016-04-01 → 2026-07-28 · 2 obs

● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●MXalt4.aspmx.l.google.com2016-04-01 → 2026-07-28 · 2 obs

● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●MXaspmx.l.google.com2016-04-01 → 2026-07-28 · 2 obs

● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1512016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1542016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1572016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1602016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1632016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

●A62.149.128.1662016-04-01 → 2026-07-28 · 3 obs

○ 2015-10-10 12:35:30
● 2016-04-01 11:22:52
● 2026-07-28 23:55:40

○A80.243.163.402007-10-15 → 2007-10-15 · 3 obs

● 2007-10-15 06:45:28
○ 2015-10-10 12:35:30
○ 2026-07-28 23:55:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	h.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net...	-
leaduser.net	dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, dns3.arubadns.net	2 records

✅ Authoritative Response

Server:81.2.216.238

NS records: dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz, dns3.arubadns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leaduser.net (unsigned zone)

⏱️ Timing

Total: 627ms | Queries: -

📄 Records

Type	Count	Sample Data
A	6	`62.149.128.163, 62.149.128.151...`
NS	4	`dns.technorail.com, dns4.arubadns.cz...`
MX	5	`alt2.aspmx.l.google.com (pri: 20), alt1.aspmx.l.google.com (pri: 20)...`
TXT	1	`google-site-verification=RzJ8rUgTBTvUb6C`
SOA	1	`dns.technorail.com hostmaster.leaduser.n`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns3.arubadns.net, dns3.arubadns.net)

Analysis

IP Addresses

leaduser.net has 6 IP addresses — 62.149.128.151, 62.149.128.154, 62.149.128.157 and 3 more.

mx.ruplan.it, mx.sweethomepiramide.com, carlan.it and two other host names share IP numbers with leaduser.net.

Name Servers

The authoritative name servers for leaduser.net are dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz and dns3.arubadns.net.

leaduser.net has at least partial name server overlap with other domains, such as emanuelasasso.it, desguacemalvarrosa.es, sepran.com and two others.

dns2.technorail.com, dns.technorail.com, dns4.arubadns.cz and dns3.arubadns.net all point to exactly two IP numbers each: dns2.technorail.com → 95.110.136.8 and 2a00:6d42:3:2096::f:1; dns.technorail.com → 94.177.210.13 and 2a00:6d40:2:2082::f:1; dns4.arubadns.cz → 81.2.216.238 and 2001:15e8:104:4::d8ee; dns3.arubadns.net → 95.110.220.5 and 2a00:6d41:3:206e::f:1.

Mail Servers

Mail for leaduser.net is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

leaduser.net has at least partial mail server overlap with other domains such as blastacars.co.nz, ns500698.ns500758.ns500759.ns500758.ns500736.ns500735.ns500735.ns500698.ns500736.ns500735.ns500576.ns500708.ns500576.ns500576.ns500576.ns500619.ns500619.trackreceptor.com, alebianco.dev and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to 142.251.179.26 and 2607:f8b0:4004:c2d::1b.

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

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

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

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