~/devtools / http-status
tool::http-status

HTTP
상태 코드

1xx부터 5xx까지 모든 HTTP 상태 코드를 카테고리별로 탐색하고 검색합니다.

ad · 728×90
61 / 61
Continue
Client should continue with the request.
1xx
Switching Protocols
Server is switching protocols as requested.
1xx
Processing
Server has received the request but has not yet completed it.
1xx
Early Hints
Used to preload resources while the server is still processing.
1xx
OK
The request has succeeded.
2xx
Created
The request has been fulfilled and a new resource has been created.
2xx
Accepted
The request has been accepted but not yet acted upon.
2xx
Non-Authoritative Information
The response is from a transforming proxy, not the origin server.
2xx
No Content
The server successfully processed the request but returns no content.
2xx
Reset Content
The server processed the request; the client should reset the document view.
2xx
Partial Content
The server is returning partial content due to a Range header.
2xx
Multi-Status
Multiple status codes for multiple independent operations (WebDAV).
2xx
Already Reported
Members of a DAV binding have already been enumerated.
2xx
IM Used
The server fulfilled the request using instance manipulations.
2xx
Multiple Choices
Multiple options for the requested resource.
3xx
Moved Permanently
The resource has permanently moved to a new URL.
3xx
Found
The resource is temporarily at a different URL.
3xx
See Other
Redirect to another resource using GET.
3xx
Not Modified
The cached version is still valid; no new content to return.
3xx
Temporary Redirect
Temporary redirect preserving the original HTTP method.
3xx
Permanent Redirect
Permanent redirect preserving the original HTTP method.
3xx
Bad Request
The server could not understand the request due to invalid syntax.
4xx
Unauthorized
Authentication is required and has failed or not been provided.
4xx
Payment Required
Reserved for future use; some services use it for payment walls.
4xx
Forbidden
The server refuses to fulfill the request (authenticated but unauthorized).
4xx
Not Found
The requested resource could not be found.
4xx
Method Not Allowed
The HTTP method is not supported for this resource.
4xx
Not Acceptable
No content matching the Accept headers is available.
4xx
Proxy Authentication Required
Authentication with a proxy is required.
4xx
Request Timeout
The server timed out waiting for the request.
4xx
Conflict
The request conflicts with the current state of the server.
4xx
Gone
The resource has been permanently deleted and will not return.
4xx
Length Required
The Content-Length header is required but not provided.
4xx
Precondition Failed
One or more conditions in the request headers evaluated to false.
4xx
Content Too Large
The request body exceeds the server's size limit.
4xx
URI Too Long
The request URI is longer than the server can process.
4xx
Unsupported Media Type
The media type of the request is not supported.
4xx
Range Not Satisfiable
The range specified in the Range header cannot be fulfilled.
4xx
Expectation Failed
The expectation in the Expect header cannot be met.
4xx
I'm a Teapot
The server refuses to brew coffee; it is a teapot (RFC 2324).
4xx
Misdirected Request
The request was directed at a server unable to produce a response.
4xx
Unprocessable Content
The request is well-formed but contains semantic errors.
4xx
Locked
The resource being accessed is locked (WebDAV).
4xx
Failed Dependency
The request failed because a previous request failed (WebDAV).
4xx
Too Early
The server is unwilling to process a potentially replayed request.
4xx
Upgrade Required
The client should switch to a different protocol.
4xx
Precondition Required
The server requires the request to be conditional.
4xx
Too Many Requests
The user has sent too many requests in a given time (rate limiting).
4xx
Request Header Fields Too Large
Request headers are too large for the server to process.
4xx
Unavailable For Legal Reasons
The resource is unavailable due to legal restrictions.
4xx
Internal Server Error
The server encountered an unexpected condition.
5xx
Not Implemented
The server does not support the requested functionality.
5xx
Bad Gateway
The gateway received an invalid response from an upstream server.
5xx
Service Unavailable
The server is temporarily unable to handle the request.
5xx
Gateway Timeout
The gateway did not receive a timely response from an upstream server.
5xx
HTTP Version Not Supported
The HTTP version used in the request is not supported.
5xx
Variant Also Negotiates
A circular reference in transparent content negotiation.
5xx
Insufficient Storage
The server is unable to store the representation (WebDAV).
5xx
Loop Detected
An infinite loop was detected while processing the request (WebDAV).
5xx
Not Extended
Further extensions to the request are required.
5xx
Network Authentication Required
Network authentication is required before accessing resources.
5xx
ad · 300×250
// about this tool

HTTP 상태 코드에 대해

HTTP 상태 코드는 클라이언트의 요청에 대한 서버의 응답 결과를 세 자리 숫자로 표현합니다. 첫 번째 자리는 응답의 분류를 나타냅니다: 1xx는 정보, 2xx는 성공, 3xx는 리다이렉션, 4xx는 클라이언트 오류, 5xx는 서버 오류입니다. 이 코드 체계는 HTTP/1.0(RFC 1945, 1996)에서 도입되어 현재 HTTP/2, HTTP/3까지 이어집니다.

실무에서 가장 자주 마주치는 코드는 200(OK), 201(Created), 301(Moved Permanently), 302(Found), 400(Bad Request), 401(Unauthorized), 403(Forbidden), 404(Not Found), 500(Internal Server Error)입니다. 특히 401과 403의 차이—인증 실패 vs 인가 거부—나 301과 302의 차이—영구 vs 임시 리다이렉트—는 API 설계와 SEO에 직접 영향을 줍니다.

이 도구는 1xx~5xx의 표준 HTTP 상태 코드 전체를 카테고리 탭으로 탐색하고, 코드 번호나 이름으로 즉시 검색할 수 있습니다. 코드 번호를 클릭하면 클립보드에 복사됩니다. REST API 설계, 서버 디버깅, 웹 개발 학습에 빠른 레퍼런스로 활용하세요.

주요 사용 사례
  • ▸낯선 HTTP 상태 코드의 정확한 의미 조회
  • ▸REST API 설계 시 올바른 상태 코드 선택
  • ▸서버나 서드파티 API의 HTTP 오류 디버깅
  • ▸리다이렉트 코드 올바른 사용 확인 (301 vs 302 vs 307 vs 308)
  • ▸인증 오류 구분 (401 vs 403)
자주 묻는 질문
Q. 401과 403의 차이는 무엇인가요?
401 Unauthorized는 '인증(Authentication)이 필요하거나 실패했다'는 의미입니다. 아직 누구인지 모른다는 뜻입니다. 403 Forbidden은 '인증은 됐지만 이 리소스에 접근할 권한이 없다(Authorization 실패)'는 의미입니다. 이미 누구인지는 알지만 허락하지 않는 것입니다.
Q. 301과 302 리다이렉트의 차이는?
301 Moved Permanently는 영구 이동을 의미하며 검색엔진이 링크 주스를 새 URL로 옮깁니다. 302 Found는 임시 이동으로 검색엔진은 원본 URL을 계속 인덱싱합니다. 307과 308은 각각 302, 301과 같지만 리다이렉트 시 HTTP 메서드를 변경하지 않습니다.
Q. 418 I'm a Teapot은 실제로 사용되나요?
RFC 2324 만우절 농담으로 만들어진 코드지만, IANA 레지스트리에 등록되어 있습니다. 실제 API에서 커피 관련 엔드포인트에 장난처럼 쓰이거나, 특정 요청을 거부할 때 유머로 사용되기도 합니다. 공식 스펙상 실제 서비스에 사용하도록 권장되지는 않습니다.