# IP Intelligence Briefing: 212.86.116.26
## Executive Summary
The IP address 212.86.116.26 presents a Moderate Risk profile (Score: 59/100) with confirmed Tor exit node indicators. The address is associated with a Ukrainian infrastructure network (ASN 6698, UA-VSYS) and is classified as a Tor exit node provider, presenting potential anonymity-related risks for inbound traffic.
## Technical Profile
Network Attribution
- ASN: 6698 (Vyacheslav Smyrnov - UA-VSYS)
- Geolocation: Kyiv, Ukraine (UA)
- Subnet: 212.86.116.0/24
- Network Classification: Tor Exit Nodes
Service Exposure
- Open Ports: 22/SSH, 80/HTTP, 443/HTTPS
- DNS Resolution: dedicated.vsys.host (vsys.host)
- TLS Certificate: CN=www.3xmwssrnwimm5tlxsqd.com (subject: www.uupuxvbxky6zvc7jw.net)
- SSHP Banner: OpenSSH_10.0p2 Debian-7+deb13u4
Threat Indicators
- Tor Exit Node: Confirmed (isTor: true)
- Blacklist Count: 1 active listing
- DNSBL Listings: 1 of 8 total lists
- Route Stability: Unstable (1 route change observed in 30 days)
- Abuse Confidence: Not definitively classified as known attacker or spam source
## Historical Activity
The IP has generated 36 total observations in the monitoring database. Recent signal activity includes:
- Multiple Tor exit node indicator observations
- Blacklist listings with high severity ratings
- Network trace hops indicating 18-hop path resolution
- Operator score: 0.1304 (labeled "Minimal")
## Neighborhood Analysis
The /24 subnet (212.86.116.0/24) shows:
- Abuse Density: 1.0 (classified as "mostly_clean")
- Threat Siblings: 1 identified within subnet
- Active Siblings: 1
## Risk Assessment
The primary risk factor is the confirmed Tor exit node classification. Tor exit nodes are commonly used to anonymize malicious traffic, though they can also serve legitimate purposes. The moderate risk score (59/100) reflects this mixed-use profile. Route instability suggests potential infrastructure changes or temporary hosting arrangements.
## Recommended Actions
Immediate Mitigation
1. Access Control: Implement enhanced verification for traffic from this IP, particularly for authentication-sensitive services
2. Logging: Increase verbosity and retention for all traffic from 212.86.116.26
Firewall Rules
```
iptables: iptables -A INPUT -s 212.86.116.26 -j DROP
nftables: nft add rule inet filter input ip saddr 212.86.116.26 drop
nginx: deny 212.86.116.26;
Cloudflare WAF: Block IP (risk score 59/100)
AWS WAF: Add to blocklist (212.86.116.26/32)
```
SOC Monitoring Priorities
- Monitor for port 22 (SSH) scanning activity from this source
- Watch for unusual traffic patterns consistent with Tor-based command-and-control
- Track DNS queries to vsys.host and related domains
## Conclusion
This IP should be blocked or subjected to enhanced scrutiny depending on organizational risk tolerance. The Tor exit node designation warrants defensive blocking for systems requiring strict trust boundaries. Monitor the subnet 212.86.116.0/24 for correlated activity from the identified threat sibling.
---
*Intel generated from IPDebrief analysis. Review firewall rules in conjunction with organizational security policies.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Vyacheslav Smyrnov |
| ASN | AS6698 |
| Network Name | UA-VSYS |
| CIDR Block | 212.86.116.0/24 |
| RIR | RIPE |
| Country | UA |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | dedicated.vsys.host |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | dedicated.vsys.host |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
CN=www.aiyeojlfnsnke7.net was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.| SANs | None |
| Valid From | 2026-01-29T00:00:00+00:00 |
| Valid Until | 2026-09-24T23:59:59+00:00 (expired) |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 238 days |
🛡️ Public Network Snapshot
| Origin ASN | AS6698 |
| Network Prefix | 212.86.116.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 59% | 2 | 21 |
| routing | 27% | 2 | 3 |
| services | 35% | 2 | 3 |
| ownership | 39% | 3 | 7 |
| reputation | 26% | 1 | 3 |
| geolocation | 32% | 2 | 3 |
| Overall | 36% | 12 | 40 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-04 22:50:11 UTC |
| Last Seen | 2026-08-27 05:06:03 UTC |
| Profile Built | 2026-08-29 05:50:32 UTC |
| Data Freshness | Live |
| Signal Types | 30 |
| Total Observations | 33 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 212.86.116.26
Who owns the IP address 212.86.116.26?
212.86.116.26 is registered to Vyacheslav Smyrnov. The address falls within the 212.86.116.0/24 network block. Registration is held at RIPE.
Where is 212.86.116.26 located?
Geolocation data places 212.86.116.26 in Kyiv, Kyiv City, Ukraine. The local time zone is Europe/Kyiv. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 212.86.116.26 malicious or safe?
212.86.116.26 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 212.86.116.26?
The reverse DNS (PTR) record for 212.86.116.26 is dedicated.vsys.host. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 212.86.116.26?
Responsive ports observed on 212.86.116.26 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.