How the Internet Moves Your Data
"Running the Internet without IP addresses would be a little like running the postal service without mailing addresses."
— Dr. Tahseen Al-Doori, Cyber Security Essentials, Chapter 3, p. 13
Where you are: Unit II — How the Digital World Works · Lesson 2.1 · This lesson follows Chapter 3 of Dr. Al-Doori's Cyber Security Essentials.
Unit II is about how things work before we study how they are attacked. Every threat later in this course abuses something you will learn here, so a clear picture now saves confusion later. We start with the Internet itself.
What you'll be able to do
Describe how data crosses the Internet using protocols and IP addresses, and explain why an IP address is not a person.
- Explain what an Internet service provider (ISP) does and why computers need protocols to talk.
- Describe, in plain words, how a message is split into packets and routed to its destination.
- Explain why the public IP address a website sees usually stands for a shared connection, not one person or one device.
A network of networks
Imagine an office before the Internet existed. Several colleagues need the same files, so someone copies them onto disks and walks them from desk to desk. That works until a colleague is in another building, or another country. The obvious fix is to connect the computers so they can share data directly. That connected group is a network.
The Internet is what you get when you connect huge numbers of those networks to each other. Dr. Al-Doori describes it as a network of networks, and that is still the best short definition. Your home network, your university's network and a video service's network are separate networks that agree to pass data to one another.
Somebody has to own the cables, fibre and equipment that join those networks. That job falls mainly to Internet service providers (ISPs): the broadband or mobile company you pay for your connection, plus the larger carriers behind them. Your ISP is your on-ramp to everyone else's network.
Protocols: rules computers can't bend
People cope with unclear instructions. We ask a question or make a sensible guess. Computers can't. They need fixed, unambiguous rules for every exchange. A set of such rules is called a protocol.
The protocol that ties the whole Internet together is the Internet Protocol (IP). Its central idea is the IP address: a number that tells the network where a piece of data should go and where the reply should come back to. When your phone asks a website for a page, the request carries the website's address as its destination and your connection's address as the return address. That is why the book compares IP addresses to postal addresses.
Packets and routers
Your data does not travel down one private wire from you to a website. It is chopped into small pieces called packets. Each packet carries the address it came from and the address it is going to, a little like a numbered parcel with a label on it.
Along the way, special computers called routers read those labels and pass each packet one step closer to its destination. If one path is busy or broken, packets can take another route. They may even arrive out of order. A further protocol on your device (TCP) checks that every piece has arrived, asks for any missing piece to be sent again, and puts the pieces back in order. Having many possible routes is what makes the Internet so resilient. One broken cable rarely stops anything.
You don't need more detail than this. Routing tables, subnet masks and the rest belong to a networking course. For security, the key point is simple: your data passes through many machines that you don't own or control.
One address, many people
The book teaches that every connected device has its own unique IP address. That was the Internet's original design, and it is still the right way to understand routing. In everyday use, though, it works a little differently.
- Inside your home, your router gives each device a private address from ranges set aside for private networks (IETF RFC 1918). These addresses are reused in millions of homes and are not reachable from the Internet directly.
- At the edge of your home, the router swaps those private addresses for one public address before traffic goes out. This is called network address translation (NAT). Your laptop, your phone and your smart TV all appear to the outside world as one address.
- At your ISP, many providers go a step further and share a single public address between many customers. The IETF reserved a special block of addresses for exactly this (RFC 6598). This is often called carrier-grade NAT.
So the public IP address a website sees is the address of a connection at a particular moment. That connection might be a household, a café, a university or a mobile network shared by many customers. It is not a name, and it is not proof of who was typing. A newer version of the protocol, IPv6, has far more addresses and reduces the need for sharing, but you will meet shared addresses every day for years to come.
Real-World Example
Imagine: a student forum receives an abusive post. The forum's records show it came from a certain IP address at 21:40. The moderators look it up and find that the address belongs to a large mobile network. Thousands of customers share that block of addresses through carrier-grade NAT. The address alone cannot say which customer, which phone or which person wrote the post. At best, the network operator's own records could point to a subscriber account at that moment. Even that names an account, not the person holding the phone.
This is why investigators treat an IP address as one clue among many. You will return to this idea in Unit VI, when we look at what evidence can and cannot prove.
From the Book to 2026
What the book teaches. Every device on the Internet gets a unique IP address, which works like a mailing address, and ISPs (the book names two regional providers) own the infrastructure.
Why it made sense. This is how IP was designed. The address analogy is still the clearest way to understand how data finds its destination, which is why the book uses it.
What has changed. Security guidance has evolved since the original text. To make the limited supply of older IPv4 addresses go further, home routers give devices private addresses (RFC 1918) and share one public address. Many ISPs also share public addresses between customers (RFC 6598). Telecom brand names also change over time, so this course uses generic examples such as "your broadband or mobile provider".
What to do now. Treat any public IP address as "a connection at a moment in time". Never assume it identifies a person, and don't panic if a message or pop-up quotes your IP address back to you. Websites see it routinely, because they need it to send you the page.
Watch: Packets, routers, and reliability — Internet 101 (Khan Academy)
This short, carefully produced video shows the packet-and-router journey you have just read about, with animations that make the routing idea easy to picture.
As you watch, notice:
- The opening point that your computer does not get a direct, dedicated line to the service. Data is split into packets that can take different routes, like a large object shipped in pieces on several trucks.
- How routers act like traffic managers, picking a path for each packet based on its destination IP address, and why having many paths keeps the Internet working when something fails.
- How TCP takes an inventory of the packets that arrive and asks for any missing ones to be resent before your song or page is complete.
The video reinforces what you just read — the lesson is complete without it.
What Would You Do?
You are browsing on your laptop when a full-screen pop-up appears: "WARNING. Your IP address 203.0.113.25 has been recorded. Your identity is known. Call this number within 10 minutes to avoid legal action." What do you make of it, and what do you do?
Knowledge Check
Your laptop and your phone are both on your home Wi-Fi. A 'what is my IP address' website shows the same public address on both. What is the most likely explanation?
A news report says an online attack was traced to an IP address belonging to a university. What can you reasonably conclude?
Answers explained
- Question 1 — c is right. At home, your router uses network address translation, so all your devices appear to the Internet as one public address. A matching address is normal. a is not right: devices on the same router share an address by design, so it is no sign of hacking. b is not right: nothing is misconfigured; this is how home connections normally work. d is not right: the site shows your real public address, because it needs that address to send you the page.
- Question 2 — b is right. An IP address points to a connection at a moment in time. Many people may share it, so it is a lead, not an identification. a is not right: a university address may be shared by thousands of people. c is not right: the traffic passed through the network; that says nothing about the equipment being malicious. d is not right: the address is real; it just doesn't name a person.
- The pop-up (What Would You Do?): it is a scare tactic. Every website you visit sees your public IP address, because it needs it to send you the page, and that address usually represents a shared connection. Quoting it proves nothing about your identity. Close the page (or the browser), don't call the number, and never pay. Unit III covers how scammers use fear and urgency like this.
Key Takeaways
- The Internet is a network of networks. ISPs own and run the connections between them.
- Computers communicate using fixed rules called protocols. The Internet Protocol uses IP addresses to route data.
- Data travels in packets that routers pass along, often by different routes, through machines you don't control.
- Home routers and many ISPs share public addresses, so an IP address identifies a connection at a moment in time, not a person.
Sources
- IETF — RFC 1918: Address Allocation for Private Internets
- IETF — RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space
- Khan Academy — Packets, routers, and reliability (Internet 101)
- Dr. Tahseen Al-Doori — Cyber Security Essentials, Chapter 3: Demystifying the Internet