IPRisk
Multi-source IP cleanliness, network ownership, and risk signals.
Not recommended for IP-quality-sensitive sign-in, registration, payment, or long-lived account sessions. Replace the exit IP and retest first.
Shows the saved deductions, clean confirmation, and every score item from this check, matching the homepage result.
Risk findings appear first; green items were not observed in this aggregate result.
All geolocation fields remain visible; confidence represents source agreement, not GPS-level physical accuracy.
| Source | Country | Region | City | Coordinates | Timezone |
|---|---|---|---|---|---|
| IPinfo | US | Utah | Salt Lake City | 40.76, -111.89 | America/Denver |
| IP2Location | US | Utah | Salt Lake City | 40.76, -111.89 | America/Denver |
| ipapi.com | US | Utah | Salt Lake City | 40.75, -111.97 | America/Denver |
| proxycheck.io | US | Utah | Salt Lake City | 40.76, -111.89 | America/Denver |
| ipapi.is | United States | Utah | Salt Lake City | 40.76, -111.89 | America/Denver |
Exit region: US (US). Region policy and IP cleanliness are assessed separately; open “Basis” for details.
Region: The current exit region is on both the ChatGPT and OpenAI API official supported lists.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Next: ChatGPT region list · API region list
Region: The current exit region is on the Claude official supported list.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Region: The current exit region is on the Gemini web app official supported list.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Next: Official guidance
Region: The exit region presents no direct conflict; TikTok also considers SIM, device settings, and location signals.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Region: The exit region presents no direct conflict; the platform also uses profile, device, and login-history signals.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Next: Review the platform’s login location guidance
Region: The exit IP alone cannot confirm the account entity, registration region, or available platform features.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Next: Check the business entity, registration region, payment records, and current login environment.
Region: The exit IP alone cannot confirm the account entity, registration region, or available platform features.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Region: General websites do not share one region policy; check the target site’s rules.
IP: High-weight risk, Tor, or low-score signals are present; score 35/100.
Next: Test the connection on the target site and follow its region and account rules.
| Field | Value |
|---|---|
| IP Address | 31.22.111.19 |
| Reputation Score | 35/100 |
| Cleanliness Level | Elevated signals |
| IP Type | Proxy Exit |
| Country | United States |
| State / province | Utah |
| City estimate | Salt Lake City · Medium confidence · 5/5 available sources agree |
| Postal code | 84101 |
| Timezone | America/Denver |
| Reference coordinates | 40.76, -111.91 |
| ISP | Alice Networks Ltd |
| ASN | AS215355 |
| Proxy/VPN | Yes |
| Proxy Type | Proxy |
| Datacenter IP | Yes |
| Tags | Proxy |
| Last Checked | 2026-10-15 03:41:42 |
A score of 35/100 means several sources returned signals requiring attention. Exact labels, check time, and original sources are listed in the report.
31.22.111.19 is a proxy IP on Alice Networks Ltd (AS215355) in US Salt Lake City.
The system queries 16 data sources covering proxy/VPN classification, malicious ranges, threat intelligence, ASN, and port exposure. Evidence is combined with fixed weights into a 0-100 score and is generated only when completeness requirements are met.
There is no universal safe score for every website. IPRisk summarizes proxy, blacklist, network-type, and threat-intelligence signals; each service has its own rules and may use data not shown here.
This IP returned multiple risk signals. After changing the exit, return to the IP cleanliness check to retest it, then use the Environment Scan to confirm browser routing consistency.