See how your website looks from other countries.

Enter a URL and every Emercom location that can take screenshots loads it and captures the page as it arrives there, together with the HTTP status, final URL, headers and HTML source that location received. Free, no signup.

Paste any public HTTP or HTTPS URL. Each location requests the page itself, so you see what visitors in that country are served, redirects, language versions, consent banners and block pages included.

Try:

Note: All checks are public. Create a free account to keep your checks private and get an email if your site stops responding.

What is a Website Screenshot Check?

A website screenshot check loads a page from a remote location and captures an image of what came back. Emercom takes the screenshot on its own monitoring nodes: the node resolves the hostname, requests the page over its own network connection and renders the result into an image. What you see is the page as a visitor near that node would receive it.

Each of those locations also runs a full HTTP check, so every screenshot comes with the HTTP status code, the final URL after redirects, the response headers and the HTML source, plus the network diagnostics an HTTP check runs: ping, DNS lookup, MTR and, for HTTPS, the certificate the server presented.

The status code says what the server answered. The screenshot shows what that answer looks like: the page you expected, a cookie wall, a country block page, or an error page that still came back as a 200 OK.

Why Check How Your Site Looks From Other Countries?

Many sites serve different content depending on where a request comes from, on purpose or by accident. From your own desk you only ever see one version. These are the usual differences:

  • Geo-redirects and language versions. A visitor in another country may land on a regional domain or a translated page, and a broken redirect rule can send them somewhere that does not exist.
  • Country blocks. Firewall, CDN or licensing rules can show some countries a block page while everyone else sees the site.
  • Consent and cookie banners. Sites often show a consent wall only to visitors from certain regions, and a banner can cover most of the page.
  • CDN edge problems. A misconfigured or stale edge in one region can serve an old version of the page, or an error, to visitors there only.
  • Network-level blocking. In some countries an ISP or a national filter replaces the page with its own notice, which a status code alone may not reveal.

Comparing the screenshots side by side, with the status code and final URL under each one, shows which locations got the page you intended and which got something else.

What You Get From Each Location

The screenshot is the first thing you see, and the rest of the HTTP check from the same location sits next to it:

  • Screenshot of the top of the page, as that location received it.
  • HTTP status code and response time.
  • Final URL after any redirects.
  • Response headers and the HTML source of the page.
  • Network diagnostics: ping, DNS lookup, MTR and, for HTTPS, the served certificate.

How the Screenshots Are Taken

Screenshots come from a lightweight renderer that runs on the monitoring node itself. That keeps the capture in the location it claims to come from, on nodes small enough to work as monitoring probes, but it is not a full desktop browser, and it differs from one in a few ways:

  • It captures the top of the page, roughly one screen, at a fixed width.
  • On some locations it renders with JavaScript turned off, so content a page builds in the browser, such as a single-page app, may be missing. Pages that rely heavily on JavaScript can render incompletely on any location.
  • Rendering needs more memory than a network check, so only some locations take screenshots, and a very heavy page can fail to render. The result then says so, and the HTTP status, headers and HTML source from that location are still there.
  • Screenshots are captured after the HTTP check, so they can appear later than the rest of the result.

Read the screenshot together with the status code. A blank or partial image next to an HTTP 200 and a complete HTML source usually means the renderer could not draw the page, not that the site is down in that location.

Common Uses for Website Screenshots

A screenshot from another country is most useful when someone there sees something you cannot reproduce from where you are.

Launching in a New Market

Before announcing a site in a new country, confirm that visitors there get the right language and domain instead of a redirect loop or a block page.

Geo-Blocking Rules

After changing firewall, CDN or WAF country rules, check that the blocked regions see the block page and every other region sees the site.

Support Tickets From Abroad

When a customer in another country says the site looks broken, a screenshot from a location near them shows what they are likely seeing, with the status code and headers to explain it.

Consent Banner Checks

Confirm that consent and cookie banners appear for visitors in the regions that need them, and that they stay out of the way elsewhere.

Frequently Asked Questions

Quick answers to the most common questions about website screenshots from other countries.

Enter the URL on this page and run the check. Every Emercom location that can take screenshots loads the page over its own connection and captures it, so you get one screenshot per location, labelled with where it was taken, along with the HTTP status code and final URL that location received.

Not exactly. The page is rendered by a lightweight renderer on the monitoring node, not by a full desktop browser. It captures the top of the page at a fixed width, some locations render with JavaScript turned off, and pages built mostly in JavaScript can render incompletely. The HTTP status, headers and HTML source next to each screenshot show exactly what the server sent.

Rendering a page needs far more memory than a ping or an HTTP request, and many monitoring nodes are small servers. Screenshots run only on the locations with room for them, and each render runs under a memory cap so it leaves room for the monitoring checks on the same node. The Screenshot tab in the full tools lists the locations that can take them.

Usually because the site decides what to serve based on where the request comes from: a redirect to a regional domain or language, a consent banner shown only in some regions, or a country block. It can also be a CDN edge in that region serving an older or broken copy. The final URL and response headers under the screenshot usually show which one it is.

The renderer could not finish the page: it ran out of memory or time, or the page needs JavaScript that was not run. If the same location shows an HTTP 200 and a complete HTML source, the site answered normally and only the capture failed. If the status is an error or the request timed out, the location could not load the page at all.

Yes, for HTTP monitors checked from locations that can take screenshots. When a check on such a location fails, a screenshot is captured along with the other diagnostics in the Forensic Snapshot. The tool on this page is a one-time check.

Monitor this website automatically

A screenshot shows the page once. An HTTP monitor checks it around the clock, on the interval you choose from every minute up to hourly, and alerts you by email, SMS, voice call or Telegram once enough locations agree the site is down. When a check fails on a location that can take screenshots, its Forensic Snapshot includes a screenshot of the page as it looked there.

Choose what to allow. Essential cookies keep you signed in and protect forms; they are always on.