Every day we open websites, use mobile apps, watch videos, send messages, call APIs, and connect to cloud servers. The screen makes this look like a simple client-to-server interaction, but the real journey crosses several layers that each solve a different problem.
Networking Basics: How Requests Move Across the Internet
Domain name -> DNS -> IP address -> Router -> Internet -> Server network -> Application -> Database -> Response
Information is divided, wrapped with protocol details, carried in packets through networking devices, processed by an application, and returned through the same broad stack. Once this flow is clear, APIs, firewalls, load balancers, Kubernetes, VPNs, proxies, and distributed systems become easier to reason about.
Start With the Smallest Useful Model
The browser is a client. It asks a server-side application for a resource, the application processes that request, and a response comes back. At the HTTP layer that might be as simple as asking for /articles and receiving a 200 OK response containing HTML.
Browser -> Request -> Server processing -> Response -> Browser renders result
That model is correct but incomplete. Before HTTP can work, the device normally resolves a hostname, chooses a route, establishes transport communication, and—when HTTPS is used—creates an encrypted TLS session.
Each Layer Answers a Different Question
- DNS
- Which IP address currently represents this hostname?
- IP
- Which network destination should receive the packets?
- Port
- Which service at that destination should receive the traffic?
- TCP or UDP
- What transport behavior does the application need?
- TLS
- How can the endpoints protect and authenticate the communication?
- HTTP
- What action is being requested, and what does the response mean?
Keep Three Terms Separate
- Request
- An application action such as GET /products.
- Connection
- A communication relationship between endpoints, such as a TCP connection.
- Packet
- A network-layer unit carrying part of that communication.
One connection can carry many HTTP requests, and one request can require many packets. Treating those words as interchangeable makes debugging unnecessarily confusing.
The Final Networking Mental Model
The complete mental model
DNS finds an address, IP and routers move packets toward it, a port identifies the service, TCP or UDP transports data, TLS can protect it, and HTTP tells the application what the data means.
Complete Series
How Internet Requests Actually Work
An eight-part beginner series tracing internet communication from an HTTP request through DNS, IP, ports, transport protocols, packets, network devices, server infrastructure, security, and troubleshooting.
HTTP Requests: Methods, URLs, Headers, and Bodies
Start at the application layer and understand what a browser or API client is actually asking for.
DNS, Domain Names, and IP Addresses
Follow the lookup that turns a human-friendly hostname into a network destination.
Public IP, Private IP, NAT, and Ports
See how local devices reach the internet and how operating systems identify each service and flow.
TCP vs UDP
Compare reliable byte streams with simpler datagrams and understand where each transport fits.
Packets, Network Layers, Switches, and Routers
Learn how data is encapsulated and moved across local links and routed networks.
The Complete Website Request Journey
Put the layers together from the browser to production infrastructure and back again.
HTTPS, TLS, and HTTP Status Codes
Understand secure transport, certificate checks, and the response codes used during debugging.
Troubleshooting, Localhost, Cloud, and Containers
Apply the model with diagnostic tools and carry it into cloud and container environments.
Nikhlesh Yadav is a Technical Lead and Solution Architect with 12+ years of experience across cloud-native systems, distributed platforms, AI integrations, Web3, and cyber security.
Read full profile