Web Server Test Check Server Response Time From Multiple Locations
Check whether your web server is up and how fast it responds. This free web server test sends an HTTP or HTTPS request from locations around the world and times every phase, from DNS lookup to the last byte.
At a glance
- Server response time: DNS, connect, TLS, time to first byte (TTFB), download and total time for each location.
- Availability: the HTTP status code, final URL, redirect chain and response headers.
- Any HTTP method: GET, HEAD, POST, PUT, PATCH, DELETE and OPTIONS, with custom headers, a request body (up to 64 KB) and Basic Auth.
- Content check: verify that the response contains a given text, to catch error pages that still return 200 OK.
- TLS check: certificate, chain, host name and expiry date; an invalid certificate is reported as an error.
- Global: test from up to 3 locations at once without an account.
- Free: no sign-up required; results export as PDF, CSV and JSON.
How to check server response time
- Enter the URL, for example
https://www.example.com/or an API endpoint. - Optionally choose the HTTP method and add headers, a request body or credentials.
- Select up to three locations.
- Click Run Test. Each location opens a new connection and reports the timing of every phase.
What the web server test measures
| Phase | What it means | What a high value usually indicates |
|---|---|---|
| DNS | Resolving the host name to an IP address | Slow or distant DNS provider |
| Connect | Opening the TCP connection | Distance to the server or network congestion |
| TLS | Negotiating HTTPS | Distance, or a slow or overloaded server |
| Time to first byte (TTFB) | The server's processing time before it starts answering | Slow application code, database or missing cache |
| Download | Transferring the response body | Large response or limited bandwidth |
A good server response time (TTFB) is under 200 ms for static or cached content and under 800 ms for dynamic pages. Compare locations: if TTFB is high everywhere, the server itself is slow; if only connect and TLS are high in one region, the problem is distance or routing.
Is the website down for everyone or just me?
Run the web server test from several locations. If every location gets an error, such as a timeout, a connection refused or a 5xx status code, the site is down for everyone. If the test locations succeed but you can't reach the site, the problem is on your side: your network, ISP, DNS cache or firewall. If only some locations fail, look for a regional network or CDN problem with the Traceroute Test.
HTTP status codes and what they mean
- 2xx (200 OK): the server answered successfully.
- 3xx (301, 302, 307, 308): a redirect. The test follows up to 10 redirects and shows the chain.
- 4xx (401, 403, 404): the request was refused or the page doesn't exist. Check the URL, credentials and access rules.
- 5xx (500, 502, 503, 504): the server or a proxy in front of it failed. Check the application, upstream servers and load balancer.
Any 4xx or 5xx response, an invalid certificate or a missing expected text is shown as an error for that location.
Test APIs and protected pages
The web server test works for REST APIs and webhooks as well as web pages. Send a POST, PUT or PATCH request with a JSON or form body, add an Authorization header or Basic Auth, and require a text such as "status":"ok" in the response. Credentials and header values are encrypted at rest and masked on shared results.
Related free tools
- Website Speed Test: load the whole page in a real browser with a waterfall.
- Ping Test: check if the server answers ICMP and measure latency.
- DNS Trace Test: check your DNS records and delegation.
To monitor your server's uptime and response time 24/7 with alerts, see Dotcom-Monitor.
Frequently asked questions
What is server response time?
Server response time is the time from sending a request until the first byte of the response arrives, also called time to first byte (TTFB). It includes the server's processing time and one network round trip. Google recommends keeping TTFB under 0.8 seconds.
How do I check if a website is down?
Run this web server test from several locations. If all locations report a timeout, connection error or 5xx status, the site is down for everyone. If they succeed, the problem is local to your network.
What is a good server response time?
Under 200 ms is excellent and typical of cached or static content. Under 800 ms is acceptable for dynamic pages. Above 1 second, visitors notice the delay and page speed metrics such as LCP suffer.
Can I test an API endpoint?
Yes. Choose the HTTP method, add headers such as Authorization or Content-Type, enter a request body, and optionally require a text in the response. The test reports the status code, headers, timing and whether the expected text was found.
Does the test follow redirects?
Yes, by default it follows up to 10 redirects and shows each hop. Turn off "Follow redirects" to test the first response only. Headers and credentials are only sent to the original host.
What is the difference between the Web Server Test and the Website Speed Test?
The Web Server Test sends one HTTP request and times the server's answer. The Website Speed Test loads the whole page in Chrome, including images, scripts and third parties, and measures what the visitor experiences.
Which protocols does the test use?
HTTP/1.1 over plain HTTP or HTTPS, on a fresh connection from each location, so connection and TLS setup are always included in the timing.
Last updated: