`leadads.in`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns05.domaincontrol.com` ⭐
		A	2603:5:2160::3^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns05.domaincontrol.com`
		A	97.74.102.3^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns05.domaincontrol.com`
NS	`ns06.domaincontrol.com`
		A	2603:5:2260::3^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns06.domaincontrol.com`
		A	173.201.70.3^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns06.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c0d::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dl-in-f27.1e100.net`
		A	74.125.137.27^{🇺🇸 Google74.125.137.0/24}
			PTR	`dy-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f27.1e100.net`
		A	192.178.128.26^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f27.1e100.net`
		A	192.178.213.26^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:4025:402::1a^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=i1-F2SsKkdyveGK3XPO7YPmMRRLlFcaVysNRAqcRXyc`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns05.domaincontrol.com`dns@jomax.net 2025-07-22 #3

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1774481759

Same first word

leadads.com

leadads.in

Similar names

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
leadads.in	ns05.domaincontrol.com, ns06.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.70.3

NS records: ns05.domaincontrol.com, ns06.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadads.in (unsigned zone)

⏱️ Timing

Total: 374ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns05.domaincontrol.com, ns06.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=i1-F2SsKkdyveGK, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns05.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

leadads.in resolves to two IP numbers: 3.33.251.168 and 15.197.225.128.

Other host names, for instance aveiroe-americas.com, commercialrealestatekeywest.com, butt(0x6675636b)(0x787878).com, sangalhos.mobi and johnscleanouts.com share IP numbers with leadads.in.

Name Servers

Two name servers ns05.domaincontrol.com and ns06.domaincontrol.com handle delegation for leadads.in.

leadads.in uses the same name server setup as other domains, for example nedsis.com, snipview.com, fotodia.de, sg305.com and william-taylor.com.