DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check exit IP, timezone and locale before a site test with Foxprofile

Confirm a proxy's country, timezone and datacenter status before a geo-specific test.

Authorization notice. Foxprofile is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA QA tester or web developer who must show a site as it appears to visitors in one country.

The problemA proxy can leave from an unexpected country or datacenter, and a random locale can make the test look wrong.

The outcomeA profile with a checked exit IP, a pinned timezone and a fixed locale, ready for a consistent test run.

What you need first

  • Python 3.10 or newer
  • Windows, macOS or Linux
  • A few hundred MB of free disk space for Camoufox and the GeoIP database
  • A proxy per profile if you want a separate exit IP for each identity

Steps

  1. Complete setup with pip install -r requirements.txt and python -m camoufox fetch, then start the app with python -m src.main
  2. Create a profile and enter the proxy in the format host:port or socks5://user:pass@host:port
  3. Open the profile dialog and set Timezone (for example Asia/Ho_Chi_Minh) and Locale (for example vi-VN)
  4. Run Check IP on the profile and read the warnings for country or timezone mismatch and datacenter IPs
  5. Launch the profile and load the target page to start the test

Prompt for your agent

Using the repo chienbm98/foxprofile, create or update the profile <profile-name> with the proxy <proxy-url>, timezone <IANA-zone> and locale <locale>, then run Check IP. Return the exit IP and any warnings. Verify that the timezone and locale fields hold the values you set and are not blank.

Caveat. The README warns that GeoIP databases can disagree, so a Vietnamese IP may get Asia/Bangkok instead of Asia/Ho_Chi_Minh unless you pin the timezone yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page