Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (18y) +6
- Not on any threat blocklist +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- 95-31-6-237.static.corbina.ru
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-07-18 06:48 UTC
- Forward DNS last checked
- 2026-07-18 06:48 UTC
Forward DNS records for 95-31-6-237.static.corbina.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 95.31.6.237 | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 95.31.6.237
- CIDR range
- 95.31.0.0/20
- IP range (int)
- 1,595,867,136 — 1,595,871,231
- Prefix length
- /20
- Organization
- PVimpelCom
- ASN
- AS8402
- ASN name
- PVimpelCom
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748700, 37.618700
- Accuracy radius
- 20 km
- Postal code
- 129329
- Regional Internet Registry
- RIPE
- Allocated
- 2008-10-10
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-07-11 09:22:23
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 95.31.6.237?
95.31.6.237 is allocated to PVimpelCom (AS8402), registered in Moscow, Russia.
Where is 95.31.6.237 located?
The geolocation for 95.31.6.237 maps to Moscow, Russia based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 95.31.6.237 on?
95.31.6.237 belongs to the 95.31.0.0/20 network block announced by AS8402. This range contains 4,096 addresses.
Does 95.31.6.237 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
