How to use Server Status Checker
- Enter the URL to testPaste a full public address starting with http:// or https:// into Public URL.
- Send the requestPress Run Server Status Checker. GigaTools sends HTTP HEAD requests, follows any redirects and waits up to 4 seconds for each answer.
- Read the final statusThe result shows the final status code and reason, for example 200 OK, with the final URL, the number of redirects and the total response time.
Common uses
- Confirming a page answers with 200 after a deployment
- Checking that an old URL returns 301 or 410 as intended
- Telling whether a site is down for everyone or only for you
Frequently asked questions
How do I use Server Status Checker?
1. Enter the URL to test: Paste a full public address starting with http:// or https:// into Public URL. 2. Send the request: Press Run Server Status Checker. GigaTools sends HTTP HEAD requests, follows any redirects and waits up to 4 seconds for each answer. 3. Read the final status: The result shows the final status code and reason, for example 200 OK, with the final URL, the number of redirects and the total response time.
What exactly does the tool report?
The status of the final response to a HEAD request, the URL it came from, how many redirects led there and the total response time. It does not keep an uptime history or look at the page content.
What happens if the URL redirects?
Redirects are followed, up to five, and every step is checked for a public address. The status shown is the final page’s. Use the HTTP Redirect Response Checker to see every step of the chain.
Why do I get 403 or 405 when the page works in my browser?
Some servers reject HEAD requests or block automated clients and unfamiliar user agents. The request comes from the GigaTools server with the user agent GigaTools/1.0, so firewalls or regional rules may treat it differently from your browser. If nothing arrives within 4 seconds, the tool says no response was received.
Is my URL stored?
No. The GigaTools server sends the request and returns the status line without saving the URL. Addresses that resolve to private or reserved networks are refused. Runs pass an automatic bot check and count toward a daily per-IP limit.