Status code
See the response code returned directly by the URL. Redirect responses remain visible instead of being hidden behind the final destination.
HTTP Status Checker
Check a URL's HTTP status code, response time, resolved IP, content type and key response headers.
Result
Check the HTTP status a URL returns right now
The HTTP Status Checker makes a lightweight server-side request to the public URL you enter and reports the response without following redirects. That makes it useful for seeing whether a URL itself returns 200, 301, 302, 404, 403, a 5xx error or another HTTP status.
Response time
Measure how long this diagnostic request takes from the Smart Web Utility server environment. Use it for troubleshooting and comparison, not as a Core Web Vitals score.
Resolved IP
See the public IP used for the request. This can help after DNS, CDN, proxy or hosting changes.
Content and redirect details
Review content type plus useful headers such as Server and Location when the endpoint returns them.
HTTP status code groups
2xx responses indicate successful HTTP processing. 3xx responses indicate redirection. 4xx responses indicate that the requested resource cannot be served as requested, such as 404 Not Found or 403 Forbidden. 5xx responses indicate a server or upstream failure.
Common status checks for website operations and SEO
200 OK
Expected for many healthy, directly accessible pages and API endpoints. A 200 response still does not guarantee that the body contains the correct content.
301 or 308 redirect
Common for permanent URL moves, canonical hostname changes and HTTP-to-HTTPS routing. Use the Redirect Checker to inspect the full chain.
404 or 410
Appropriate for genuinely removed or missing resources. Investigate when an important page or internal link unexpectedly returns one of these statuses.
500, 502, 503 or 504
These often point to application errors, unavailable upstream services, overloaded servers, proxy failures or maintenance conditions.
Why a browser can behave differently
Responses may vary by cookies, authentication, user agent, geography, CDN routing, bot protection and request headers. This checker reports what its server-side request receives. For a logged-in or personalized browser session, compare the result with your browser developer tools.
Response time is not a page-speed score
The timing reported here covers this diagnostic request. It does not measure rendering, Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift or other real-user experience metrics. Use it to spot obvious server-response differences rather than to judge complete frontend performance.
Related website tools
Frequently asked HTTP status questions
Is every 404 response bad?
No. A missing resource should normally return a proper not-found response. The problem is when a page that should exist, or a URL still used by internal links and external users, returns 404 unintentionally.
What is the difference between 301 and 302?
Both are redirects, but they communicate different intent: 301 is generally used for a permanent move, while 302 is generally used for a temporary redirect. Other redirect codes such as 307 and 308 preserve request-method semantics differently.
Why does this tool show 301 while my browser opens the page normally?
Your browser follows redirects automatically. This checker deliberately exposes the first response so you can see that redirect instead of silently landing on the destination.
Does a 200 response mean a page is indexable?
No. Indexability also depends on factors such as robots directives, canonicalization, crawl access and the content itself.