Type a website. We look up its domain, connect from our server and follow its redirects, then tell you whether it is up, down for everyone, returning an error page, or just blocking bots, with the reason in plain words. If it is up here but not for you, the problem is most likely on your side. Free, no signup.
Checks run live from a server in Canada; nothing is cached.
| Up | The server answered with a normal page (2xx, after any redirects). It works for us, so if it doesn't for you, see the checklist below. |
| Down | The domain doesn't resolve, the connection is refused or times out, the HTTPS certificate fails, a redirect loops, or the server answers with a 5xx error (500, 502, 503, 504). |
| Error page | The server works, but this address returns 404 Not Found or another 4xx. The site is up; the page isn't. |
| Bot wall | The server answered, but with 403, 429, 202 or a challenge page that big sites send to unknown fetchers. The site is almost certainly up for people. Take a screenshot to see what a real browser gets. |
| Your connection | Open another site you know works. If none load, restart the router or switch between Wi-Fi and mobile data. |
| DNS cache | An old address may be cached after a site moved. Flush it (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS) or try another DNS resolver such as 1.1.1.1. |
| Browser | Try a private window: it skips extensions, cookies and the cache. Ad blockers and privacy extensions break some sites. |
| Blocked for you | Some sites block countries, VPN or company networks. Try with the VPN off, or from a phone on mobile data. |
We ran this checker on these sites on 26 October 2026, from a server in Canada. All 19 were up, but 6 answered a plain checker with a bot wall (403, 429 or Amazon's empty 202) instead of their page. A down checker that reads every 403 as "down" would have called a third of them broken; that is why bot walls get their own verdict here. Times include every redirect.
| Site | Result |
|---|---|
| example.com | Up: HTTP 200, 65 ms no redirect |
| github.com | Up: HTTP 200, 53 ms no redirect |
| wikipedia.org | Up: HTTP 200, 107 ms 1 redirect |
| bbc.co.uk | Up: HTTP 200, 34 ms 1 redirect |
| cloudflare.com | Up: HTTP 200, 125 ms 1 redirect |
| shopify.com | Up: HTTP 200, 135 ms 1 redirect |
| stripe.com | Up: HTTP 200, 184 ms 1 redirect |
| youtube.com | Up: HTTP 200, 211 ms 1 redirect |
| linkedin.com | Up: HTTP 200, 294 ms 1 redirect |
| apple.com | Up: HTTP 200, 351 ms 1 redirect |
| netflix.com | Up: HTTP 200, 467 ms 2 redirects |
| facebook.com | Up: HTTP 200, 876 ms 1 redirect |
| microsoft.com | Up: HTTP 200, 1559 ms 2 redirects |
| amazon.com | Bot wall: HTTP 202, 72 ms 1 redirect |
| reddit.com | Bot wall: HTTP 403, 35 ms 1 redirect |
| nytimes.com | Bot wall: HTTP 403, 77 ms 1 redirect |
| stackoverflow.com | Bot wall: HTTP 403, 108 ms 1 redirect |
| chatgpt.com | Bot wall: HTTP 403, 18 ms no redirect |
| google.com | Bot wall: HTTP 429, 332 ms 1 redirect |
The same checks run over the Shotmint API for free with any key (500 a day, 0 credits), so an uptime script, cron job or Make/n8n/Zapier scenario can alert you when a site goes down, then screenshot what visitors see:
curl "https://shotmint.creasework.com/v1/check?type=up&url=example.com" \
-H "X-API-Key: YOUR_KEY"
# {"type":"up", "verdict":"up", "status":200, "total_ms":..., "summary":"example.com is up: HTTP 200 in ... ms.", ...}
A free, keyless status badge for a GitHub README, docs page or status page: it shows up in green, an error code in orange, or down in red, and is re-checked at most every 5 minutes. Clicking it opens this checker for the details.
[](https://shotmint.creasework.com/is-it-down?url=example.com)
Replace example.com with your domain (after a check above, this snippet already uses it). GitHub caches README images for a few minutes, so a badge there can lag by that much. Certificate expiry badge: SSL checker.
More site checks: SSL checker, redirect checker, HTTP header checker, broken link checker. Get a free API key