104.168.104.139
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
- Datacenter — common VPN/proxy host −6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (12y) +3
- Trust score 72 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- alansayce.com
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 300 s
- Reverse DNS last checked
- 2026-07-18 19:11 UTC
- Forward DNS last checked
- 2026-07-18 19:11 UTC
Forward DNS records for alansayce.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 50.3.117.85 | — | 171760s |
| AAAA | 2001:41d0:700:19b7:87a5:4bc4:f3d7:10d2 | — | 172800s |
| MX | mx.alansayce.com | 0 | — |
| NS | ns1.alansayce.com | — | — |
| NS | ns2.alansayce.com | — | — |
| TXT | v=DMARC1; p=none | — | — |
| TXT | v=spf1 a:dns.alansayce.com ~all | — | — |
| TXT | v=spf1 ip4:172.245.145.16 ip4:172.245.145.17 ip4:172.245.145.157 ip4:172.245.145.160 ip4:172.245.145.161 ip4:172.245.145.162 ip4:172.245.145.184 ip4:172.245.145.185 ip4:172.245.145.186 ip4:172.245.145.187 ip4:5.39.44.128 ip4:5.39.44.129 ip4:5.39.44.130 ip4:5.39.44.131 ip4:5.39.44.132 ip4:5.39.44.133 ip4:5.39.44.134 ip4:5.39.44.135 ip4:5.39.44.136 ip4:5.39.44.137 ip4:5.39.44.138 ip4:5.39.44.139 ip4:5.39.44.140 ip4:5.39.44.141 ip4:5.39.44.142 ip4:5.39.44.143 ip4:5.39.44.144 ip4:5.39.44.145 ip4:5.39.44.146 i | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 104.168.104.139
- CIDR range
- 104.168.104.0/23
- IP range (int)
- 1,755,867,136 — 1,755,867,647
- Prefix length
- /23
- Organization
- HostPapa
- ASN
- AS36352
- ASN name
- HostPapa
- Location
- Los Angeles, California, United States
- Coordinates
- 34.054400, -118.244000
- Accuracy radius
- 20 km
- Postal code
- 90060
- Regional Internet Registry
- ARIN
- Allocated
- 2014-08-27
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-11 09:22:55
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 | — | US |
See the full history for 104.168.96.0/19.
Frequently Asked Questions
Who owns 104.168.104.139?
104.168.104.139 is allocated to HostPapa (AS36352), registered in Los Angeles, United States.
Where is 104.168.104.139 located?
The geolocation for 104.168.104.139 maps to Los Angeles, 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 104.168.104.139 on?
104.168.104.139 belongs to the 104.168.104.0/23 network block announced by AS36352. This range contains 512 addresses.
Does 104.168.104.139 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.
