Web ownership & practical systems

HTTP Status Codes for Troubleshooting

Lesson 7 of 25

When a browser, crawler, app or other client requests a web resource, the server returns an HTTP response.

One part of that response is a status code.

That number is one of the fastest troubleshooting clues available.

200 OK

The request succeeded and the server returned a normal successful response.

If the page looks wrong while returning 200, the problem may be inside the content or application rather than basic HTTP availability.

301 Moved Permanently

The requested resource has been assigned a permanent new location.

Permanent redirects are commonly used when URLs or domains change.

302 Found

The server is redirecting the request, normally without declaring the move permanent.

Temporary and permanent redirects should be chosen intentionally.

304 Not Modified

The server indicates that the client can continue using its cached representation under the applicable cache conditions.

This is not the same thing as a blank response or broken page.

400 Bad Request

The server considers the request malformed or invalid.

Look at what was actually sent before assuming the application itself is down.

401 Unauthorized

Authentication is required or the supplied authentication did not satisfy the request.

Despite the English label, this code is primarily associated with authentication.

403 Forbidden

The server understood the request but refuses to provide the requested access.

Permissions, access rules, security controls and application authorization are possible areas to inspect.

404 Not Found

The server cannot find the requested resource at that location.

Check the URL, route, file, content record and rewrite behavior.

410 Gone

The resource is intentionally no longer available.

This can communicate a stronger removal decision than an ordinary missing resource.

429 Too Many Requests

The client has exceeded a request limit.

Look for rate limiting, excessive automation, loops or unusually high request volume.

500 Internal Server Error

The server encountered an unexpected condition while handling the request.

Application errors and server logs are important evidence here.

502 Bad Gateway

A gateway or proxy received an invalid response from an upstream service.

The visible web server may be alive while the service behind it is not responding correctly.

503 Service Unavailable

The service is temporarily unable to handle the request.

Maintenance, overload or an unavailable dependency can produce this result.

Read before changing

The status code does not always tell you the exact cause.

It tells you where to begin looking.

Record the URL, status, time and visible error before changing the system. That evidence can save a long troubleshooting session.

Put This Lesson to Work

Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.

Worked example

For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.

Your finished result

A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.

Check your understanding

  • Can you explain the main idea without repeating a slogan?
  • What evidence or example supports your explanation?
  • Which decision will you make differently, and why?
Open the matching worksheet
WRUnity logo

Welcome to WRUnity

One free SpiderTaz Network account works across every network site.