Developer Tool
HTTP Status Checker
Check the HTTP status code of any URL, follow redirect chains and analyze response headers.
Redirect chain
Response headers
Bulk check
Checking…
HTTP Status Codes — Reference
2xx — Success
200
OK
The request succeeded. The response contains the requested content.
201
Created
Resource successfully created (POST/PUT).
204
No Content
Success, no content to return. Common for DELETE requests.
3xx — Redirects
301
Moved Permanently
Permanent redirect. SEO value is transferred to the new URL.
302
Found
Temporary redirect. SEO value is not transferred.
304
Not Modified
Resource hasn't changed since last access. Browser uses cached version.
307
Temporary Redirect
Temporary redirect that preserves the HTTP method.
308
Permanent Redirect
Permanent redirect that preserves the HTTP method.
4xx — Client errors
400
Bad Request
Malformed request. The server cannot process it.
401
Unauthorized
Authentication required to access this resource.
403
Forbidden
Access denied even with valid authentication.
404
Not Found
The requested resource does not exist on this server.
410
Gone
The resource existed but has been permanently deleted.
429
Too Many Requests
Too many requests — rate limit exceeded.
5xx — Server errors
500
Internal Server Error
Internal server error. Something went wrong on the server side.
502
Bad Gateway
Invalid response received from an upstream server (proxy, CDN).
503
Service Unavailable
Server temporarily unavailable (maintenance or overload).
504
Gateway Timeout
The upstream server didn't respond in time.
FAQ
301 is a permanent redirect: search engines transfer "link juice" to the new URL and update their index. 302 is temporary: SEO value stays on the original URL. Use 301 for site migrations and 302 for temporary redirects.
A redirect chain occurs when a URL redirects to another, which redirects to a third, and so on. Each hop slows down loading and dilutes SEO value. Ideally, your redirects should not exceed 1-2 hops.
403 means the resource exists but access is denied. 404 means it doesn't exist. From an SEO perspective, a 403 on a public page often indicates a server configuration issue or an overly restrictive robots.txt.