Status and reachability
Separate 2xx, 3xx, 4xx, 5xx and connection errors to learn whether the request reached a service and whether redirects, access control, rate limiting or server handling failed.
HTTP checker and troubleshooting guide
HTTP Status Checker & Website Speed Test
Enter a URL to test HTTP or HTTPS availability, status and request timing from multiple Vietnam probes. Separate DNS, connection, time to first byte, total time and regional differences before deciding whether to investigate the CDN, WAF or origin.
- Multi-probe HTTP checks in Vietnam
- Status and redirect diagnosis
- DNS / connect / TTFB / total time
Run an HTTP check now
Enter a full URL or domain. Active Vietnam probes will request it and the shared result page will compare status, DNS, connection, TTFB and total time.
This form uses the existing /api/test endpoint and shared result page; it does not create a separate test system.
What can an HTTP status check tell you?
Requesting the same URL from different networks turns “down or slow” into three actionable questions: response state, request-stage timing and regional consistency.
Request-stage timing
Compare DNS, connection, TTFB and total time. Slow TTFB points toward origin work, cache misses or origin routing; slow connection establishment points toward the network path or handshake.
Differences inside Vietnam
A failure on only some probes is often more useful than one average. Continue with ISP routing, CDN steering, WAF rules or country policy checks.
How to use the website response-time checker
1
Enter the exact URL
Use the affected URL, including HTTPS, path and query when relevant. A domain without a scheme defaults to HTTPS.
2
Request it from multiple probes
13CE creates one existing test job and active Vietnam probes request the same target without changing the origin.
3
Read status before timing
Classify success, redirect, client error or server error first; then compare DNS, connection, TTFB and total time.
4
Retest after a change
Record the affected probe, time and status. After a CDN, WAF or origin fix, use the same URL to confirm the difference is gone.
How to interpret HTTP test results
| Result | What it means | Next action |
|---|---|---|
| 2xx | The request was handled successfully, but content and performance can still be wrong. | Confirm the response content, TTFB, total time and cross-probe consistency. |
| 3xx | The client must follow a redirect, often for HTTPS or URL canonicalization. | Check Location, final destination, loops and excessive chains. |
| 4xx | The service was reached, but the path, permission, authentication, rate or policy was rejected. | Use the exact code to inspect the URL, authentication, WAF, country policy and limits. |
| 5xx | A CDN, gateway or origin failed to complete an apparently valid request. | Correlate the timestamp with CDN, proxy, application and upstream logs. |
| High TTFB, normal connection | The request connected but waited for its first byte, suggesting origin work, cache miss or slow origin path. | Review CDN cache hits, application/database time and origin resources. |
| Only some probes fail | The scope may be an ISP, route, CDN edge or regional access policy. | Keep the node-level evidence and compare DNS and Ping results. |
Common use cases
Post-deployment availability
Check the home page, sign-in route and important APIs after release to catch bad statuses, destinations or region-specific failures.
Slow access from Vietnam
Separate connection, TTFB and total time across Vietnam probes to identify network setup, origin processing or transfer delay.
CDN or WAF policy mistakes
If only certain probes receive 403, 429 or a different redirect, inspect country rules, IP reputation, bot protection and edge configuration.
HTTPS and canonical redirects
Verify apex, www, HTTP and HTTPS variants converge on one intended URL without loops, downgrades or unexpected cross-domain redirects.
Example: most probes return 200, a few return 403
The failing requests probably reached a CDN, WAF or origin access-control layer; this is different from a missing DNS answer.
Compare edge identifiers and headers between healthy and affected probes, then review country rules, allowlists and security policy. Use the DNS checker to see whether those probes were steered to another address, and retest the same URL after the fix.
Limits of this tool
13CE performs request-level HTTP diagnostics. It does not execute every script on the page and is not a Core Web Vitals browser test. A 200 result also does not prove that business content is correct; combine it with browser testing, application logs and monitoring.
HTTP checker FAQ
What is the difference between an HTTP check and a website speed test?
An HTTP check focuses on request success, status codes and request-stage timing. A website speed test focuses more broadly on perceived user experience. 13CE provides a useful availability and network-diagnostic view, but it is not a full browser rendering test.
Does HTTP 200 mean the website is fully healthy?
No. A 200 response only means this request received a successful class of response. Confirm the returned content, TTFB, total time and consistency across nodes.
Why does the site work locally but return 403 from Vietnam?
Common causes include WAF or CDN country policies, IP reputation rules, rate limits and origin allowlists. Compare the affected nodes with healthy nodes and inspect edge or origin controls.
Are 301 and 302 responses always a problem?
No. Redirects from HTTP to HTTPS or from an old URL to a canonical URL are normal. Investigate an incorrect destination, a loop or an unnecessarily long chain.
Can an HTTP check replace a real browser speed test?
Not completely. HTTP testing isolates DNS, connection, TTFB and total request time. Browser experience also depends on JavaScript, images, fonts, rendering and the user device.
Authoritative references
Use the IETF HTTP semantics standard and the IANA registry for status-code definitions.
Status looks normal but access is still slow?
Use Ping to check basic round-trip latency, or compare DNS answers to see whether regions are being sent to different addresses.