138.124.254.45
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 (33y) +6
- Not on any threat blocklist +5
- Trust score 76 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
Network Allocation for 138.124.254.45
- CIDR range
- 138.124.254.0/23
- IP range (int)
- 2,323,447,296 — 2,323,447,807
- Prefix length
- /23
- Organization
- Denis Aleksandrovich Iakovlev
- ASN
- AS214891
- ASN name
- Denis Aleksandrovich Iakovlev
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748400, 37.617500
- Accuracy radius
- 20 km
- Postal code
- 117485
- Regional Internet Registry
- ARIN
- Allocated
- 1993-09-01
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-11 09:23:19
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 | — | CH |
See the full history for 138.124.254.0/23.
Frequently Asked Questions
Who owns 138.124.254.45?
138.124.254.45 is allocated to Denis Aleksandrovich Iakovlev (AS214891), registered in Moscow, Russia.
Where is 138.124.254.45 located?
The geolocation for 138.124.254.45 maps to Moscow, 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 138.124.254.45 on?
138.124.254.45 belongs to the 138.124.254.0/23 network block announced by AS214891. This range contains 512 addresses.
Does 138.124.254.45 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.
