IP Judge ipjudge.org

Claude Code / Codex exit check

A clean browser doesn’t mean Claude Code is clean. The terminal’s exit needs its own check.

Run this in your terminal:

curl -sL ipjudge.org/en/cc | bash
Read-only: it installs, changes and uploads nothing. It asks api.anthropic.com, claude.ai, api.openai.com and chatgpt.com which IP they see, compares with the no-proxy exit, and checks IPv6 and the time zone. Below is the browser-side check — compare its “IP used for Claude”.

CheckingRuns only between your browser and this site. No sign-up.

Checking your network exit…

Looking up your IP…

Can you use these AI platforms?

By each company’s official regions + the exit you actually reach them from
ChatGPTOpenAI
Checking
ClaudeAnthropic
Checking
GeminiGoogle
Checking
MuseMeta
Checking

How to fix

Most serious first · what happened → how to fix it

When all checks finish, issues and fixes are listed here, most serious first.

Who sees which of your IPs

Grouped by exit

Shown when the checks finish.

Use cases

A fit score, not a success rate · how

Calculating…

■ 80+ suitable■ 55–79 usable, with risk■ below 55 not recommended

IP details

The exit that opened this site

Looking up…

Browser and connection checks

13 checks · tap for details · run only between your browser and our probe
IP used for Claude
Checking…
IP used for ChatGPT
Checking…
Reaching Gemini
Checking…
IPv4 exit
Checking…
IPv6 exit
Checking…
WebRTC
Checking…
DNS resolver
Checking…
Exit for unlisted domains
Checking…
TLS fingerprint
Checking…
TCP fingerprint
Checking…
Browser time zone
—
Browser language
—
Automation traces
Checking…

Proxies often route by domain: the IP that opened this site is not necessarily the one Claude or ChatGPT sees. The first two checks ask claude.ai and chatgpt.com directly.

FAQ

Why do the terminal and browser use different exits?

Many proxy apps default to “system proxy” mode: browsers follow it, terminals don’t. Without HTTPS_PROXY, Claude Code goes direct. TUN / enhanced mode, or setting the variables, fixes it.

How do I set a proxy for the terminal?

Add this to ~/.zshrc or ~/.bashrc (use your proxy app’s HTTP / mixed port, often 7890 or 7897):

export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890
Open a new terminal and run the check again. Per Claude Code’s docs, it only reads https_proxy / HTTPS_PROXY / http_proxy / HTTP_PROXY — no SOCKS, and no ALL_PROXY. You can also put them in the env block of ~/.claude/settings.json, which is the only place background Claude Code sessions read.

What about Windows?

Run the same command in Git Bash or WSL. In PowerShell, curl.exe -s https://api.anthropic.com/cdn-cgi/trace shows the ip= and loc= lines.

Further reading

Look up another IP

Enter an IPv4 or IPv6 address for the full report.

Which exit do Claude Code / Codex use?

A clean browser doesn’t mean a clean terminal. Run this in your terminal:

curl -sL ipjudge.org/en/cc | bash

Why the terminal needs its own check →