Reading iphey Results with a Proxy
iphey gives one headline verdict, five tiles and a score called MX Score. Its site explains little about how the verdict is reached, so we read the script that draws the results on iphey.com on October 30, 2026. The headline is simpler than it looks: any single flagged signal turns it from Trustworthy to Unreliable. This guide explains each part, which red items matter on real websites, and how to fix them when you browse through a proxy.
Short answer
- The headline label is binary in ipheyโs current page code: Trustworthy when no signal is flagged, Unreliable when at least one is.
- MX Score runs from 0 to 100. The page colors 70 and above as good, 40 to 69 as a warning and below 40 as bad.
- Most proxy-related reds come from a location mismatch: the IP points to one country while the browserโs time zone or language says another.
- iphey runs on MixVisit, an open-source fingerprint library. A green result covers what that library and ipheyโs IP data measure, nothing more.
What iphey checks
The iphey results page shows five tiles: Browser, Location, IP address, Hardware and Software. Each fills in once the test completes. iphey says it compares browser settings with a database of fingerprints collected from real people, and its FAQ lists inputs such as the user agent, canvas, WebRTC, audio and fonts.
The client-side collection comes from MixVisit, an MIT-licensed JavaScript fingerprint library whose README names iphey.com as its demo. That is useful: you can read what the library collects instead of guessing. The IP checks run on ipheyโs side and are not documented in the same way.
How the labels and score are decided
| Item | Good | Warning | Bad |
|---|---|---|---|
| Headline label | Trustworthy (no signals) | None | Unreliable (one or more signals) |
| MX Score | 70 to 100 | 40 to 69 | Below 40 |
| Fields named risk score | Below 34 | 34 to 66 | 67 and above |
| Fields named risk | low | medium | high |
| True or false fields | false | None | true |
iphey does not document its thresholds, but its page code applies them in plain sight. What we found on October 30, 2026:
- The headline reads Trustworthy when the result contains no signals and Unreliable when it contains at least one. There is no middle label in the current code.
- A tile that carries a signal changes its text to โClick here to seeโ and turns red; the details panel shows the signalโs message.
- MX Score is drawn on a 0 to 100 ring and colored by tier.
- Rows in the details panel ending in โrisk scoreโ are colored by their own thresholds, and rows reporting a โriskโ of low, medium or high map directly to green, amber and red. A yes or no field that reads true is shown in red.
These thresholds belong to ipheyโs display, so they can change at any release. They also mean one unimportant mismatch is enough to show Unreliable, even with a high MX Score.
Fixing red items when you use a proxy
Open the red tile, read the signal, then fix the one thing it names. Common cases:
- Location. The browserโs time zone or language does not match the IPโs country. Set the browser profileโs time zone and language to the exit location. Our What is my IP page shows the time zone for your current address, so you can compare it with your device clock.
- IP address. The address is labeled as a VPN, proxy or hosting address. Hosting ranges are easy to label; a carrier address usually shows the operator as its network. Check the network name on the ASN lookup.
- WebRTC. The browser reveals a different public address than the one you browse from. Run our WebRTC leak test and limit WebRTC in the profile until only the proxy address appears.
- Hardware and Software. The claimed device does not fit the measured one, for example a phone user agent on a desktop screen and graphics card. Partial spoofing causes more mismatches than no spoofing at all. Change the whole profile or none of it.
- Browser. Traces of automation or a modified browser. A test run from an automated session is measuring the automation.
Rerun the test after each change, and change one thing at a time. If you use a rotating line, make sure the IP did not change between the start and the end of the test.
What real sites actually use
A checker shows what a page can collect. A websiteโs defense decides what to do with it, usually with more data than any checker has. The W3Cโs guidance on browser fingerprinting separates passive fingerprinting, from headers and the IP address, from active fingerprinting, where a site runs script in the browser. It also concludes that eliminating fingerprinting entirely is implausible, which is why a perfect checker result is not the goal.
Anti-bot vendors add signals iphey does not show. Imperva describes combining static, challenge-based and behavioral analysis for every visitor. Cloudflare lets Bot Management customers act on JA3 and JA4 TLS fingerprints in their own rules, a signal from the connection itself that page scripts cannot see. Behavior over time and account history matter too. Use iphey to catch the mismatches you created, not as a prediction of how a site will treat you.
Checking the same items yourself
Our tools measure single items without a score, so you can see the raw values:
- WebRTC leak test: the ICE candidates the browser exposes, including any public address.
- JA4 fingerprint checker: the TLS fingerprint observed for your request.
- DNS leak test: which resolvers your device uses and whether their country matches your IP.
- What is my IP: the address, provider and time zone a website sees.
With Coronium mobile proxies, the exit is a carrier address on a physical device with its own SIM, rented to one customer, which keeps the IP tile from reading as a hosting range. The location and browser tiles still depend on how you set up the profile.
Sources and review scope
Sources reviewed October 30, 2026. Each checker was reviewed on October 30, 2026 from its own documentation, its published page scripts or an archived copy of its page, as the article states. Checkers change without notice, and a checker verdict is not a websiteโs decision. We do not see any siteโs private risk rules.
Frequently asked questions
Read another checker
How each public checker reaches its verdict, and which of its findings a real site can act on.
Related workflows
See the fingerprint values your browser exposes.
Compare your IPโs time zone with your device.
Another checker, with a consistency verdict.
How sites read the browser beyond the IP.
Separate the exit IP, GeoIP data and browser location.
The layers a site can check, from IP to TLS.
The full set of error and checker guides.
Where to get a dedicated line
A Coronium mobile proxy is one physical device with its own SIM, rented to one customer. It connects over HTTP or SOCKS5, the IP changes by dashboard button, API link or timer, and data is not metered on dedicated lines. Brazil lines are the exception: 20 GB of data a month and a new IP on request only, with no timer. Stock and prices differ by country and carrier.