Getting started

Trace the request path

Before changing a server, write down what should happen when a visitor enters the address. This creates a shared model and makes every test easier to interpret.

Working rule

A failed browser page is the final symptom, not the location of the fault.

Map the path

A typical HTTPS request crosses at least five boundaries. Your system may add a CDN, load balancer, reverse proxy, or service mesh, but the reasoning stays the same.

  1. Name resolutionThe client asks a resolver for the address associated with the hostname.
  2. Network connectionThe client opens a TCP connection to the returned address and port.
  3. TLS negotiationThe endpoint selects parameters and presents a certificate valid for the requested name.
  4. HTTP exchangeThe client sends a request; an HTTP server returns a status, headers, and an optional body.
  5. Application workThe origin may call other services before it can produce the response.

Check each layer

LayerQuestionUseful evidence
DNSDid the name resolve to the intended address?Record type, answer, TTL, resolver
TCPCould the client establish a connection?Connect result, latency, timeout or refusal
TLSDid the endpoint negotiate for the intended name?Certificate names, issuer, protocol, ALPN
HTTPWhich server handled the request?Status, response headers, redirect chain
OriginCould the application complete its work?Request ID, service logs, dependency health

Record evidence

For every test, keep the timestamp, client network, requested hostname, returned status, and exact result. Redact secrets, session cookies, private keys, and tokens before sharing logs.

Evidence is most useful when it is comparable. Repeat the same test after a change instead of switching tools and variables at the same time.

Know when to stop

If a test confirms that one layer works, move to the next boundary. If the result is ambiguous, improve the observation before editing production. A safe rollback is part of the test plan, not an afterthought.

Next guide

Start with DNS

Learn how to distinguish authoritative data from a cached resolver answer.

Read the DNS checklist