212.35.160.182
212.35.160.182 is an IPv4 address operated by ROSTELECOM-AS - PJSC Rostelecom, RU (AS12389), with approximate network location Tula, Russia. It belongs to a mobile network. As of November 14, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | ROSTELECOM-MNT |
| ASN | AS12389 |
| Network Name | RU-ROSTELECOM-TULA-North-Broadband |
| CIDR Block | 212.35.160.0/21 |
| RIR | RIPE |
| Network registration country | RU |
| Routing operator | ROSTELECOM-AS - PJSC Rostelecom, 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 Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| caa | Not applicable |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Unknown / lookup inconclusive 182.160.35.212.in-addr.arpa |
| fcrDns | Not checked |
☁️ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Firewalled / No Services |
| Network Tier | End-User — Residential ISP endpoint |
🔌 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
| Port | Latest capture attempt |
|---|---|
| 443 | Certificate not captured; current certificate unknown (unreachable) |
| 8443 | Certificate not captured; current certificate unknown (unreachable) |
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS12389 |
| Network Prefix | 212.35.160.0/23 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 45% | 2 | 5 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 30% | 2 | 3 |
| reputation | 15% | 1 | 2 |
| geolocation | 21% | 2 | 2 |
| Overall | 23% | 9 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Fresh
| First Seen | 2026-11-05 13:10:31 UTC |
| Last Seen | 2026-11-13 05:39:45 UTC |
| Profile Built | 2026-11-14 05:41:16 UTC |
| Data Freshness | Fresh |
| Signal Types | 19 |
| Total Observations | 21 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 212.35.160.182
Who owns the IP address 212.35.160.182?
212.35.160.182 is registered to ROSTELECOM-MNT. The address falls within the 212.35.160.0/21 network block. Registration is held at RIPE.
Where is 212.35.160.182 located?
Geolocation data places 212.35.160.182 in Tula, Tula Oblast, Russia. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 212.35.160.182 malicious or safe?
212.35.160.182 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.
Is 212.35.160.182 a VPN, proxy, or data center address?
212.35.160.182 is classified as a mobile network based on network ownership and behavioural analysis.