Free Website Uptime & Latency Checker

Check Your Website Uptime in Seconds

Enter any URL to instantly see if it's up, how fast it responds, its HTTP status code, and where it redirects. No signup required.

Uptime Check Terms Explained

A plain-language guide to every result and header shown in your uptime check.

UP / DOWN

The overall result of the check. UP means the website answered with a working response. DOWN means it did not respond, timed out, or returned an error code such as 500 or 503.

HTTP status code

A three-digit number the server sends back with every response to say what happened. 2xx means success, 3xx means redirect, 4xx means a problem with the request (such as a missing page), and 5xx means the server itself failed.

Example200 = OK, 301 = Moved permanently, 404 = Not found, 500 = Internal server error, 503 = Service unavailable.

What is HTTP 200 (OK)?

HTTP 200 means the request succeeded and the server returned the page or data that was asked for. It is the response you want to see for a healthy website or API.

Checked at

The exact date and time the check ran, taken from the server's response, in GMT. It tells you how fresh the result is.

Checked from

The city and country of the monitoring server that ran the check. Latency, TTFB, and DNS times are measured from this location, so a site can be fast from one country and slow, or even blocked, from another.

Example"Checked from: Frankfurt am Main, Hesse, Germany" means the request was sent from our server in Frankfurt.

Latency

The total time for the whole request to finish, measured in milliseconds (ms): DNS lookup, connecting, the SSL handshake, waiting for the server, and downloading the response. Lower is better.

ExampleUnder 300 ms feels fast, 300-700 ms is acceptable, and over 700 ms starts to feel slow to visitors.

TTFB (Time to First Byte)

The time from sending the request until the first byte of the response arrives. It shows how quickly your server starts answering. A high TTFB usually points to slow backend code, database queries, or an overloaded server.

ExampleLatency 140 ms with TTFB 123 ms means most of the time was spent waiting for the server; the download itself took only about 17 ms.

DNS lookup

The time spent turning the domain name (www.example.com) into the server's IP address. This has to happen before the browser can connect. A few milliseconds is normal; hundreds of milliseconds suggests a slow DNS provider.

Anycast IP

An IP address that is announced from many data centers at once, so each visitor is routed to the nearest one. CDNs and DNS providers such as Cloudflare use Anycast to make lookups and connections faster.

SSL certificate

SSL (Secure Sockets Layer, today TLS) is what makes a site load over https:// with a padlock. "Valid" means the certificate is trusted, matches the domain, and has not expired. The number in brackets is how many days remain before it expires.

Example"Valid (32 days)" means the certificate works today and must be renewed within 32 days, or visitors will see a security warning.

Raw HTTP response headers

Extra information the server sends along with the page, such as the content type, caching rules, and which server or proxy handled the request. They are useful for debugging caching, CDN, and configuration problems.

content-type

Tells the browser what kind of data is being sent and how it is encoded.

Example"text/html; charset=utf-8" means an HTML web page in UTF-8 text encoding.

cache-control

Rules for whether and how long browsers and CDNs may store a copy of the response.

Example"no-store, max-age=0" means never cache it and always fetch a fresh copy. "public, max-age=3600" means anyone may cache it for one hour.

server / via / x-powered-by

Identify the software involved in serving the response. "server" is the web server (e.g. nginx), "via" lists proxies the response passed through (e.g. "1.1 Caddy"), and "x-powered-by" names the framework (e.g. Express or Next.js).

cf-ray / cf-cache-status

Headers added when the site is behind Cloudflare. cf-ray is a unique ID for the request, useful when contacting Cloudflare support. cf-cache-status shows whether the response came from Cloudflare's cache (HIT) or from your server (MISS).

date

The time the server generated the response, in GMT. If it is far off from the real time, the server clock is wrong, which can break SSL and authentication.