Blog / How the internet works /
What TCP/IP means, in plain words
TCP/IP is the set of rules that lets your phone, a server in another country and the router in your house understand each other. It’s the language underneath the web, email and nearly everything else online.
You’ll never type it into anything, which is why it’s easy to ignore. But it explains a lot of everyday things: why a page sometimes loads slowly, what an IP address is, why a connection drops, and how a site can be “up” but unreachable. Let’s go through it without the jargon.
Two names, two jobs
The name is two protocols bolted together:
- IP (Internet Protocol) handles addressing and routing: where something is going.
- TCP (Transmission Control Protocol) handles reliability: making sure everything arrives, intact and in order.
A protocol is just an agreed set of rules. Computers from different companies and countries can talk because they all follow the same ones.
The postal analogy
Imagine you want to send someone a long book, but the post only accepts small envelopes.
- You tear the book into pages and put each page in its own envelope.
- You number the pages so they can be reassembled.
- You write the address of the recipient and your own return address on each envelope.
- The postal system routes each envelope independently. They might take different paths and arrive out of order.
- The recipient sorts them by number, notices if one is missing, and asks you to resend it.
- They put the book back together.
In this picture, IP is the addressing and delivery system. TCP is you and the recipient numbering the pages, checking nothing is lost and asking for a resend.
IP: addresses and routing
Every device on a network has an IP address, a number that identifies it. You’ve seen them: something like 192.168.1.5, or longer ones with letters and colons.
IPv4 and IPv6
- IPv4 uses four numbers (for example
203.0.113.10). It allows roughly 4.3 billion addresses, which sounded like plenty and ran short as billions of devices came online. - IPv6 uses much longer addresses with letters and numbers. It provides a vastly larger number, enough that running out is not a practical concern.
Both are in use at once, and many networks support both.
Packets
Data on the internet doesn’t travel in one piece. It’s split into small chunks called packets. Each carries a piece of the data plus a header with the sender’s address, the destination address and some control information.
Routers
Routers are the sorting offices. Each looks at the destination address on a packet and decides which direction to send it next. A packet might pass through a dozen or more routers on its way, with no single device knowing the whole path.
Where DNS fits
People remember names, not numbers. DNS translates a name like example.com into an IP address, so your device knows where to send the packets. It’s the address book that sits alongside TCP/IP.
TCP: making it reliable
IP alone is “best effort”. It tries to deliver packets, but doesn’t promise they all arrive, or in order. Packets can be lost, delayed or duplicated.
TCP adds the reliability layer on top.
The handshake
Before sending data, two devices set up a connection with a three-step exchange:
- Your device says, “I’d like to connect.” (SYN)
- The server replies, “Okay, I’m ready.” (SYN-ACK)
- Your device confirms, “Great, let’s go.” (ACK)
It’s the equivalent of a phone call starting with “Hello? Can you hear me?” “Yes, I can hear you.” “Good.”
Numbering and acknowledgements
TCP numbers the chunks of data it sends. The receiver confirms what has arrived. If something goes missing, the sender notices the gap and sends it again.
Flow control
TCP also watches how fast data is being sent. If the network or the receiver is struggling, it slows down. Many connection speed problems come from this adjustment.
Ports
An IP address gets data to the right device. A port gets it to the right application on that device. Think of the address as a building and the port as the office door. Websites over HTTPS use port 443, and plain HTTP uses port 80. Email and other services have their own.
UDP, the other option
TCP isn’t the only choice. UDP is a lighter protocol that skips the handshake, the numbering and the resends. It’s faster but less reliable.
That trade-off suits things where a late packet is useless, such as live video calls, voice and online games. A slightly glitchy frame matters less than a delay. Newer web protocols such as HTTP/3 are built on a UDP-based transport called QUIC, which adds its own reliability. I touched on that in HTTP/2, HTTP/3 and CDNs: what site owners need to know.
Where the web sits
TCP/IP is often described in layers, each doing one job and relying on the one below:
| Layer | Job | Examples |
|---|---|---|
| Application | What the user’s software does | HTTP, email, DNS |
| Transport | Reliable (or fast) delivery | TCP, UDP |
| Internet | Addressing and routing | IP |
| Link | Moving bits across one connection | Wi-Fi, Ethernet, mobile networks |
When you open a web page, your browser (application) asks DNS for the address, TCP opens a connection, IP carries the packets across routers, and Wi-Fi or mobile data carries each hop.
Why this matters to a normal person
- It explains “the internet is slow”. Slow can mean packets are being lost and resent, a congested path, or a weak Wi-Fi signal, not simply low speed.
- It explains why your IP address isn’t your name. It can change, and many people share one on the same network.
- It explains why a VPN or a different network can fix a problem. You’re changing the route the packets take.
Why it matters if you run a website
Server and connection settings
Hosting, firewalls and CDNs work at this level. A firewall rule blocking a port can make a service unreachable while the website itself is fine.
Latency
Each new connection takes a few round trips before data flows: the handshake, then an encryption setup for HTTPS. The further apart the visitor and the server, the more time that adds. This is why a CDN, which puts content closer to the visitor, helps, and why hosting location can matter.
Troubleshooting
Terms like “connection timed out”, “connection refused” and “DNS failure” start to make sense:
- Timed out: packets are going out but nothing is coming back. Often a firewall, a down server or a routing problem.
- Refused: the server was reached but nothing was listening on that port.
- DNS failure: the name couldn’t be turned into an address.
Knowing which one you’re seeing narrows the search quickly.
Security
Open ports are doors. A server should only expose the ones it needs.
Common myths
- “The internet is a cloud.” It’s cables, routers and servers, physically located somewhere.
- “An IP address is a precise location.” It usually points to a network or a provider, not a house.
- “TCP/IP is a single program.” It’s a family of agreed rules, built into every operating system.
- “Faster internet means everything loads faster.” Latency and packet loss often matter as much as bandwidth.
Key takeaways
- IP handles addressing and routing; TCP handles reliable, ordered delivery.
- Data travels in packets, passing through many routers.
- DNS turns names into IP addresses; ports direct traffic to the right application.
- UDP trades reliability for speed, and suits live media.
- Understanding the basics makes errors and slowness easier to diagnose.
Related reading
When a page fails to load, do you know whether it’s DNS, the connection or the server? Next time, try to work out which.