01Down for everyone, or just for you?
When a website stops loading, two families of causes compete: a site outage (server off, crashed application, expired domain) and a local problem (DNS cache, router, blocking ISP, corporate firewall, browser extension). This check settles it by making the same request as your browser, but from Cloudflare's servers — a neutral vantage point, outside your connection.
If the site answers here, don't wait for a fix that will never come: the blockage is on your side. If the site is unreachable here too, it is very likely down for everyone — you can inspect its domain with the whois (expired?), its DNS records and its redirect chain.
02Understanding the verdict
- Up
- The site answered with a 2xx status: it works. An access problem on your side comes down to DNS, cache or local network.
- Page error
- 4xx codes: the server runs but refuses or cannot find the page — wrong URL, removed content, filtered access (some sites block automated requests).
- Server error
- 5xx codes: the web server is reachable but the application behind it is failing (502/503/504, typical of maintenance or overload).
- Unreachable
- No answer: connection impossible or timeout. Server off, broken DNS, or hosting incident.
- Redirects
- The check follows up to 5 redirects (http → https, www…) before recording the final status, as a browser would.
03From the command line
The same URL as this page answers in plain text for curl:
$ curl "its-my-ip.com/down?url=exemple.fr" status: up http: 200 url: https://exemple.fr/ redirects: 1 time: 342 ms
04Frequently asked questions
The site works for you but not for me: what should I do?
In order: force-reload past the cache (Ctrl+Shift+R), try a private browsing window (rules out cookies and extensions), test from your phone on 4G/5G (rules out your router and ISP), switch DNS servers (1.1.1.1 or 8.8.8.8). If mobile works and your landline connection doesn't, the blockage is at your ISP or in your local network.
The check says “unreachable” but the site opens in my browser: how come?
Your browser may be serving a local cache of the site, or the site blocks requests coming from datacenters (some firewalls reject anything that is not a residential browser). “Unreachable” here with a working site on your side is rare but possible — the opposite is far more common.
What do 502 and 503 errors mean?
502 (Bad Gateway): the front server answers but the application behind it is unreachable or crashed. 503 (Service Unavailable): the service is deliberately unavailable, typically during maintenance or overload. In both cases the problem is on the site's side, and it is often temporary.
Where does the test request come from?
From Cloudflare's servers, with an identified User-Agent (ItsMyIp-DownChecker) and no cookies. It is a neutral viewpoint: neither your ISP, nor your DNS, nor your cache is involved. In return, a site that filters datacenter requests may answer us differently — the verdict points it out.
Why is the check limited to public addresses?
Private addresses (192.168.x.x, 10.x.x.x…) and loopback designate machines on internal networks: testing them from a public service would be meaningless and would open the door to abuse (probing someone else's infrastructure). The check therefore refuses any non-public host, at every redirect.