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
- Not on any threat blocklist +5
- Established allocation (14y) +3
- Trust score 83 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- pcbk.ru
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 600 s
- Reverse DNS last checked
- 2026-08-23 08:18 UTC
- Forward DNS last checked
- 2026-08-23 08:18 UTC
Forward DNS records for pcbk.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 5.23.50.35 | — | 172800s |
| MX | mail.pcbk.ru | 10 | — |
| MX | mail2.pcbk.ru | 20 | — |
| NS | dns.pcbk.perm.ru | — | — |
| NS | ns3-l2.nic.ru | — | — |
| NS | ns4-cloud.nic.ru | — | — |
| NS | ns4-l2.nic.ru | — | — |
| NS | ns8-cloud.nic.ru | — | — |
| NS | ns8-l2.nic.ru | — | — |
| TXT | 05c83a9d-c116-4282-a2b8-2a7356b024be | — | — |
| TXT | 201804192127050njxcthd622fcxmidant7wxz58f1dh5eallvqrtuj37axi9dfm | — | — |
| TXT | 2019051821383136pgtx7gqkjm3cnovh3f2ikw2iiuk5qi673evfcb1l31v36ufi | — | — |
| TXT | 202007030802135q8tcpp2ht1laz8p6nvyc3sbaqytiy0gwwy6mqtt5nt04aw46f | — | — |
| TXT | 2021070221140337jhsj5e0ax28fgnl6v209foqudkvewwti5i8boh69jyftedgl | — | — |
| TXT | _globalsign-domain-verification=-Lz-Uvzy9Wrneqh74R65G0T7FF_q5DbrYX1D21icaS | — | — |
| TXT | _globalsign-domain-verification=-cxdmthhCKLZaJGZgLroqYN875meN4rrNXDyFagJ50 | — | — |
| TXT | _globalsign-domain-verification=CAdZDEzlcd-BEIFXyMHpXFFk-ZR-ySKNDaoMv8fVEH | — | — |
| TXT | _globalsign-domain-verification=TtOH_4zFDCuzsQczl01K4wbQi3L8KdsJttTxiFFqZD | — | — |
| TXT | google-site-verification=tljAMdcIkpqTvu6_14D2djSKTPDzaBmQgSQzXXoyORk | — | — |
| TXT | v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc@pcbk.ru | — | — |
| TXT | v=spf1 mx ip4:188.17.150.118 ip4:178.47.133.248/29 ip4:188.170.119.128/28 include:spf.unisender.com -all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
- vh236.timeweb.ru — Jul 3, 2026 → present
- pcbk.ru — Jun 29, 2026 → Jul 3, 2026
- vh236.timeweb.ru — Jun 25, 2026 → Jun 29, 2026
- pcbk.ru — Jun 19, 2026 → Jun 25, 2026
- vh236.timeweb.ru — Jun 11, 2026 → Jun 19, 2026
Network Allocation for 5.23.50.35
- 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_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-08-23 05:20:32
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.50.35?
5.23.50.35 is allocated to Jsc timeweb (AS9123), registered in St Petersburg, Russia.
Where is 5.23.50.35 located?
The geolocation for 5.23.50.35 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.50.35 on?
5.23.50.35 belongs to the 5.23.48.0/21 network block announced by AS9123. This range contains 2,048 addresses.
Does 5.23.50.35 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.
