Private first-party diagnostic
Check the IP address observed by Mexela
Compare this observation before and after enabling your proxy. The initial result is rendered by Mexela for this request and does not use an external IP, geolocation, ASN, or fingerprinting provider.
Current request
What Mexela observed
Observation complete.
Read the proxy troubleshooting guide.
- Observed IP address
- 216.73.217.146
- Address family
- IPv4
- HTTPS request
- Yes
- Observation time (UTC)
- 2026-10-22T04:37:08Z
- Request method
- GET
- Browser user agent
- Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
- Accepted language
- Not provided
This result shows what the Mexela web application observed for one request. It does not prove device-wide routing, DNS or WebRTC behavior, country, ASN, anonymity, destination acceptance, or the absence of normal infrastructure access logs.
How to use this result
- Record the observed IP address before enabling the proxy.
- Enable the proxy in the browser or application you are testing.
- Select Check again and compare the newly observed address.
- Use application-specific DNS, WebRTC, protocol, and destination tests when those properties matter.
Need a broader method? Read how to test a proxy safely and the proxy testing and troubleshooting guide.
If your proxy client reports an error
Use the symptom reported by your browser or application. This checker observes requests that reach Mexela; it cannot diagnose a proxy connection that never reaches the page. Keep passwords and authenticated proxy URLs out of reports.
- 407 or authentication rejected: confirm the username, password or approved public source IP with the proxy authentication guide.
- Connection refused or timeout: check host, port, protocol and the stage that failed. Use the connection and timeout checks; a timeout alone does not prove the proxy is offline.
- DNS or TLS error: identify which side resolves the hostname and keep certificate validation enabled. Follow the DNS and TLS troubleshooting steps.
- Protocol mismatch: compare your client's configured scheme and supported proxy type in the HTTP, HTTPS and SOCKS5 guide.
- Other errors or unclear results: separate the connection, destination response and application behavior with the proxy testing and troubleshooting guide.
