How This Page Reached You

A live tour of how the web actually works, narrated by your own session. Every number below is real and measured from this visit. Nothing is stored.

The short story: what happens when you open a web page

Typing an address and pressing Enter kicks off a sequence that usually finishes in well under a second:

  1. DNS lookup — the domain name (like cleanosint.com) is just a label. Your computer asks a DNS resolver to translate it into an IP address, the actual number that identifies the server on the internet.
  2. TCP connect — your browser opens a connection to that IP. A quick back-and-forth (the "three-way handshake") establishes a reliable channel.
  3. TLS handshake — because the site is HTTPS, the browser and server agree on encryption keys. After this, everything is scrambled so nobody in between (your ISP, a coffee-shop wifi) can read or change it.
  4. The request — the browser sends an HTTP request: a method (GET), a path, and a stack of headers describing itself. The "waiting" time is the server building the response.
  5. The response — bytes come back: a status code (200 OK), response headers, and the page content.
  6. Render — the browser parses the HTML, runs scripts, and paints the page you're reading.

An API call (like the live demo above) is the same thing without the rendering step: a program asks a server for data and gets structured JSON back instead of a web page.

Privacy note: everything here is information every site you visit can already see. We read it from your own session and never store it. Your IP's full value is never logged by our backend, only its leading segment.