Check-Host.cc

Domain

neicon.ru

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of neicon.ru

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
5
A/AAAA targets
Subdomains
23
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
5
in our scans

DNS Records

A
95.163.139.138, 95.163.139.142
AAAA
MX
10 mx.yandex.net
NS
ns1.dns2b.ru, ns2.dns2b.ru, ns3.dns2b.ru, ns4.dns2b.ru, ns5.dns2b.ru
TXT
google-site-verification=RRgGaEqxfv2EVrmQbcvGpPoRKY6ZTV0HHaDf6OWC5JU, v=spf1 include:_spf.yandex.net include:_spf.neicon.ru ~all, yandex-verification: a305132f052ed792
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
archive.neicon.ru 2026-06-22 23:29:24.788
na.neicon.ru 2026-06-23 18:22:49.720
neicon.ru 2026-06-22 23:29:24.788
autoconfig.letter.neicon.ru 2026-06-18 19:08:06.226
autodiscover.letter.neicon.ru 2026-06-18 19:08:06.226
mail.neicon.ru 2026-07-25 17:13:22.435
neuroassistant.neicon.ru
1970-01-01 00:00:00.000
rtmp.neicon.ru 2026-07-25 04:45:36.060
sapphire.neicon.ru
1970-01-01 00:00:00.000
www.conf.neicon.ru
1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: rtmp.neicon.ru
Issuer: YR2
SANs: rtmp.neicon.ru

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
A 95.163.139.142 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
NS ns2.dns2b.ru 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
MX 10 mx.yandex.net 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
A 95.163.139.138 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
NS ns5.dns2b.ru 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
TXT v=spf1 include:_spf.yandex.net include:_spf.neicon.ru ~all 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
TXT yandex-verification: a305132f052ed792 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
NS ns1.dns2b.ru 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
NS ns4.dns2b.ru 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
TXT google-site-verification=RRgGaEqxfv2EVrmQbcvGpPoRKY6ZTV0HHaDf6OWC5JU 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788
NS ns3.dns2b.ru 2026-06-01 21:31:20.733 2026-06-22 23:29:24.788