HTTP response behavior
HTTP checks show whether a page or API returns successfully, which status code is returned, whether redirects happen, and whether response headers differ across probes.
Methodology
How 13CE measures website speed, DNS, TCP reachability, and latency from Vietnam
13CE is designed to answer a practical question: how does a website, CDN, API, or domain behave when it is checked from Vietnam and related network paths? This methodology explains what each test measures, what it does not prove by itself, and how to turn results into the next troubleshooting step.
- Explains HTTP, DNS, TCP, and latency signals
- Clarifies what Vietnam probe results can and cannot prove
- Helps turn test output into a practical diagnosis
What does 13CE measure?
DNS answers
DNS checks show where a hostname points from different networks or resolvers. They help reveal inconsistent records, stale cache, traffic steering, or resolver-specific behavior.
TCP reachability
TCP checks focus on whether a port can be reached and how quickly a connection can be established. This is useful when HTTP fails before a full application response is available.
Latency and path quality
Latency checks help separate normal distance from abnormal degradation. Comparing regions can show whether slowness is broad, local, or tied to a specific network path.
How should results be interpreted?
1
Start with the symptom
If users cannot open the site, start with HTTP and TCP. If users land on different IPs, start with DNS. If the site works but feels slow, start with latency.
2
Compare regions and paths
Look for patterns across Vietnam probes and related paths. A problem that appears only in one region is different from a problem that appears everywhere.
3
Check whether DNS explains the route
If probes resolve to different IPs or CNAMEs, HTTP and latency differences may be caused by traffic steering rather than the application itself.
4
Confirm with the next test
Use the next guide to confirm the hypothesis: HTTP for status and headers, DNS for answer selection, latency for path quality, and resolver checks for public DNS versus ISP DNS behavior.
What can Vietnam probe results prove?
They can reveal regional behavior
If Vietnam probes consistently return different status codes, DNS answers, or latency than other paths, that is a useful sign of regional routing, CDN, resolver, or upstream differences.
They cannot represent every real user
No probe network represents every device, ISP, or last-mile condition. Use 13CE to narrow the problem, then confirm with logs, monitoring, CDN data, or user reports when needed.
Where should you go next?
If you are investigating a real incident, start with the guide closest to the symptom: HTTP for access failures, DNS for inconsistent targets, latency for slow access, and resolver comparison for public DNS versus ISP DNS differences.