HTTP check

Does the site answer, with what status, and where does the time go?

Tested from around the worldPlain English + technicalFree, no sign-up

How to read the results

The bar splits the request into DNS, connect, TLS and waiting for the server.
A long “server” segment means slow back-end code or database.

Check everything at once

The health check runs this and 30 more checks on a domain, then ranks what to fix.

More in Website and HTTP

Is it down?Is a website down for everyone or just you?
Geoblock checkerSee which countries can open a URL and which are blocked.
Redirect tracerTrace every redirect from first URL to final page.
Security headersGrade a site’s security headers from A to F.
Website speedTime a page load and weigh its assets.
HTTP/2, HTTP/3, IPv6 supportCheck HTTP/2, HTTP/3 and IPv6 support.
What’s that site running?See every technology a website runs: CDN, host, CMS, scripts and trackers.
robots.txt, sitemap, llms.txtCheck robots.txt, sitemap, llms.txt and security.txt.
Sitemap inspectorValidate a sitemap, follow its index and spot risks.
Meta tag / link checkerPreview search and social cards, find broken links.

About the HTTP check

Load a URL from our probes and see the status code, IP, protocol and a timing breakdown: DNS, connect, TLS and time to first byte.

Every result comes in two styles: plain English for everyone, and the exact technical detail for engineers, with the raw JSON one click away.

Questions

Time to first byte: from starting the request to the first byte of the reply. Under 600 ms is good.