You open your browser, type youtube.com into the search bar, and press Enter. Within seconds, the homepage appears, ready for you to search, browse, or stream a video. It feels like one simple, almost instantaneous action.
But what actually happens between pressing Enter and seeing YouTube appear on your screen?
Behind that simple keystroke, your device performs a series of complex operations. It needs to find where YouTube is located on the internet, establish secure communication, prepare your request for transmission, send it across multiple networks, and process the response when it arrives back on your device.
To make sense of this complexity, network engineers use a conceptual framework called the OSI (Open Systems Interconnection) Model. It divides network communication into seven layers, with each layer representing a different set of responsibilities.
The internet does not always follow these seven layers as separate steps. However, the OSI Model is still a useful way to understand how data travels across a network. Real-world internet protocols often combine or distribute these functions across a simpler TCP/IP architecture. Still, the OSI Model provides a useful mental map for understanding what happens when data travels across a network.
So, let’s see what happens when you connect to YouTube and how the request gets there and back.
Following the Request: Layers 7 to 3
Layer 7 — Application:
Your browser is where the journey begins. When you type youtube.com and press Enter, the browser needs to turn your action into a network request. But your computer cannot route data using a human-readable name like “youtube.com.” It needs an IP address.
This is where the Domain Name System (DNS) comes in. Think of DNS as the internet's phonebook. You remember a website using a name such as youtube.com, while computers use numerical IP addresses to identify destinations. DNS helps translate the domain name into an IP address so your device can begin communicating with the appropriate infrastructure.
Layer 6 — Presentation:
Now the data needs to be represented and protected. In the traditional OSI Model, the Presentation Layer handles data formatting, transformation, compression, and encryption.
When your browser connects to YouTube using HTTPS, Transport Layer Security (TLS) helps protect the communication. Encryption makes it difficult for someone intercepting the connection to read the information being exchanged.
Think of it like placing a message inside a locked envelope before sending it. The message can still reach its destination, but someone who intercepts it should not be able to simply read what's inside.
In modern internet communication, however, encryption does not neatly belong to one isolated OSI layer. TLS and other protocols operate across the real-world networking stack in ways that don't map perfectly onto the traditional seven-layer model.
Layer 5 — Session:
The Session Layer is conceptually responsible for establishing, managing, and terminating communication sessions between applications.
Your device may be handling several network conversations at once. You could have YouTube open while receiving messages, browsing another website, and running another application in the background. The Session Layer provides a way of understanding how these different communication sessions can be managed.
Modern networking doesn't necessarily have one standalone protocol operating as a dedicated Session Layer. Many of these functions are distributed across other protocols and application mechanisms.
Layer 4 — Transport:
Now the request needs a way to move between your device and its destination.
The Transport Layer is concerned with end-to-end communication. Depending on the protocol being used, it can help manage delivery, ordering, error recovery, flow control, and other aspects of transporting data.
Two of the best-known transport protocols are TCP and UDP.
TCP (Transmission Control Protocol) is designed for reliable, ordered delivery. It keeps track of transmitted data and uses acknowledgements and retransmission mechanisms to help ensure information arrives correctly.
UDP (User Datagram Protocol) takes a lighter approach. It is connectionless and provides fewer built-in mechanisms for guaranteeing delivery or ordering. This makes it useful when low overhead and latency are important, particularly when an application can tolerate some data loss or manage reliability itself.
Modern web applications such as YouTube can also use QUIC, which forms the foundation of HTTP/3. QUIC runs over UDP but adds features such as reliable delivery, connection management, encryption, and stream handling. This allows modern applications to benefit from UDP's lightweight foundation while still having mechanisms for reliable communication.
Layer 3 — Network:
Now the data needs to find its way across the internet.
The Network Layer handles logical addressing and routing. IP packets contain information about their source and destination, while routers examine this information and make forwarding decisions about where the packets should go next.
Your home router may send the traffic toward your Internet Service Provider (ISP). From there, the data can pass through multiple interconnected networks and routers before reaching the infrastructure responsible for handling the request.
The exact route can vary depending on network configuration, routing decisions, connectivity, and other factors.
Think of it as a road trip. Your data is the traveller, the destination IP address identifies where it needs to go, and routers act like junctions that determine which road the traveller should take next.
The Physical Side: Layers 2 and 1
Layers 7 through 3 help us understand much of the software and routing side of the journey. But the data still needs a way to physically move.
Layer 2 — Data Link:
This layer handles communication across a local network.
It takes Network Layer packets and encapsulates them into frames for transmission using technologies such as Wi-Fi and Ethernet. When your laptop sends data to your home router over Wi-Fi, Layer 2 helps manage that local connection.
Layer 1 — Physical:
At the bottom is the Physical Layer. This is where digital information becomes physical signals capable of travelling through a medium. Those signals might be electrical signals through copper cables, pulses of light through fibre-optic cables, or radio waves travelling through the air.
So, What Happened When You Pressed Enter?
When you typed youtube.com and pressed Enter, a simplified version of the journey looks like this:
1. You enter youtube.com. Your browser interprets your request.
2. DNS helps find the destination. The domain name is resolved to an appropriate IP address.
3. Secure communication is established. Protocols such as TLS help protect the connection.
4. The data is prepared for transport. Transport protocols manage how information is exchanged.
5. Packets are addressed and routed. IP and routers help move the data across networks.
6. The request reaches YouTube's infrastructure. The servers process the request and prepare a response.
7. The response travels back. Data makes its way across networks toward your device.
8. Your browser processes the response. The information is interpreted and the YouTube page appears on your screen.
All of that happens very quickly.
Why the OSI Model Matters
The OSI Model is more than just a theory. It helps network engineers understand how communication works and find problems when a network is not working properly.
If a website won't load, an engineer can work through the layers systematically. Is there a physical connection? Is the device connected to Wi-Fi? Does it have a valid IP address? Is DNS resolving the website correctly? Is the transport connection working? Or is the problem actually with the application?
By breaking a complicated system into smaller responsibilities, the OSI Model gives engineers a mental map for finding problems instead of guessing blindly.
When you type youtube.com, you're doing one simple thing: opening a website. But behind that action is a complex network of applications, protocols, routers, cables, wireless signals, and servers working together.
The OSI Model helps us understand that hidden journey.
So, the next time you press Enter and a website appears almost instantly, remember that a complex network of technologies is working behind the scenes to move information from your device across the internet and back again.
