You use the internet constantly and it mostly feels like magic. It isn't — it's a stack of agreed protocols, each handling one job, layered so that loading a web page quietly relies on all of them working together. Understanding the stack demystifies networking and underpins network security.
Layers: divide and conquer
The internet works by splitting the problem into layers, each with one responsibility, stacked so each relies on the one below. The TCP/IP model is the practical version: the link layer moves bits between adjacent devices, the internet layer routes across networks, the transport layer manages end-to-end delivery, and the application layer is what your software speaks. You can understand one layer without mastering the others — that's the point.
IP: addressing and routing
The Internet Protocol (IP) gives every device an address and gets packets (small chunks of data) from source to destination across many intermediate routers. IP is 'best effort' — it doesn't guarantee delivery or order; it just forwards packets toward their address, hop by hop.
Data doesn't travel as a stream — it's chopped into packets, routed independently, and reassembled at the other end. Almost everything follows from that.
TCP vs. UDP: two ways to deliver
- TCP adds reliability on top of IP — it ensures packets arrive, in order, retransmitting what's lost. Used where correctness matters: web pages, email, file transfers.
- UDP skips those guarantees for speed and low latency. Used where being fast beats being perfect: live video, voice, gaming.
DNS and HTTP: the everyday protocols
DNS is the internet's phone book — it translates a name like shamirgeorge.com into the IP address machines actually route to. HTTP/HTTPS is the language of the web — how your browser requests a page and the server responds, with HTTPS adding encryption so the conversation can't be read or tampered with in transit.
Why it matters for security
Network security is, in large part, understanding these protocols well enough to know how they're attacked and defended — spoofed addresses, intercepted traffic, manipulated DNS, unencrypted channels. You can't secure a network whose mechanics you don't understand.
Understand the network
My Mastering Internet Protocols course walks the layered model, IP, TCP/UDP, DNS, and HTTP/HTTPS — the protocols behind everything online, explained without the jargon.
View the course →Questions
What's the difference between TCP and UDP?
TCP guarantees reliable, ordered delivery (web, email, files); UDP trades those guarantees for speed and low latency (live video, voice, gaming).
What does DNS do?
It translates human-readable names (like a website address) into the numeric IP addresses computers use to route traffic — the internet's phone book.