leadercommand.com - dns.ninja

`leadercommand.com`

DNSSEC	⚠️ Not signed
A	195.161.41.33^{🇷🇺 RTCOMM-AS195.161.0.0/16 RTCOMM-RU}
NS	`ns1.jino.ru` ⭐
		A	217.107.34.200^{🇷🇺 RTCOMM-AS217.107.0.0/18 RTCOMM-RU}
			PTR	`ns1.jino.ru`
NS	`ns2.jino.ru`
		A	2001:1bb0:e000:1e::917^{🇷🇺 RTCOMM-AS2001:1bb0::/32 RTCOMM-RU}
			PTR	`ns2.jino.ru`
		A	195.161.62.86^{🇷🇺 RTCOMM-AS195.161.0.0/16 RTCOMM-RU}
			PTR	`ns2.jino.ru`
NS	`ns3.jino.ru` ⚠️ Not in parent delegation
		A	217.107.219.170^{🇷🇺 RTCOMM-AS217.107.208.0/20 RTCOMM-RU}
			PTR	`ns3.jino.ru`
NS	`ns4.jino.ru` ⚠️ Not in parent delegation
		A	2001:1bb0:e000:1e::1cd^{🇷🇺 RTCOMM-AS2001:1bb0::/32 RTCOMM-RU}
		A	81.177.139.205^{🇷🇺 RTCOMM-AS81.177.128.0/19 RTCOMM-RU}
			PTR	`ns4.jino.ru`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 include:_spf.yandex.net ~all`
SOA	`ns1.jino.ru`hostmaster@jino@ru 2019-01-23 #5

`com`

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

WOT: SAFE (65/100)

Same first word

leadercommand.ru

leadercommand.com

Similar names

leadcommander.com

DNS History

12 records (6 active, 6 former)

●NSns1.jino.ru2015-08-20 → 2026-07-24 · 2 obs

● 2015-08-20 10:30:50
● 2026-07-24 01:09:52

●NSns2.jino.ru2017-03-28 → 2026-07-24 · 3 obs

○ 2015-08-20 10:30:50
● 2017-03-28 18:40:04
● 2026-07-24 01:09:52

●NSns3.jino.ru2017-03-28 → 2026-07-24 · 6 obs

○ 2015-08-20 10:30:50
● 2017-03-28 18:40:04
● 2026-05-29 23:56:20
○ 2026-06-21 03:50:56
● 2026-07-15 05:29:18
● 2026-07-24 01:09:52

●NSns4.jino.ru2017-03-28 → 2026-07-24 · 6 obs

○ 2015-08-20 10:30:50
● 2017-03-28 18:40:04
● 2026-05-29 23:56:20
○ 2026-06-21 03:50:56
● 2026-07-15 05:29:18
● 2026-07-24 01:09:52

○MXmail.leadercommand.com2015-08-20 → 2017-03-28 · 4 obs

● 2015-08-20 10:30:50
● 2017-03-28 18:40:04
○ 2026-03-30 04:18:22
○ 2026-07-24 01:09:52

●MXmx.yandex.net2026-03-30 → 2026-07-24 · 6 obs

○ 2017-03-28 18:40:04
● 2026-03-30 04:18:22
● 2026-05-29 23:56:20
○ 2026-06-21 03:50:56
● 2026-07-15 05:29:18
● 2026-07-24 01:09:52

●A195.161.41.332026-07-15 → 2026-07-24 · 3 obs

○ 2026-06-21 03:50:56
● 2026-07-15 05:29:18
● 2026-07-24 01:09:52

○A195.161.62.1002026-03-30 → 2026-04-19 · 5 obs

○ 2017-03-28 18:40:04
● 2026-03-30 04:18:22
● 2026-04-19 20:56:34
○ 2026-05-29 23:56:20
○ 2026-07-24 01:09:52

○A217.107.219.192026-05-29 → 2026-05-29 · 4 obs

○ 2026-04-19 20:56:34
● 2026-05-29 23:56:20
○ 2026-06-21 03:50:56
○ 2026-07-24 01:09:52

○A81.177.165.2302017-03-28 → 2017-03-28 · 4 obs

○ 2016-07-18 09:36:10
● 2017-03-28 18:40:04
○ 2026-03-30 04:18:22
○ 2026-07-24 01:09:52

○A81.177.165.622015-08-20 → 2015-08-20 · 3 obs

● 2015-08-20 10:30:50
○ 2015-12-12 09:37:52
○ 2026-07-24 01:09:52

○A81.177.165.642015-12-12 → 2016-07-18 · 5 obs

○ 2015-08-20 10:30:50
● 2015-12-12 09:37:52
● 2016-07-18 09:36:10
○ 2017-03-28 18:40:04
○ 2026-07-24 01:09:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net...	-
leadercommand.com	ns1.jino.ru, ns2.jino.ru	-

✅ Authoritative Response

Server:195.161.62.86

NS records: ns1.jino.ru, ns2.jino.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadercommand.com (unsigned zone)

⏱️ Timing

Total: 922ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`195.161.41.33`
NS	4	`ns2.jino.ru, ns4.jino.ru...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 include:_spf.yandex.net ~all`
SOA	1	`ns1.jino.ru hostmaster@jino.ru`

Analysis

IP Addresses

leadercommand.com points to a single IP number: 195.161.41.33.

Additional host names — komfort-shop.ru, elmasta.ru, etiger.ru and two others — share IP numbers with leadercommand.com.

Name Servers

leadercommand.com has four authoritative name servers: ns1.jino.ru, ns2.jino.ru, ns3.jino.ru and ns4.jino.ru.

There is at least partial name server overlap between leadercommand.com and other domains — smartmed.clinic, fobesko.ru, nzi.ru and two more among them.

Host names with two IP numbers:

ns2.jino.ru resolves to two addresses: 195.161.62.86 and 2001:1bb0:e000:1e::917.

ns4.jino.ru resolves to two addresses: 81.177.139.205 and 2001:1bb0:e000:1e::1cd.

Host names pointing to a single IP address:

The hostname ns1.jino.ru resolves to 217.107.34.200.

The hostname ns3.jino.ru resolves to 217.107.219.170.

Mail Servers

leadercommand.com has one mail server: mx.yandex.net.

leadercommand.com shares the same mail server setup as other domains, including fethiyedays.com, mototech.ru, sarko.ch and two others.

mx.yandex.net carries two IP numbers: 77.88.21.249 and 2a02:6b8::311.