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
- Listed on 1 threat blocklist −30
- Long-established allocation (32y) +6
- Trust score 41 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
Network Allocation for 170.168.31.189
- CIDR range
- 170.168.31.0/28
- IP range (int)
- 2,863,144,704 — 2,863,144,719
- Prefix length
- /28
- Organization
- Alex Largman
- ASN
- AS59651
- ASN name
- Alex Largman
- Location
- Uman, Cherkasy Oblast, Ukraine
- Coordinates
- 48.747700, 30.215100
- Accuracy radius
- 20 km
- Postal code
- 20310
- Regional Internet Registry
- RIPE
- Allocated
- 1994-07-20
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country, maxmind_asn
- Last updated
- 2026-07-21 04:11:34
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | HK |
See the full history for 170.168.28.0/22.
Frequently Asked Questions
Who owns 170.168.31.189?
170.168.31.189 is allocated to Alex Largman (AS59651), registered in Uman, Ukraine.
Where is 170.168.31.189 located?
The geolocation for 170.168.31.189 maps to Uman, Ukraine 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 170.168.31.189 on?
170.168.31.189 belongs to the 170.168.31.0/28 network block announced by AS59651. This range contains 16 addresses.
Does 170.168.31.189 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.
