Your website, seen
from another country.
We request your URL from machines in 14 countries at the same time. Then we compare what each one got back: status, address, final URL, content. If one country sees something different, you learn which country — and whose rule caused it.
Four things change at the border.
The same URL is a different trip from every country. Each of these four can quietly change the answer — and only one of them shows up in your own browser.
The address
Geo-DNS and anycast hand each country a different IP on purpose — Tokyo gets the Tokyo edge. A different address is normal. Different content is not.
by designThe distance
Light in fibre covers 200 km per millisecond and won't go faster. A visitor 8,000 km from your nearest server pays that tax on every round trip, before your code runs at all.
physicsThe permission
ISP-level blocklists and on-path filtering can sit between a country and your server. Requests die in transit — your logs never see them, so you never notice.
the pathYour own rules
Geo-blocks, region redirects, CDN country settings, a WAF being cautious. The most common cause of "not available in your region" is a rule on your side of the wire.
your rulesSix answers a country can give
Every row this tool sorts lands on one of these. Here's what each one means — and who owns the fix.
That country gets your site — same content as everyone else, whatever address it was served from. The only readout that means "nothing to see here."
The explicit geo-wall: your own server or CDN saying "we chose not to serve this region." Common on US sites that walled off the EU in 2018 and never revisited it.
Everyone else gets 200, one country gets Forbidden. Look for a country rule in your CDN, a WAF list, or a geo plugin someone installed years ago.
The connection starts and then breaks: an RST, a dropped read, or a TLS handshake that fails. On-path filtering does this — so does a broken certificate chain or an edge under load. We report the break; the next step is telling those apart.
Packets left, nothing came back, and your access log shows no request at all. From exactly one country, that pattern usually means something on the path dropped it in transit.
A geo-redirect: Germany lands on /de, Japan on jp.example.com. Fine when deliberate. A trap when the target 404s, loops, or serves last year's prices.
Whose block is it, anyway?
When one country can't see your site, the fix depends on who is blocking it. The shape of the failure tells you which:
- A page came back, fast — a 451 or 403 in under 100 ms means your own edge served the wall. That's a config, and you can change it today.
- Cut mid-handshake — the connection broke while it was opening. A middlebox on the path does this; so does an expired certificate on your edge. Check your own TLS first, because that half you can settle in a minute.
- Refused — something answered with a refusal instead of a handshake. Usually a firewall rule or a closed port at the far end, not the countries in between.
- Silence — the request died in transit and your logs never saw it. From one specific country, that's the path, not the site.
- Slow but 200 — not blocked, just far. That's a distance problem with a distance fix: an edge nearer to them.
The usual suspects
ranked by how often it's themWhat you can check locally
Some of this is doable locally. The last row is the one your terminal cannot do.
Common questions
It requests your URL at the same moment from 14 machines in 14 countries. Then it compares four things per answer: the HTTP status, the final URL after redirects, the serving IP, and a fingerprint of the returned page. Every country lands in one of two buckets — those that see your site, and those that see something else.
Four reasons cover most cases. A geo-block returns 401, 403 or 451 to some regions. A geo-redirect sends certain countries to a different site or a country landing page. A CDN serves those visitors a different edge cache. Or one region is simply having an outage, timing out while the rest load fine.
One machine in each of 14 countries across 6 continents: the United States, Canada (North America), Brazil, Peru (South America), the United Kingdom, France, Germany (Europe), Türkiye, Israel (the Europe–Asia bridge), India, Singapore, South Korea (Asia), Australia (Oceania) and South Africa (Africa). They are datacenter machines, physically in each country. Geo-DNS answers, geo-walls and CDN edges all key on the country of the source address — which these probes genuinely have.
No. We do not run probes inside China, Russia or the UAE, so this is not a censorship-testing tool. What it does show is whether the 14 countries we test from all receive the same site. Any that get a block page, a redirect, a different edge or a timeout are flagged.
It means at least one country saw something other than the majority answer while others saw your normal site. The result groups the odd-ones-out by reason: geo-wall, offsite redirect, different content, or unreachable. You see exactly which countries differ, and why.
Each probe builds two fingerprints: one from the page's HTML tag skeleton, ignoring text, scripts and per-request values, and one from the normalized text. Two countries count as the same only when both match the majority. Ordinary dynamic content does not trip a false difference.
Yes, it is completely free and no signup is required. You can leave an email on a result to be notified once if a country later changes bucket. For continuous monitoring from multiple locations with ongoing alerts, that is what the Uptimia platform is built for.
Free tools are just the start.
Uptimia keeps your sites healthy.
Uptime, SSL, domain expiry, page speed, transactions — monitored from 171+ locations worldwide. Free for 30 days.