Server Response Code & HTTP Header Checker
Inspect HTTP status codes (200, 301, 403, 404, 500, 503), analyze full server response headers, and measure latency.
Understanding HTTP Status Codes & Server Response Headers
What This Tool Actually Checks
This tool sends a single live HTTP request to the URL you provide, using redirect: 'manual' so it captures the exact first-hop response instead of silently following any redirect chain. It records the numeric status code (e.g. 200, 301, 403, 500), the server's status text, the full set of returned response headers, and the round-trip latency in milliseconds measured from request start to response completion.
Each recognized status code is paired with a plain-English explanation of what it means at the protocol level, plus a specific note on how that status affects search engine crawling and indexing — because how Googlebot treats a 301 versus a 404 versus a 503 during a maintenance window can materially change your organic visibility.
How to Use It
- Paste the exact URL you want to inspect, including the path if you're testing a specific page rather than the homepage.
- Click Check Response. The request runs server-side with a 10-second timeout.
- Read the large status code at the top — the color coding follows the standard convention (green for 2xx success, cyan for 3xx redirects, amber for 4xx client errors, red for 5xx server errors).
- Check the response time in milliseconds next to the status code — this is raw server latency, not a full page load metric.
- Scroll through the full headers list to inspect caching directives, server software disclosure, and security headers returned alongside the status.
How HTTP Status Codes Are Grouped
HTTP status codes are grouped into 5 classes by their first digit. 1xx codes are informational and rarely seen directly. 2xx codes (200 OK being the most common) confirm the request succeeded. 3xx codes indicate redirection — 301 is permanent and passes link equity, 302 and 307 are temporary and do not. 4xx codes mean the client's request was faulty or unauthorized (401 needs credentials, 403 is a hard denial, 404 means the resource doesn't exist, 410 means it's permanently gone). 5xx codes mean the server itself failed to fulfill a valid request (500 is a generic crash, 502 means an upstream proxy got an invalid response, 503 means temporary overload).
Response headers carry equally important metadata: Cache-Control and ETag govern how browsers and CDNs cache the response, Content-Type tells the browser how to render the payload, and security-relevant headers like Strict-Transport-Security or X-Frame-Options can be reviewed in more depth with our Security Headers Checker.
Worked Example
Suppose you check https://example.com/old-blog-post/ after a site redesign and get back:
- Status:
301 Moved Permanently - Response time:
142 ms - Location header:
/blog/old-blog-post-new-slug/
Interpretation: the page was intentionally moved and correctly configured with a permanent redirect, so any existing backlinks or search rankings pointing at the old URL will transfer to the new one over time. Compare this to receiving 404 Not Found instead — that would mean the redirect rule was never created, and both the visitor and any accumulated SEO value for that URL are simply lost.
Practical Use Cases
- Post-deploy smoke testing: Developers hit key URLs immediately after a release to confirm they return 200 rather than an unexpected 500 from a broken plugin update.
- Redirect map validation: Agencies migrating a site verify every entry in their old-URL-to-new-URL redirect map actually returns 301 (not 302 or 404) before decommissioning the old server.
- Maintenance window verification: Site owners confirm their maintenance page correctly returns 503 with a Retry-After header rather than 200, which would risk Google indexing the "Down for Maintenance" page itself.
- Header debugging during CDN setup: When placing a WordPress site behind Cloudflare or another CDN, this tool helps confirm that caching and security headers are being added or preserved as expected at the edge.
Common Mistakes & Limitations
- Confusing 302 with 301: Many WordPress redirect plugins default to 302 (temporary), which does not consolidate SEO signals the way a 301 does. Always verify the actual code returned, not just that "the redirect works" in a browser.
- Single-request snapshot: A 200 response right now does not guarantee the endpoint is stable under load — intermittent 502/504 errors caused by PHP worker exhaustion may not appear in a single low-traffic test.
- Custom status codes on some hosts: A minority of WAFs or CDNs return non-standard codes for blocked requests (e.g. Cloudflare's 1020), which this tool will display as a generic status without a built-in explanation.
- Response time is server latency, not full page load: The measured duration reflects only the initial byte response, not the time to render CSS, JavaScript, or images — use a Core Web Vitals tool for full-page performance analysis.
Frequently Asked Questions
What is the difference between HTTP 301 and 302 redirects for SEO?
301 is a permanent redirect that transfers 100% of link equity and signals search engines to update their canonical index. 302 is a temporary redirect that instructs search engines to keep the original URL indexed.
How does a 503 status code protect SEO during scheduled maintenance?
Returning a 503 Service Unavailable (with a Retry-After header) informs Googlebot that the outage is temporary. Google will not de-index pages or penalize search rankings during the maintenance window.
What causes 502 Bad Gateway and 504 Gateway Timeout errors in WordPress?
A 502 occurs when the reverse proxy (Nginx / Cloudflare) receives an invalid response from PHP-FPM. A 504 occurs when PHP workers are exhausted and a script takes longer than the timeout limit (e.g. 60 seconds) to execute.
Does this tool enforce SSRF security checks?
Yes. All live audits enforce strict SSRF safeguards, blocking requests to private networks, loopbacks, and cloud metadata IPs.
Why does this tool use redirect: "manual" instead of following redirects automatically?
Following redirects automatically would hide the very first status code returned by the server, which is exactly what you need to see when debugging a redirect chain. By capturing the immediate response manually, the tool reports the true first-hop status code (e.g. 301, 302, 307) instead of silently jumping to the final destination.
What is the difference between a 401 and a 403 status code?
401 Unauthorized means the request lacks valid authentication credentials and the server is asking the client to supply them. 403 Forbidden means the server understood who is making the request but has decided to deny access regardless — commonly triggered by a WAF rule, IP block, or incorrect file permissions rather than a login prompt.
Why do I sometimes see a 304 Not Modified response?
304 is returned when a client sends conditional headers (If-Modified-Since or If-None-Match) and the resource has not changed since the cached copy was last fetched. It has no response body, saving bandwidth. It is not an error — it is the caching layer working as intended.
Can this tool diagnose why my WordPress site is intermittently returning 502 or 504 errors?
It can confirm that the error is occurring and show you the exact status code and response time at the moment of the test, but intermittent gateway errors are usually caused by PHP-FPM worker exhaustion or slow database queries under load, which requires server-side log analysis (slow query log, PHP-FPM status page) rather than a single external HTTP request to fully diagnose.