What the 1xx, 2xx, 3xx, 4xx, and 5xx Filters Mean on HTTP Status Dogs

Updated

HTTP Status Dogs groups every HTTP response status code into five classes, and the numbers you see in its filter bar — 1xx, 2xx, 3xx, 4xx, 5xx — are those classes. The first digit tells you who is responsible for the response and what kind of outcome it represents: informational, success, redirection, client error, or server error. Selecting a class on the site narrows the list to every code in that range, which is faster than searching one code at a time when you only know the general category you're dealing with.

The five classes at a glance

Filter Class name First digit means Typical use
1xx Informational Request received, still processing Interim responses during protocol handling
2xx Success Request understood and accepted Normal successful page loads and API calls
3xx Redirection Further action needed to complete the request Redirects, caching, moved resources
4xx Client error The request itself is the problem Bad URLs, missing auth, malformed input
5xx Server error The server failed to fulfil a valid request Backend crashes, timeouts, upstream failures

The class is only a category, not a single code. Each filter contains multiple individual status codes, which is why picking 4xx returns a set of results rather than one page.

How to use the filters

  1. Open the site and find the filter row containing All, 1xx, 2xx, 3xx, 4xx, and 5xx.
  2. Select a class to restrict the listing to that range. Choose All to see every code again.
  3. If you already know part of the code or its name, type it into the search field instead — the filters and the search box work together.
  4. If nothing matches, the site shows "No dogs found." with a prompt to try another code or name, or to clear your filters.

That empty state is the main thing to watch for: it usually means your filter and your search term disagree — for example, a 2xx filter combined with a search for a 404 code — rather than the site being broken.

What each class tells you in practice

1xx — Informational

The server has received the request and is telling the client to keep waiting. These are rare in day-to-day browsing and mostly appear in lower-level protocol exchanges.

2xx — Success

The request worked. When a page loads normally or an API call returns data, you're in this class.

3xx — Redirection

The resource isn't at the address you requested, and the response tells the client where to go next. This is the class behind URL redirects and cache-related behaviour.

4xx — Client error

Something about the request is wrong: a mistyped URL, missing credentials, or invalid input. The server is reachable but won't accept what was sent.

5xx — Server error

The request was valid, but the server couldn't complete it. These point at the server side, not the caller.

When to filter by class instead of searching

Use a class filter when you know the symptom but not the exact number — for instance, "the page just won't load and it's clearly my URL" points at 4xx, while "the whole site is down for everyone" points at 5xx. Use the search box when you already have the specific code or name in hand. Combining both is useful for confirming that a code you're thinking of really belongs to the class you expect.