Browser-direct · 16-host probe

IP connectivity test

An ICMP ping from a server does not tell you whether your browser can actually reach a site. Check your active public egress IP above, then probe 16 major domestic, global and AI endpoints directly from your browser tab.

16 live targetsDirect from browserGlobal & AI groupsHTTP RTT timing

Egress IP & browser reachability bench

Confirm which egress IP your browser is currently using, then click Start test below to measure reachability and HTTP response latency.

Waiting for the report…
Current egress IP — — —
Heuristic risk score / 100
— pts
—
Network type—
ASN—
Native IP—
Checked at—

How to read it:—

Reputation:—

Source:—

216-site browser reachability & latency

Direct browser reachability & response time

Click Start test to send lightweight HEAD requests from your browser to domestic, global and AI hosts in parallel without reading page content.

Not tested Direct from your browser · current network only

Reachable means your browser received an HTTP response; regional account gates, login CAPTCHAs or API quotas are checked separately.

Why test from the browser instead of ICMP ping?

Split-tunnel routing, browser secure-DNS (DoH), enterprise firewalls and CDN edge rules treat browser HTTPS traffic very differently from terminal ICMP packets. A host can answer ping in 20 ms while resetting TLS handshakes in Chrome.

This tool dispatches lightweight no-cors HEAD requests straight from your browser without reading cookies or page bodies, measuring the exact network path your browser uses.

How to read reachability groups and latency

Targets are grouped into China (Douyin, Taobao, WeChat, Bilibili), Global (Google, YouTube, Facebook, GitHub, TikTok, X, Discord) and AI platforms (OpenAI, ChatGPT, Claude, Gemini, Perplexity).

  • ≤ 220 ms (green): responsive interactive browsing and low handshake overhead
  • 221–500 ms (amber): usable for web apps and chat, noticeable on media-heavy pages
  • Global OK but AI hosts unreachable: often an edge WAF or ASN block on cloud/datacenter ranges
  • Reachable here yet blocked after sign-in: TCP/TLS succeeded, so check official regional gates on our ChatGPT, Claude or Gemini IP tools

Debugging a headless Linux VPS? Use curl

When testing a remote server without a browser, run a single curl command to print an instant terminal diagnostic card with ASN, risk flags and 8 AI readiness scores:

curl -sL https://ip-find.com/en/
curl -sL https://ip-find.com/8.8.8.8
curl -s https://ip-find.com/ip

Frequently asked questions

Do these connectivity probes pass through ip-find’s server?

No. Every HEAD request is sent directly by your browser to the target domain. Our server never proxies the traffic or sees your session cookies.

Why does a site show Reachable when it still says 'Unavailable in your region'?

Reachable confirms that DNS, TCP and TLS completed and an HTTP response arrived. Regional restrictions are enforced at the application layer based on your egress IP country.

Is the millisecond value a bandwidth speed test?

No. It measures total browser round-trip time for connection setup and HTTP headers (similar to HTTP RTT), not megabits-per-second download throughput.

What should I do after switching networks or routing rules?

Click Check current IP again at the top, then click Test again on the connectivity card so both panels reflect the new route.

HTTP reachable, but still hitting AI region blocks?

Once network reachability passes, verify whether your egress country and ASN pass ChatGPT, Claude, Gemini or TikTok risk rules.