Skip to content

Uptime Check

Short answer

Check if a URL is up right now: HTTP status, response time, redirects, HTTPS, days left on the TLS certificate and key response headers.

What it does not do: It is one check, made from our servers when you click: nothing is scheduled, stored or alerted, so it does not replace an uptime monitor.

Free · No signup · Fetched by our server
We fetch the URL on our server to run the check. Results aren't saved.

What It Does

Requests your URL live, follows any redirects and reports the HTTP status, response time, whether the final address is HTTPS, how many days the TLS certificate has left, and the key response headers. It is a single on-demand check — nothing is scheduled, stored or alerted.

Why It Matters

When someone reports that your site is down, you need to know in seconds whether it is down for everyone. The same check warns you before a certificate expires — an expired certificate stops visitors with a browser warning and keeps crawlers away from your pages.

How It Works

  1. Enter the URL you want to check

  2. We request it live and follow redirects to the final address

  3. Measure the status code, response time and TLS certificate expiry

  4. Return a score with online, HTTPS, certificate and speed checks plus the key response headers

Sample input + output

INPUT
url: https://rankproof.eu
OUTPUT
Site is online and performing well.          100/100
  HTTP status: 200 (Online) · Response time: 23 ms
  HTTPS: Yes · SSL certificate: 84 days
  Site responds successfully                 OK
  Served over HTTPS                          OK
  Certificate not expiring soon              OK
  Fast response time                         OK
  Response headers:
    content-type: text/html
    cache-control: public, s-maxage=300, stale-while-revalidate=86400
    strict-transport-security: max-age=31536000; includeSubDomains; preload

How to read the result

HTTP status (200, Online)
The status of the final address after redirects. 200 to 399 counts as online; a 4xx or 5xx status, a timeout or a failed connection fails the check and the score is 0. We send a HEAD request, which asks for the headers without the page body.
Response time (23 ms)
How long the whole request took from our server, measured once. Under a second passes, one to three seconds is a warning and costs 10 points, three or more fails and costs 25. A visitor far away or on a phone network waits longer, so use it to spot a slow server, not as your page speed.
HTTPS (Yes)
Whether the final address is https://. A site that ends on plain HTTP loses 40 points and the certificate check fails.
SSL certificate (84 days)
Days until the certificate expires, read from the public Certificate Transparency logs, where every trusted certificate is recorded: the newest one covering the host. That is usually the one the site serves, but right after a renewal the site may still use the previous certificate for a while, so the figure can run ahead; the expiry date your browser shows is the final word. It warns at 30 days or fewer (12 points) and fails at 7 or fewer (30). "Unknown" means the logs did not answer in time; it costs 5 points and says nothing bad about the certificate.
Response headers
content-type, x-powered-by, cache-control and strict-transport-security when the server sends them, so you can see at a glance how the page is cached and whether HSTS is set.

Who Uses This

  • DevOps Engineer

    Confirm from outside your own network whether an outage is real or local before you escalate an incident.

  • Agency Owner

    Spot-check client sites after a hosting or DNS change and catch certificates that are close to expiry.

  • E-commerce Lead

    Check your checkout domains before a campaign launch; an expired certificate on a checkout page stops sales.

Common problems and how to fix them

  1. An error status although the page works in your browser

    Some servers and firewalls refuse HEAD requests (405) or automated requests (403). HTTP expects HEAD to answer like GET without the body, so allow it in the server or firewall settings.

  2. Slow response

    Most of the time is the server building the page. Cache the HTML where it rarely changes, check slow database queries and plugins, and use the page speed test to see the time to first byte from real visitors.

  3. The certificate expires soon

    Turn on automatic renewal and confirm it works; many certificates now last 90 days or less, so a manual renewal is easy to miss.

    # Certbot: confirm that automatic renewal works
    sudo certbot renew --dry-run
    
    # and that the timer which runs it is active
    systemctl list-timers | grep certbot
  4. The certificate shows as Unknown

    Check the expiry date yourself: click the padlock in the browser, or ask the server directly from a terminal.

    openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
      | openssl x509 -noout -enddate
    # notAfter=Jan 20 12:00:00 2027 GMT
  5. Not served over HTTPS

    Install a certificate and redirect every plain-HTTP request to HTTPS with a 301.

    # nginx
    server {
      listen 80;
      server_name example.com www.example.com;
      return 301 https://example.com$request_uri;
    }

Frequently Asked Questions

Does it monitor my site continuously?
No. It is a one-time live check that runs when you click. For round-the-clock monitoring with alerts, use a dedicated uptime service; use this check to confirm an outage or verify a fix.
Where is the check made from?
From our servers, not your browser, so the result reflects what an outside visitor gets rather than your local network or cache.
What counts as online?
A final response with a status between 200 and 399. A 4xx or 5xx status, a timeout or a connection failure fails the check.
When does the certificate check warn?
It warns at 30 days or fewer before expiry and fails at 7 days or fewer. Renew well before either threshold.

Sources

The documentation this tool and the explanations on this page are based on.