The OSI Model can feel theoretical in the classroom. But it describes something that happens billions of times every second all around you. Let's trace a real request — from the moment you press Enter in your browser to the moment the webpage loads — and see every OSI layer in action.
The Scenario: Visiting a Website
You type https://example.com in your browser and press Enter. Here is exactly what happens at each OSI layer:
Layer 7 — Application: DNS + HTTP
First, your browser needs to resolve example.com to an IP address. It sends a DNS query (Layer 7, Application) to your configured DNS server. The response provides the IP: 93.184.216.34.
Now your browser creates an HTTPS GET request — another Layer 7 action — requesting the root document from that IP.
Layer 6 — Presentation: TLS Handshake
Because the URL starts with https://, your browser initiates a TLS handshake. Certificates are exchanged and verified, a cipher suite is negotiated, and a shared session key is established. All subsequent HTTP data will be encrypted — invisible to anyone monitoring the network path.
Layer 5 — Session: Connection Management
The Session Layer manages the ongoing connection, maintaining state between your browser and the server for the duration of your visit. When you navigate to another page on the same site, the session remains active — you don't re-authenticate or re-handshake.
Layer 4 — Transport: TCP Segments
Your HTTPS request is handed to TCP, which assigns a source port (e.g., 49523) and uses destination port 443 (HTTPS). The data is segmented if needed. TCP's three-way handshake has already established the connection. Each segment is numbered for ordered reassembly.
Layer 3 — Network: IP Routing
Each TCP segment is wrapped in an IP packet. Your device's IP (e.g., 192.168.1.5) is the source. The server's IP (93.184.216.34) is the destination. Your router reads the destination IP and routes the packet toward the internet — which may involve 15–30 intermediate routers, each making independent routing decisions at Layer 3.
Layer 2 — Data Link: Frame Delivery
On each network segment (your home LAN, your ISP's network, each internet exchange), the packet is wrapped in a Frame with appropriate MAC addresses for that segment. As the packet crosses from one network to another at routers, the frame is stripped and recreated with new MAC addresses for the next hop.
Layer 1 — Physical: Bits on Wire
Your home network likely uses Ethernet (to your router) and then whatever your ISP uses. For most users this is a combination of copper, fiber, and possibly cellular — all Physical Layer concerns. The bits travel as electrical signals, light pulses, or radio waves.
The Return Journey
The server receives your request, processes it, and sends back the webpage data — following the exact same layered process in reverse. Your browser's network stack performs de-encapsulation: bits → frame → packet → segment → data → HTTP response → rendered webpage.
All of this happens in under 100 milliseconds for a well-optimized website.
See this entire journey visualized in the OSI Model Simulator — it's the most powerful way to make this abstract process concrete.
Top comments (0)