leadforce.ru - dns.ninja

leadforce.ru

DNSSECโš ๏ธ Not signed
A185.26.122.9
NSns3.hostland.ru โญ
A81.95.18.218๐Ÿ‡ท๐Ÿ‡บ MTTELECOM-AS81.95.16.0/20 MTTELECOM-NETWORK
A185.22.183.98๐Ÿ‡ท๐Ÿ‡บ RETNRU-SPB-AS185.22.180.0/22 CJSC "RetnNet"
NSns.hostland.ru
A185.26.122.3๐Ÿ‡ท๐Ÿ‡บ HOSTLAND185.26.122.0/24
PTRserv3-26.hostland.ru
A185.26.123.231๐Ÿ‡ท๐Ÿ‡บ HOSTLAND185.26.123.0/24
PTRsmtp1.hostland.ru
MXmx.yandex.net โญ
TXTv=spf1 redirect=_spf.yandex.net
SOAns.hostland.rusupport@hostland.ru serial=100000000

ru

DNSSEC๐Ÿ”’ Signed (DS record present)
NSa.dns.ripn.net โญ
NSb.dns.ripn.net
NSd.dns.ripn.net
NSe.dns.ripn.net
NSf.dns.ripn.net
SOAa.dns.ripn.nethostmaster@ripn.net serial=4069270

Same first word

Similar names

DNS History

13 records (4 active, 9 former)

20162017201820192020202120222023202420252026NSns.hostland.runs3.hostland.runs1.peterhost.runs2.peterhost.ruMXmx.yandex.netalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA185.26.122.980.93.54.10980.93.54.112
โ—NSns.hostland.ru2026-03-24 โ†’ 2026-06-16 ยท 3 obs
โ—‹ 2017-04-09 16:24:18
โ— 2026-03-24 11:00:44
โ— 2026-06-16 01:40:10
โ—‹NSns1.peterhost.ru2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹NSns2.peterhost.ru2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—NSns3.hostland.ru2026-03-24 โ†’ 2026-06-16 ยท 3 obs
โ—‹ 2017-04-09 16:24:18
โ— 2026-03-24 11:00:44
โ— 2026-06-16 01:40:10
โ—‹MXalt1.aspmx.l.google.com2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹MXalt2.aspmx.l.google.com2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹MXaspmx.l.google.com2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹MXaspmx2.googlemail.com2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹MXaspmx3.googlemail.com2015-05-28 โ†’ 2017-04-09 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—MXmx.yandex.net2026-03-24 โ†’ 2026-06-16 ยท 3 obs
โ—‹ 2017-04-09 16:24:18
โ— 2026-03-24 11:00:44
โ— 2026-06-16 01:40:10
โ—A185.26.122.92026-03-24 โ†’ 2026-06-16 ยท 3 obs
โ—‹ 2017-04-09 16:24:18
โ— 2026-03-24 11:00:44
โ— 2026-06-16 01:40:10
โ—‹A80.93.54.1092016-03-28 โ†’ 2017-04-09 ยท 5 obs
โ—‹ 2015-12-21 16:59:26
โ— 2016-03-28 19:17:02
โ— 2017-04-09 16:24:18
โ—‹ 2026-03-24 11:00:44
โ—‹ 2026-06-16 01:40:10
โ—‹A80.93.54.1122015-05-28 โ†’ 2015-12-21 ยท 4 obs
โ— 2015-05-28 10:42:04
โ— 2015-12-21 16:59:26
โ—‹ 2016-03-28 19:17:02
โ—‹ 2026-06-16 01:40:10

๐Ÿ” DNS Trace

๐Ÿ“‹ Delegation Chain

ZoneNameserversGlue
rua.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net...-
leadforce.runs.hostland.ru, ns3.hostland.ru4 records

โœ… Authoritative Response

Server:81.95.18.218

NS records: ns.hostland.ru, ns3.hostland.ru

๐Ÿ”’ DNSSEC Status

โš ๏ธ Insecure (no DNSSEC)

No DS record for leadforce.ru (unsigned zone)

โฑ๏ธ Timing

Total: 5195ms | Queries: -

๐Ÿ“„ Records

TypeCountSample Data
A1185.26.122.9
NS2ns.hostland.ru, ns3.hostland.ru
MX1mx.yandex.net (pri: 10)
TXT1v=spf1 redirect=_spf.yandex.net
SOA1ns.hostland.ru support.hostland.ru

๐Ÿ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns3.hostland.ru, ns3.hostland.ru, ns.hostland.ru...)

Analysis

IP Addresses

leadforce.ru directs to one IP number, which is 185.26.122.9.

Name Servers

Two name servers handle the delegation for leadforce.ru: ns3.hostland.ru and ns.hostland.ru.

ns3.hostland.ru and ns.hostland.ru both carry two IP addresses. The A records for ns3.hostland.ru are 81.95.18.218 and 185.22.183.98; the A records for ns.hostland.ru are 185.26.122.3 and 185.26.123.231.

Mail Servers

leadforce.ru routes its mail through a single mail server, mx.yandex.net.