5.227.60.173
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
- Not on any threat blocklist +5
- Enterprise allocation +4
- Established allocation (14y) +3
- Trust score 77 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
Domains hosted
as of 2026-10-04 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — counted once a week from issued.live's DNS snapshot.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Network Allocation for 5.227.60.173
- CIDR range
- 5.227.32.0/19
- IP range (int)
- 98,770,944 — 98,779,135
- Prefix length
- /19
- Organization
- MTS PJSC
- ASN
- AS8580
- ASN name
- MTS PJSC
- Location
- Nizhniy Novgorod, Nizhny Novgorod Oblast, Russia
- Coordinates
- 56.332700, 44.001200
- Accuracy radius
- 20 km
- Postal code
- 603000
- Regional Internet Registry
- RIPE
- Allocated
- 2012-09-07
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-10-06 04:03:54
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 5.227.60.173?
5.227.60.173 is allocated to MTS PJSC (AS8580), registered in Nizhniy Novgorod, Russia.
Where is 5.227.60.173 located?
The geolocation for 5.227.60.173 maps to Nizhniy Novgorod, 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 5.227.60.173 on?
5.227.60.173 belongs to the 5.227.32.0/19 network block announced by AS8580. This range contains 8,192 addresses.
Does 5.227.60.173 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.
