lead.watch - robtex.com

lead.watch

DNSSEC⚠️ Not signed
A216.150.1.1πŸ‡¨πŸ‡¦ Amazon216.150.1.0/24 EC2 Prefix
NSns1.dns-parking.com ⭐
A2400:cb00:2049:1::a29f:18c9πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.24.201Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.dns-parking.com
NSns2.dns-parking.com
A2400:cb00:2049:1::a29f:192aπŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.25.42Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.dns-parking.com
MXmx1.hostinger.com ⭐
A2606:4700:90:0:c1f8:f874:2386:b61fπŸ‡ΊπŸ‡Έ Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US
A172.65.182.103πŸ‡ΊπŸ‡Έ Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
MXmx2.hostinger.com(10)
A2606:4700:90:0:c1f8:f874:2386:b61fπŸ‡ΊπŸ‡Έ Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US
A172.65.182.103πŸ‡ΊπŸ‡Έ Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
TXTv=spf1 include:_spf.mail.hostinger.com ~all
SOAns1.dns-parking.comdns@hostinger.com 2026-07-09 #1

watch

DNSSECπŸ”’ Signed (DS record present)
NSv0n0.nic.watch ⭐
NSv0n1.nic.watch
NSv0n2.nic.watch
NSv0n3.nic.watch
NSv2n0.nic.watch
NSv2n1.nic.watch
SOAv0n0.nic.watchhostmaster@donuts.email serial=1784041261

Same first word

Similar names

DNS History

15 records (5 active, 10 former)

2017201820192020202120222023202420252026NSns1.dns-parking.comns2.dns-parking.comns-1165.awsdns-17.orgns-1813.awsdns-34.co.ukns-439.awsdns-54.comns-632.awsdns-15.netMXmx1.hostinger.commx2.hostinger.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA216.150.1.152.17.181.44
β—‹NSns-1165.awsdns-17.org2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹NSns-1813.awsdns-34.co.uk2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹NSns-439.awsdns-54.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹NSns-632.awsdns-15.net2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
●NSns1.dns-parking.com2026-04-05 β†’ 2026-07-14 Β· 3 obs
β—‹ 2026-02-20 23:59:02
● 2026-04-05 22:11:24
● 2026-07-14 15:17:20
●NSns2.dns-parking.com2026-04-05 β†’ 2026-07-14 Β· 3 obs
β—‹ 2026-02-20 23:59:02
● 2026-04-05 22:11:24
● 2026-07-14 15:17:20
β—‹MXalt1.aspmx.l.google.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹MXalt2.aspmx.l.google.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹MXaspmx.l.google.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹MXaspmx2.googlemail.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
β—‹MXaspmx3.googlemail.com2016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20
●MXmx1.hostinger.com2026-04-05 β†’ 2026-07-14 Β· 3 obs
β—‹ 2026-02-20 23:59:02
● 2026-04-05 22:11:24
● 2026-07-14 15:17:20
●MXmx2.hostinger.com2026-04-05 β†’ 2026-07-14 Β· 3 obs
β—‹ 2026-02-20 23:59:02
● 2026-04-05 22:11:24
● 2026-07-14 15:17:20
●A216.150.1.12026-04-05 β†’ 2026-07-14 Β· 3 obs
β—‹ 2026-02-20 23:59:02
● 2026-04-05 22:11:24
● 2026-07-14 15:17:20
β—‹A52.17.181.442016-12-11 β†’ 2017-05-02 Β· 4 obs
● 2016-12-11 00:12:14
● 2017-05-02 23:37:24
β—‹ 2026-02-20 23:59:02
β—‹ 2026-07-14 15:17:20

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
watchv2n0.nic.watch, v2n1.nic.watch, v0n0.nic.watch, v0n2.nic.watch...12 records
lead.watchns1.dns-parking.com, ns2.dns-parking.com-

βœ… Authoritative Response

Server:162.159.25.42

NS records: ns1.dns-parking.com, ns2.dns-parking.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lead.watch (unsigned zone)

⏱️ Timing

Total: 2143ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1216.150.1.1
NS2ns1.dns-parking.com, ns2.dns-parking.com
MX2mx2.hostinger.com (pri: 10), mx1.hostinger.com (pri: 5)
TXT1v=spf1 include:_spf.mail.hostinger.com ~
SOA1ns1.dns-parking.com dns.hostinger.com

πŸ“Œ Glue Records Collected

Total: 12

In-bailiwick: 12 (v2n1.nic.watch, v2n0.nic.watch, v0n3.nic.watch...)

Analysis

IP Addresses

lead.watch directs to one IP number, which is 216.150.1.1.

Among the host names that share IP numbers with lead.watch are seekho.in, expdr.com, xgoat.io and two others.

Name Servers

lead.watch has two authoritative name servers β€” ns1.dns-parking.com and ns2.dns-parking.com.

lead.watch has the same name server delegation as a number of other domains, such as american-international-group.com, soscortinas.com.br, aminallcny.com and two more.

The name servers for lead.watch overlap at least partially with those of other domains β€” for example gurukrupacoolcare.com.

Both ns1.dns-parking.com and ns2.dns-parking.com have two IP addresses each. ns1.dns-parking.com resolves to 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9; ns2.dns-parking.com resolves to 162.159.25.42 and 2400:cb00:2049:1::a29f:192a.

Mail Servers

The MX records for lead.watch point to two mail servers: mx1.hostinger.com and mx2.hostinger.com.

lead.watch has the same mail server arrangement as a number of other domains, for example discografiascompletasfull.com, hospitaldeilheus.com.br, garjoo.com and two more.

lead.watch shares at least some of its mail servers with other domains, such as unifiedmentor.com.

Both mx1.hostinger.com and mx2.hostinger.com point to 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f.

The host names mx1.hostinger.com and mx2.hostinger.com both resolve to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

The host names mx1.hostinger.com and mx2.hostinger.com both resolve to 172.65.182.103 IP addresses.