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
- Has a reverse-DNS (PTR) record +5
- Established allocation (14y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- vds-kuhni33526.timeweb.ru
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 600 s
- Reverse DNS last checked
- 2026-07-18 05:42 UTC
- Forward DNS last checked
- 2026-07-18 05:42 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 5.23.53.149
- CIDR range
- 5.23.48.0/21
- IP range (int)
- 85,405,696 — 85,407,743
- Prefix length
- /21
- Organization
- Jsc timeweb
- ASN
- AS9123
- ASN name
- Jsc timeweb
- Location
- St Petersburg, St Petersburg, Russia
- Coordinates
- 59.941700, 30.309600
- Accuracy radius
- 20 km
- Postal code
- 195213
- Regional Internet Registry
- RIPE
- Allocated
- 2012-05-07
- Data source(s)
- maxmind_city, maxmind_asn, maxmind_country, ipinfo_lite
- Last updated
- 2026-07-11 09:19:13
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.23.53.149?
5.23.53.149 is allocated to Jsc timeweb (AS9123), registered in St Petersburg, Russia.
Where is 5.23.53.149 located?
The geolocation for 5.23.53.149 maps to St Petersburg, 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.23.53.149 on?
5.23.53.149 belongs to the 5.23.48.0/21 network block announced by AS9123. This range contains 2,048 addresses.
Does 5.23.53.149 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.
