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
- Trust score 70 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
Web3 / decentralized network node
This IP is an observed participant in a decentralized blockchain network. It’s a neutral signal — it does not affect the trust score.
Observed from public blockchain peer lists (Arweave network) — how we collect this →
Network Allocation for 139.64.164.124
- CIDR range
- 139.64.164.0/24
- IP range (int)
- 2,336,269,312 — 2,336,269,567
- Prefix length
- /24
- Organization
- GTHost
- ASN
- AS63023
- ASN name
- GTHost
- Location
- Denver, Colorado, United States
- Coordinates
- 39.739100, -104.986600
- Accuracy radius
- 20 km
- Postal code
- 80252
- Regional Internet Registry
- ARIN
- Allocated
- 2020-06-24
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite, maxmind_asn
- Last updated
- 2026-07-11 09:23:20
Frequently Asked Questions
Who owns 139.64.164.124?
139.64.164.124 is allocated to GTHost (AS63023), registered in Denver, United States.
Where is 139.64.164.124 located?
The geolocation for 139.64.164.124 maps to Denver, United States 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 139.64.164.124 on?
139.64.164.124 belongs to the 139.64.164.0/24 network block announced by AS63023. This range contains 256 addresses.
Does 139.64.164.124 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.
