Fastsoft / Guide
Practical guide
On page load, probe the exits seen by ChatGPT, Cloudflare and a China-based site, then inspect ownership, third-party risk flags, OpenAI API response, WebRTC and browser details.
How to use it
- Open the page and wait for the three exit cards and location details.
- Review the environment reference score, six weights and observed-signal coverage. Missing IP intelligence contributes a neutral value.
- Review ChatGPT and OpenAI API responses, then hide IPs or clear local history if needed.
Example
Different exits on the ChatGPT and Cloudflare cards may mean these browser requests followed different routes. Interpret them using your own proxy rules.
What to know
The reference score weights IP intelligence 40, IP flags 15, supported region 20, time zone 10, language region 5 and exit consistency 10. Missing signals contribute a neutral 50 and lower coverage. It is not an official OpenAI score; low-coverage results are preliminary. HTTP 401 from the OpenAI API only confirms that an unauthenticated request received a response; it does not prove Codex, sign-in or account access. No authoritative DNS probe is deployed, so DNS leak status remains unknown.
Interpreting the results
- The three exit cards contact different sites; proxy routing and IPv6 rules may affect each route. The China-site card does not guarantee a China-based IP.
- The region label uses a snapshot of OpenAI’s official ChatGPT supported locations. The API has its own official list; check the current official pages for changes.
- Fastsoft queries IPQuery through its IP intelligence endpoint and falls back to IPinfo for basic ownership. Responses may be cached for up to 30 minutes and are not written to D1. History stays in this browser.
- WebRTC candidates describe this browser only. A mismatch with the ChatGPT exit does not prove a true IP leak; device details are not published OpenAI risk rules.
Common question
Why is score coverage low or DNS status unknown?
The IP intelligence provider may be blocked or rate limited; that signal then contributes a neutral value and lowers coverage. No total is shown without the target exit IP. A credible DNS leak test needs dedicated authoritative DNS infrastructure; an ordinary page cannot infer it.