Step by step
The example above, written out — the same steps the animation plays.
- 1You type example.org. Computers find each other by IP address, not by name — so first the browser has to find example.org's IP.
- 2Not in the cache. The browser (and the operating system) have no saved answer for this name.
- 3Ask the resolver. The browser asks a DNS resolver — usually your ISP's, or one like 1.1.1.1 / 8.8.8.8.
- 4Resolver asks a root server. The resolver doesn't know either, so it starts at the top of DNS.
- 5Root: "ask .org". Root servers don't know every domain — only who runs each top-level domain like .org or .com.
- 6Resolver asks .org. Next stop: the servers for .org.
- 7.org: "ask its nameserver". .org knows which nameserver is responsible for example.org.
- 8Resolver asks the domain's nameserver. This server is the authority: it holds the domain's records.
- 9The answer. The A record: example.org is at 203.0.113.10. The TTL says how long anyone may cache it.
- 10Back to the browser. The resolver caches the answer too, so the next person asking gets it instantly.
- 11TCP: SYN. Now the browser opens a TCP connection to the IP: "can we talk?"
- 12TCP: SYN-ACK. The server agrees: "yes, let's talk".
- 13TCP: connected. The browser acknowledges, and can send data straight after. One round trip so far.
- 14TLS: hello. HTTPS: the browser proposes encryption settings and sends its half of a key exchange.
…and 6 more steps — press Play above to watch them all.
What's happening?
- DNS: the browser asks a resolver, which asks a root server, then the .org servers, then the domain's own nameserver for its IP address.
- TCP opens a connection to that IP; TLS proves the server's identity with a certificate and sets up encryption.
- HTTP asks for the page; the HTML leads to more requests for CSS, JavaScript and images, and then the page is drawn.
Where you'll meet it
This is the classic interview question, and the reason CDNs, DNS caching, keep-alive connections and TLS 1.3 exist: most of the wait is round trips.
Common mistake
Thinking DNS is one lookup at "the DNS server". It is a chain of servers — and every answer is cached for its TTL, which is why DNS changes take time to spread.
FAQ
What does a DNS resolver do?
It does the lookup on your behalf — asking root, top-level-domain and authoritative servers in turn — and caches the answer.
Why is a repeat visit faster?
The IP address is cached, so DNS is skipped, and the browser usually has CSS, JavaScript and images cached too.
What does HTTPS add?
A TLS handshake: the server proves who it is with a certificate, and both sides agree a key so nobody in between can read or change the traffic.
Are these times real?
They are typical round-trip times for illustration. Real ones depend on distance, network and caching.