Checks from our server whether a website answers right now: its status code, how long it took, whether the name resolves and whether the certificate is valid. For anyone asking "is my site down, or is it just me?", with the limit that it shows one location.
How to use it
Enter the address of the site. You can leave out https://.
- Type or paste the address and press Run check.
- Read the top line: it says whether the site answered, and from where it was checked.
- Look at the findings, starting with the critical ones: an unreachable site, a missing DNS record or an expired certificate.
- If it answers here but not for you, the problem may be on your side or in a region this check cannot see.
How Reavlo tests this
This tool runs on our server, because a browser cannot ask another site for its status. Nothing about the request is stored or logged: not the address, not the answer.
One location. Every check is made from our server, which is one place on the internet. A site that is down only for some regions, networks or providers can look fine here, and a site that blocks our server can look down while it works for everyone else. The tool always says that it was checked from one location.
Request. One request to the address with up to 3 redirects, a time limit and a size cap; only the status and headers are read. The response time is measured on our server and includes the name lookup, the connection, the certificate exchange and the redirects, so it is a rough number to compare with itself, not a benchmark. Addresses that point to private or internal networks are refused before any connection is made.
Statuses. A status of 500 or higher is critical, and 400 to 499 is a warning, as RFC 9110 defines them. A timeout, a failed connection or a name that does not resolve is reported as the site not answering.
DNS. The A and AAAA records of the host are looked up with our server's resolver. A name with neither is critical. A lookup that itself fails is reported as unknown, not as missing.
Certificate. For https addresses the certificate of the final connection is read: the issuer and the end date. An end date in the past is critical, and 14 days or fewer left is a warning. A certificate that the server does not trust (a wrong name, an unknown issuer) stops the connection and is reported as a failed connection.
Limits. The tool does not run JavaScript, so a page that loads blank in the browser can still answer 200 here. It makes a single request per run and does not monitor the site over time: for that you need an uptime monitor.
Questions
Is the address I enter stored?
No. The address goes to our server only to make the request, and neither it nor the answer is stored or written to a log. Analytics records only that the tool ran, never the address.
Why does the tool say the site is up when I cannot open it?
The check is made from our server. The problem can be on your network, your browser, your DNS cache, or in a region or provider that has trouble reaching the site. Try another network or device.
Why does the tool say the site is down when it works for me?
Some sites or firewalls block requests from data centres, and a site can be slow or fail for one location only. A result from one location is a clue, not a verdict.
What does the response time include?
Everything between our server starting the request and receiving the status: the name lookup, the connection, the certificate exchange, any redirects and the wait for the server.
Can I use this to monitor my site?
Not as a monitor. Each run is one request and the number of runs per minute is limited. An uptime monitor checks continuously from several places and alerts you.