Website Status & Uptime Checker

HTTP 200 OK indicates that the client request was successfully received, understood, and processed by the server, and the requested web page or payload has been returned.

A 301 Moved Permanently status signifies that the requested resource has been permanently relocated to a new URL, instructing search engines to transfer link equity and browsers to cache the new destination. A 302 Found (or 307 Temporary Redirect) indicates a temporary shift, meaning search engines should retain the original URL in search indices.

4xx status codes (such as 400 Bad Request, 401 Unauthorized, 403 Forbidden, and 404 Not Found) denote client-side errors, meaning the request was invalid or lacked permissions. 5xx status codes (like 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout) denote server-side failures, meaning the server crashed, timed out, or could not reach an upstream application process.

Under Google Core Web Vitals guidelines, a server response time (Time to First Byte / TTFB) of under 200ms to 300ms is considered excellent. Response times between 300ms and 800ms are acceptable, while anything above 800ms typically leads to noticeable page load delays and higher bounce rates.

Every redirect hop adds DNS lookup, TCP handshake, TLS negotiation, and HTTP round-trip latency. A chain of 3 to 4 redirects can easily add 500ms to 1000ms of delay on mobile connections. Furthermore, search engine crawlers may abandon crawling a URL if a redirect chain exceeds 5 hops.

While this web tool provides on-demand single checks, Uzvera's commercial monitoring service continuously pings your websites and API endpoints at regular intervals (e.g. every 60 seconds). If your server goes down, responds with a 5xx error, or exceeds your latency threshold, alerts are dispatched immediately via email, Slack webhooks, and push notifications.