What Actually Happens When You Type a Web Address Into Your Browser

Step 1 — The DNS Lookup: Translating a Name Into an Address

The moment you press Enter after typing a web address, your browser's first job is to figure out where on the internet that address lives. Domain names like example.com are easy for people to remember, but computers communicate using numerical IP addresses — strings of numbers like 93.184.216.34.

To make the translation, your browser contacts a DNS (Domain Name System) resolver — usually one run by your Internet Service Provider, though you can configure your own. The resolver checks its cache for a recent answer. If it doesn't have one, it queries a chain of DNS servers until it gets the correct IP address, then hands it back to your browser.

This lookup typically takes anywhere from a few milliseconds to around 100ms. Your home router often caches DNS results locally to speed things up on repeat visits.

Step 2 — Making the Connection: TCP and the TLS Handshake

Armed with the IP address, your browser opens a connection to the web server using TCP (Transmission Control Protocol). TCP is a reliable communication standard that breaks data into packets and makes sure they all arrive correctly. Establishing a TCP connection requires a brief back-and-forth exchange called a three-way handshake — three small messages between your device and the server to confirm both sides are ready.

For secure sites (those using HTTPS, indicated by a padlock in your address bar), an additional step runs immediately after: the TLS handshake. This exchange negotiates encryption keys so that all data sent between you and the server is scrambled from anyone trying to intercept it. This is what protects your passwords, credit card numbers, and private messages in transit.

Step 3 — The Request and Response: Fetching the Page

With a secure connection established, your browser sends an HTTP request to the server — essentially asking, "Please send me the content for this page." The server processes that request, locates the relevant files, and sends back an HTTP response.

That response includes a status code (the familiar 200 OK means success; 404 Not Found means the page doesn't exist) and the actual content: usually an HTML file that describes the page's structure. Your browser begins reading that HTML immediately.

As it reads, the browser discovers additional resources it needs — images, stylesheets, JavaScript files — and fires off new requests for each one. Modern browsers download many of these in parallel, which is one reason high-speed connections feel snappier. A complex page might require dozens of individual requests before it fully renders.

Step 4 — Rendering: Turning Code Into a Visual Page

Once your browser has the HTML, CSS (styling instructions), and JavaScript (interactive behavior), it begins rendering — converting those raw code files into the visual layout you see on screen. The browser builds two internal models: the DOM (Document Object Model, representing page structure) and the CSSOM (CSS Object Model, representing visual styles). These combine to produce a final "render tree" that the browser paints onto your display.

JavaScript can modify the page dynamically — loading new content, responding to clicks, or personalizing elements — which is why some pages continue to change slightly after they first appear. If your computer is under heavy load during this stage, rendering can stall. Background processes competing for resources are a common reason pages feel sluggish even on a fast connection.