leadcontext.ru - robtex.com
leadcontext.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 194.58.96.112🇷🇺 AS-REGRU194.58.96.0/24 Reg.Ru | ||||||
| PTR | 194-58-96-112.cloudvps.regruhosting.ru | ||||||
| NS | ns1.nameself.com ⭐ | ||||||
| A | 2a00:15f8:c001:3::144🇷🇺 MASTERHOST-AS2a00:15f8::/32 .masterhost | ||||||
| A | 87.242.73.100🇷🇺 MASTERHOST-AS87.242.73.0/24 | ||||||
| A | 88.212.207.45🇷🇺 UNITEDNET88.212.206.0/23 EXEPTO SERVERS PLANT | ||||||
| PTR | 45-207-212-88.host.exepto.ru | ||||||
| NS | ns2.nameself.com | ||||||
| A | 2a02:2100:e001:4::203🇷🇺 UNITEDNET2a02:2100::/32 United Network LLC | ||||||
| A | 88.212.208.183🇷🇺 UNITEDNET88.212.208.0/22 EXEPTO SERVERS PLANT | ||||||
| PTR | 183-208-212-88.host.exepto.ru | ||||||
| A | 95.213.146.179🇷🇺 SELECTEL95.213.146.0/24 -NET | ||||||
| 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 | yandex-verification: 7de88d8069f3fe04 | ||||||
| SOA | ns1.nameself.comsupport@regtime.net serial=1773936004 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4068500 | ||||||
Same first word
leadcontext.ru |
DNS History
11 records (4 active, 7 former)
○NSns1.expired.reg.ru2015-10-20 → 2015-10-20 · 4 obs
● 2015-10-20 23:21:38
○ 2015-12-24 07:52:22
○ 2026-04-13 14:16:30
●NSns1.nameself.com2026-03-04 → 2026-04-13 · 3 obs
● 2026-03-04 02:56:38
● 2026-04-13 14:16:30
○NSns1.reg.ru2015-05-24 → 2015-05-24 · 3 obs
○ 2015-10-20 23:21:38
○ 2026-04-13 14:16:30
○NSns2.expired.reg.ru2015-10-20 → 2015-10-20 · 4 obs
● 2015-10-20 23:21:38
○ 2015-12-24 07:52:22
○ 2026-04-13 14:16:30
●NSns2.nameself.com2026-03-04 → 2026-04-13 · 3 obs
● 2026-03-04 02:56:38
● 2026-04-13 14:16:30
○NSns2.reg.ru2015-05-24 → 2015-05-24 · 3 obs
○ 2015-10-20 23:21:38
○ 2026-04-13 14:16:30
●MXmx.yandex.net2026-03-04 → 2026-04-13 · 3 obs
● 2026-03-04 02:56:38
● 2026-04-13 14:16:30
○MXmx.yandex.ru2015-05-24 → 2015-05-24 · 3 obs
○ 2015-10-20 23:21:38
○ 2026-04-13 14:16:30
●A194.58.96.1122026-03-04 → 2026-04-13 · 3 obs
● 2026-03-04 02:56:38
● 2026-04-13 14:16:30
○A31.31.204.362015-10-20 → 2015-10-20 · 4 obs
● 2015-10-20 23:21:38
○ 2015-12-24 07:52:22
○ 2026-04-13 14:16:30
○A83.246.147.502015-05-24 → 2015-05-24 · 3 obs
○ 2015-10-20 23:21:38
○ 2026-04-13 14:16:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| leadcontext.ru | ns1.nameself.com, ns2.nameself.com | - |
✅ Authoritative Response
Server:95.213.146.179
NS records: ns1.nameself.com, ns2.nameself.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadcontext.ru (unsigned zone)
⏱️ Timing
Total: 1187ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 194.58.96.112 |
| NS | 2 | ns2.nameself.com, ns1.nameself.com |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | yandex-verification: 7de88d8069f3fe04 |
| SOA | 1 | ns1.nameself.com support.regtime.net |
Analysis
IP Addresses
leadcontext.ru resolves to one IP number: 194.58.96.112.
Other host names, for instance 194-58-96-112.cloudvps.regruhosting.ru, share IP numbers with leadcontext.ru.
Name Servers
leadcontext.ru is delegated to two name servers ns1.nameself.com and ns2.nameself.com.
leadcontext.ru shares the same name server setup as other domains, for instance koyuma.ru, flatshomes.ru, neonavigation.com, 1ckazan.ru and fi-ot.ru.
leadcontext.ru at least partially shares name servers with other domains, for instance infosmska.ru.
Host names with three IPs:
ns1.nameself.com points to 2a00:15f8:c001:3::144, 87.242.73.100 and 88.212.207.45.
ns2.nameself.com points to 2a02:2100:e001:4::203, 88.212.208.183 and 95.213.146.179.
Mail Servers
leadcontext.ru is handled by a single mail server, mx.yandex.net.
leadcontext.ru shares the same mail server setup as other domains, for instance sistemavl.ru, tatlibak.com.tr, znakspb.ru, viocom.ru and domperil.ru.
leadcontext.ru shares at least some mail servers with other domains, including prohobby.by, rosstel.su, poltawka.ru and gp-com.ru.
mx.yandex.net resolves to two IP numbers: 2a02:6b8::311 and 77.88.21.249.