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
- Long-established allocation (15y) +6
- Trust score 71 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
Geolocation
All 1 IP addresses in 134.17.16.240/32
BGP Routing
Live BGP anomalies →This block is announced in BGP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | RIR Transfer | arin | ripe |
Frequently Asked Questions
What is 134.17.16.240/32?
134.17.16.240/32 is a CIDR network block containing 1 IPv4 addresses (from 134.17.16.240 to 134.17.16.240). CIDR notation combines an IP address with a prefix length to define a range of addresses.
Who owns the 134.17.16.240/32 network?
The 134.17.16.240/32 range is allocated to Mobile TeleSystems JLLC and announced via AS25106 from Belarus.
How many IP addresses are in 134.17.16.240/32?
134.17.16.240/32 contains exactly 1 usable IPv4 addresses. A /32 prefix length means 1 addresses are covered by this single routing entry.
