Why does the checker show a different result than my browser?

Browsers send cookies, Accept headers and cached responses. This tool makes a clean, cookie-less request, so what you see is closer to what a search-engine bot or a fresh visitor would get.

The site loads for me but returns 403 here — why?

Some firewalls block datacenter IPs or non-browser user agents. A 403 from the checker with a working browser often means bot protection, not a broken site.

Can I follow a redirect chain with it?

The tool reports the final status and headers after the server-side request completes, so permanent and temporary redirects are already resolved — check the response headers to see where you landed.

HTTP status checker — Guide

Check the live HTTP status code and response headers of a URL to troubleshoot reachability, redirects and caching.

What it is and when to use it

Check a live URL and see the actual HTTP status code and response headers it returns right now — useful to tell "the site is down" from "the site redirects", to verify a cache purge, or to confirm a security header actually ships in production. Requests run through the DigDevBox API, so the result reflects a server-side fetch, not your local cache.

Checks from the server side what HTTP status code and response headers a URL actually returns, to confirm what is really served in production.

How to use it

Enter the URL (https is assumed when no scheme is given)
Click check status or press enter
Read the colour-coded status and the response header list, which can be copied as a whole

A worked example

Fill in a sample URL

example.com

Copy this into the tool, or open HTTP status checker

Things that trip people up

The check runs from this site's server, so you see the result from the server's network environment, which may differ from a local curl (DNS cache, proxy, regional differences)
The site must be deployed; local development requests will fail
Status codes are coloured green for 2xx, orange for 3xx and red for 4xx / 5xx

Questions people ask

Why does the checker show a different result than my browser?: Browsers send cookies, Accept headers and cached responses. This tool makes a clean, cookie-less request, so what you see is closer to what a search-engine bot or a fresh visitor would get.
The site loads for me but returns 403 here — why?: Some firewalls block datacenter IPs or non-browser user agents. A 403 from the checker with a working browser often means bot protection, not a broken site.
Can I follow a redirect chain with it?: The tool reports the final status and headers after the server-side request completes, so permanent and temporary redirects are already resolved — check the response headers to see where you landed.

Next steps

Open the HTTP status checker tool

Spotted something wrong on this page? Tell us via Contact Us