51.250.92.246
IP address 51.250.92.246/32 was assigned to Yandex Cloud (ASN 200350) under the RU-YANDEXCLOUD block. The profile recorded a low-risk reputation with a risk score of 25. Network scanning revealed no open ports, and the service purpose was listed as firewalled. Behavioral analysis showed no honeypot hits, enumeration strikes, or WAF violations. One DNSBL listing was present in the control plane, but no known campaigns or specific threat indicators were associated with the address. Geolocation data was inconsistent, with sources disagreeing between Russia and Great Britain. The neighborhood subnet was classified as clean with zero threat siblings. Intelligence confidence remained very low due to signal contradictions. Analysts recommended monitoring the address with low severity rather than blocking due to conflicting signals. The address was active between July 20 and September 5, 2026.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | mnt-ru-yandexcloud-1 |
| ASN | AS200350 |
| Network Name | RU-YANDEXCLOUD |
| CIDR Block | 51.250.0.0/17 |
| RIR | ARIN |
| Country | RU |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS200350 |
| Network Prefix | 51.250.0.0/17 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 23% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 23% | 2 | 4 |
| reputation | 20% | 1 | 3 |
| geolocation | 17% | 2 | 3 |
| Overall | 17% | 10 | 17 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-20 12:28:41 UTC |
| Last Seen | 2026-09-05 11:37:38 UTC |
| Profile Built | 2026-09-05 11:52:53 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 51.250.92.246
Who owns the IP address 51.250.92.246?
51.250.92.246 is registered to mnt-ru-yandexcloud-1. The address falls within the 51.250.0.0/17 network block. Registration is held at ARIN.
Where is 51.250.92.246 located?
Geolocation data places 51.250.92.246 in Russia. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 51.250.92.246 malicious or safe?
51.250.92.246 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.