Check HTTP status codes for any URL.
HTTP Status Checker requests a URL from our server and reports the real status code (200, 301, 404, 500...), the final address after redirects, response time, SSL certificate details and the key response headers. Because the request comes from a server, it works for any public site, unlike checks run inside a browser.
Made for developers. Typical uses:
Only public http and https addresses on standard ports can be checked, with a few checks per minute. Some sites block automated requests and answer 403 or 429.
Accuracy: Output is tested against known inputs. For production code, review the result and run your own tests.
A step-by-step way to find out why a site is down or misbehaving: check DNS records, then the HTTP status code and redirect chain, then domain expiry and your own IP.
Explore more in Developer Tools, read the guides and articles, or see how we test our tools.
Check HTTP response headers for any URL.
Best for auditing a site's security headers (CSP, X-Frame-Options, HSTS) after a server configuration change
Check URL redirects and redirect chains.
Best for auditing a site's redirects for SEO after a domain migration
Check website status and HTTP response codes.
Best for confirming whether a website outage is real or a problem on your end
Look up DNS records for any domain.
Best for verifying MX records are set up correctly after configuring email
Check domain registration details.
Best for checking when a domain is due to expire before it lapses
Parse user agent strings to identify browser, OS, device, and version.
Best for decoding a user agent string from server logs to see which browser is causing errors
Test REST APIs with visual interface.
Best for quickly testing an API endpoint without installing a full API client