HTTP Status Checker
Check what a URL returns from probes around the world: the HTTP status code, where a redirect points, and how long DNS, the TCP and TLS handshakes, the first byte and the download took.
How to Use
- Paste a URL such as https://github.com/, or just a host name (https:// is added). The path and query string are sent as typed.
- Pick the method: HEAD asks only for headers and is the polite default; GET also downloads the body (the first 10 KB is shown); OPTIONS asks what the server allows.
- Choose how many probes (3 to 10) and where, and HTTP/1.1 or HTTP/2.
- Press Run live check. Each probe’s status and timing appear as it finishes, usually in 2 to 5 seconds. Until then the page shows a recorded example.
- Click a row for its headers, certificate and a phase-by-phase explanation in Show Work. For a 3xx answer, Check the redirect target runs the next hop.
A live run uses 5 of the 250 free Globalping tests per hour for your IP address.
| # | Probe | Status | Total | DNS | TCP | TLS | First byte | Download | Server address |
|---|
Worked Example
HEAD https://github.com/ from five probes (recorded 6 October 2026). All five got 200 OK over TLS 1.3. Totals: Sydney 17 ms, São Paulo 28 ms, Tokyo 32 ms, Buffalo 79 ms, Helsinki 81 ms. Each probe was sent to a different server address, from 140.82.121.4 (Helsinki) to 4.237.22.38 (Sydney).
Splitting Helsinki’s 81 ms. DNS 3 + TCP 24 + TLS 27 + first byte 26 + download 1 = 81 ms. The TCP handshake is one round trip, so the server was about 24 ms away; TLS 1.3 needs about one more (27 ms) and the request itself one more. First byte minus the TCP round trip, 26 − 24 = 2 ms, is roughly the server’s own time. The response header x-github-edge-region: fra shows where it was served.
The common mistake: reading the total as server speed. Helsinki’s 81 ms looks almost five times slower than Sydney’s 17 ms, yet the server-time estimate is about the same: 2 ms for Helsinki and 6 − 3 = 3 ms for Sydney. The difference is distance (24 ms versus 3 ms per round trip), multiplied by the three round trips a fresh HTTPS request needs. A slow server shows up as a large first byte compared with TCP, as in Tokyo: 18 − 4 = 14 ms.
The certificate. github.com’s certificate was issued by Sectigo Public Server Authentication CA DV E36, valid from 1 September 2026 to 29 November 2026 23:59:59 UTC: 54 days left when the example was recorded.
Show Work
Timing Phases
HTTP Status Codes and Redirects
Where the codes come from. HTTP/1.0 (RFC 1945, May 1996) was the first RFC to define the three-digit status codes, and HTTP/1.1 (RFC 2068 in January 1997, RFC 2616 in June 1999, RFC 7231 in June 2014) refined it. Today’s definition is RFC 9110, HTTP Semantics (June 2022), which applies to HTTP/1.1, HTTP/2 and HTTP/3 alike. New codes are registered with IANA in the HTTP Status Code Registry, which is what the table below is built from.
The five classes (RFC 9110 §15). 1xx is an interim response before the final one. 2xx means the request was received, understood and accepted. 3xx means the client must take another step, usually following the Location header. 4xx means the client seems to have erred. 5xx means the server knows it has erred or cannot do what was asked. The reason phrase after the number (“OK”, “Not Found”) is only a suggestion; servers may send other text or none.
Redirects. A 3xx response names the new address in its Location header. These probes report each response as it is, without following it, so a chain such as http:// → https:// → www. shows one hop per check: use Check the redirect target to step through it. 308 Permanent Redirect, for permanent moves that must keep the method, was first defined in June 2014 (RFC 7238) and standardised in April 2015 (RFC 7538).
| Code | Name (IANA) | Meaning | Reference |
|---|---|---|---|
| 100 | Continue | The server has the request headers; the client should send the body. | RFC 9110 §15.2.1 |
| 101 | Switching Protocols | The server is switching to the protocol named in the Upgrade header, such as WebSocket. | RFC 9110 §15.2.2 |
| 102 | Processing | Interim reply: the server is still working on a long request (WebDAV). | RFC 2518 |
| 103 | Early Hints | Interim reply with header hints, such as Link preloads, before the final response. | RFC 8297 |
| 104 | Upload Resumption Supported (temporary) | Temporary registration for resumable uploads (expires 2026-11-13). | draft-ietf-httpbis-resumable-upload-05 |
| 200 | OK | The request succeeded. | RFC 9110 §15.3.1 |
| 201 | Created | A new resource was created; Location usually points to it. | RFC 9110 §15.3.2 |
| 202 | Accepted | Accepted for processing, but not finished. | RFC 9110 §15.3.3 |
| 203 | Non-Authoritative Information | A 200 response that a proxy has modified. | RFC 9110 §15.3.4 |
| 204 | No Content | Success, with no content in the response. | RFC 9110 §15.3.5 |
| 205 | Reset Content | Success; the client should reset the form or view it sent from. | RFC 9110 §15.3.6 |
| 206 | Partial Content | Only the byte range(s) the client asked for. | RFC 9110 §15.3.7 |
| 207 | Multi-Status | Several status codes for several resources, in an XML body (WebDAV). | RFC 4918 |
| 208 | Already Reported | Members already listed earlier in the same reply (WebDAV bindings). | RFC 5842 |
| 226 | IM Used | The server applied delta encoding to the resource (RFC 3229). | RFC 3229 |
| 300 | Multiple Choices | Several representations exist; the client picks one. | RFC 9110 §15.4.1 |
| 301 | Moved Permanently | Moved for good to the URI in Location. Clients may turn a POST into a GET. | RFC 9110 §15.4.2 |
| 302 | Found | Temporarily at the URI in Location. Clients may turn a POST into a GET. | RFC 9110 §15.4.3 |
| 303 | See Other | Fetch the URI in Location with GET to see the result. | RFC 9110 §15.4.4 |
| 304 | Not Modified | The cached copy is still valid (reply to a conditional request). | RFC 9110 §15.4.5 |
| 305 | Use Proxy | Deprecated: was used to send the client through a proxy. | RFC 9110 §15.4.6 |
| 306 | (Unused) | Unused; reserved. | RFC 9110 §15.4.7 |
| 307 | Temporary Redirect | Temporarily at the URI in Location; the method must not change. | RFC 9110 §15.4.8 |
| 308 | Permanent Redirect | Moved for good to the URI in Location; the method must not change. | RFC 9110 §15.4.9 |
| 400 | Bad Request | The server cannot process the request because it is malformed. | RFC 9110 §15.5.1 |
| 401 | Unauthorized | Authentication is needed; the WWW-Authenticate header says how. | RFC 9110 §15.5.2 |
| 402 | Payment Required | Reserved for future use. | RFC 9110 §15.5.3 |
| 403 | Forbidden | The server understood the request but refuses it. | RFC 9110 §15.5.4 |
| 404 | Not Found | Nothing found at this URI, or the server will not say whether there is. | RFC 9110 §15.5.5 |
| 405 | Method Not Allowed | This method is not allowed here; the Allow header lists the ones that are. | RFC 9110 §15.5.6 |
| 406 | Not Acceptable | No representation matches the request's Accept headers. | RFC 9110 §15.5.7 |
| 407 | Proxy Authentication Required | The client must authenticate with the proxy first. | RFC 9110 §15.5.8 |
| 408 | Request Timeout | The server gave up waiting for the complete request. | RFC 9110 §15.5.9 |
| 409 | Conflict | The request conflicts with the current state of the resource. | RFC 9110 §15.5.10 |
| 410 | Gone | Gone for good, deliberately. | RFC 9110 §15.5.11 |
| 411 | Length Required | A Content-Length header is required. | RFC 9110 §15.5.12 |
| 412 | Precondition Failed | A precondition in the request headers (If-Match and similar) was false. | RFC 9110 §15.5.13 |
| 413 | Content Too Large | The request body is larger than the server accepts. | RFC 9110 §15.5.14 |
| 414 | URI Too Long | The URI is longer than the server will process. | RFC 9110 §15.5.15 |
| 415 | Unsupported Media Type | The body's media type or encoding is not supported. | RFC 9110 §15.5.16 |
| 416 | Range Not Satisfiable | None of the requested byte ranges exist. | RFC 9110 §15.5.17 |
| 417 | Expectation Failed | The Expect header's expectation cannot be met. | RFC 9110 §15.5.18 |
| 418 | (Unused) | Unused; reserved. | RFC 9110 §15.5.19 |
| 421 | Misdirected Request | This server is not set up to answer for this host name or scheme. | RFC 9110 §15.5.20 |
| 422 | Unprocessable Content | The request is well-formed but its content cannot be processed. | RFC 9110 §15.5.21 |
| 423 | Locked | The resource is locked (WebDAV). | RFC 4918 |
| 424 | Failed Dependency | Failed because an earlier action it depended on failed (WebDAV). | RFC 4918 |
| 425 | Too Early | The server will not risk processing early (replayable) data. | RFC 8470 |
| 426 | Upgrade Required | The client must switch to the protocol named in the Upgrade header. | RFC 9110 §15.5.22 |
| 428 | Precondition Required | The server requires a conditional request. | RFC 6585 |
| 429 | Too Many Requests | Too many requests in a given time; Retry-After may say when to try again. | RFC 6585 |
| 431 | Request Header Fields Too Large | The header fields are too large. | RFC 6585 |
| 451 | Unavailable For Legal Reasons | Unavailable because of a legal demand. | RFC 7725 |
| 500 | Internal Server Error | The server hit an unexpected condition. | RFC 9110 §15.6.1 |
| 501 | Not Implemented | The server does not support the function (often the method) requested. | RFC 9110 §15.6.2 |
| 502 | Bad Gateway | A gateway or proxy got an invalid response from the server behind it. | RFC 9110 §15.6.3 |
| 503 | Service Unavailable | The server cannot handle the request now (overload or maintenance). | RFC 9110 §15.6.4 |
| 504 | Gateway Timeout | A gateway or proxy did not get a reply in time from the server behind it. | RFC 9110 §15.6.5 |
| 505 | HTTP Version Not Supported | The HTTP version used is not supported. | RFC 9110 §15.6.6 |
| 506 | Variant Also Negotiates | Content negotiation is misconfigured on the server. | RFC 2295 |
| 507 | Insufficient Storage | The server cannot store what is needed to finish (WebDAV). | RFC 4918 |
| 508 | Loop Detected | The server found an infinite loop (WebDAV bindings). | RFC 5842 |
| 510 | Not Extended (obsoleted) | Obsoleted; was for the HTTP Extension Framework. | RFC 2774 |
| 511 | Network Authentication Required | The client must log in to the network first, as with a captive portal. | RFC 6585 |
Source: IANA Hypertext Transfer Protocol (HTTP) Status Code Registry, downloaded 6 October 2026. Unassigned numbers are left out.
About This Tool
Reference: Internet Protocol History.
This HTTP status checker sends your URL to the Globalping network, a public set of probes run by jsDelivr, and shows what each probe received. You choose HEAD, GET or OPTIONS, HTTP/1.1 or HTTP/2, 3 to 10 probes and where they are (every continent, one continent, or a country, city, network or cloud region), and IPv4 or IPv6.
Each row gives the status code and name, the total time and its five phases, and the server address the probe reached. Click a row for the response headers, the TLS version, cipher and certificate (subject, issuer, validity, days left), the first part of the body for GET, and a Show Work breakdown; a 3xx row offers a one-click check of its Location. The bar chart compares the phases across probes.
Privacy: the request goes from your browser to api.globalping.io, not to this site, and only when you press Run; this site never fetches your URL. Private and local addresses are refused before anything is sent. Sources: RFC 9110, RFC 7538, RFC 8446, RFC 9293, RFC 1945, RFC 2616 (rfc-editor.org), the IANA HTTP Status Code Registry and the Globalping API specification for the timing definitions.
Related tools: HTTP Status Codes, Ping Test, and Open Port Checker.
Frequently Asked Questions
What do the HTTP status code classes mean?
The first digit is the class (RFC 9110 §15): 1xx informational, 2xx success, 3xx redirection (look at the Location header), 4xx client error (the request was wrong or not allowed, such as 404 Not Found or 403 Forbidden) and 5xx server error (500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable). The IANA registry has 64 entries, including two reserved as unused (306 and 418); the table on this page gives each one.
What is the difference between a 301, 302, 307 and 308 redirect?
301 and 308 say the move is permanent; 302 and 307 say it is temporary. The difference within each pair is the method: after a 301 or 302 a client may turn a POST into a GET, while 307 and 308 forbid changing the method (RFC 9110 §15.4). For moving a web page for good, 301 and 308 both work; 308 is newer, first defined in June 2014 (RFC 7238) and standardised in April 2015 (RFC 7538).
What are DNS, TCP, TLS, first byte and download times?
DNS is the name lookup. TCP is the handshake, about one round trip. TLS is the encryption handshake, about one more round trip with TLS 1.3 (RFC 8446). First byte runs from sending the request to the first byte of the reply: one more round trip plus the server’s own time. Download is the rest of the response. They add up to the total: from Helsinki, 3 + 24 + 27 + 26 + 1 = 81 ms.
Why does one region get a different status or speed?
Big sites answer from many places. In our example GitHub sent each probe to a different address, and the response header x-github-edge-region named fra for Helsinki and iad for Buffalo. Different sites can serve different redirects, blocks or cached copies. A 403 or 451 from one country only, or a 5xx from one region, points at that site rather than the whole service.
Is HEAD enough to check if a website is up?
Usually. RFC 9110 §9.3.2 says a HEAD response should carry the same headers as GET, just without the content, so the status code and redirects match. Some servers or firewalls treat HEAD differently, though; if HEAD gives 405 Method Not Allowed or 403, run the check again with GET.
Common Use Cases
Is the site down everywhere?
Five probes on five continents: 5 × 200 OK means it is up; failures from one region only point at a regional problem.
Check a redirect after a move
A site that moved to https:// should answer a plain http:// request with 301 or 308 and the https:// address in Location; step through the chain one hop at a time.
Find out why a page is slow
Split the total into phases: 81 ms from Helsinki was 24 ms TCP and 27 ms TLS of distance, and only about 2 ms of server time.
Watch a certificate expiry
Each HTTPS check shows the certificate’s issuer and end date; github.com’s had 54 days left on 6 October 2026.
Verify a CDN or geo setup
Different response addresses and edge-region headers per probe show which site serves each region.
Read response headers
See Server, Cache-Control, Strict-Transport-Security and Location from outside your own network.
Last updated: