How does the internet work
Type one line into the address bar, press Enter, and the page appears almost at once. In that short moment, everything you learned in this area happens in order, all together: an address is found from a name, a reliable connection is made, the connection is locked, and then the page is exchanged. Let's follow that invisible flow from start to finish.
Typing into the address bar
The journey starts at the address bar. You type the name of the site you want to visit, press Enter, and at that moment a long journey begins.
To us it lasts only a blink, but inside, several agreements do their jobs one after another. They are the very agreements you learned one by one in this area. Now let's follow that journey step by step from the beginning.
Type the name into the address bar one piece at a time. Once it is complete, the journey begins.
The name is typed, but the computer still does not know where to go. Names are given so people can remember them easily; to find the way, the computer needs an address made of numbers.
So the very first job is to find out the real number address this name points to. We have already met the agreement that handles this job: DNS.
DNS turns the name into an address
The first agreement is DNS. As we learned, DNS works like a giant phone book: give it a name and it tells you the number address. The browser first checks whether it has an answer it received recently, and if not, it asks a server whose job is looking up names.
Then the real address the computer will use comes back, clear and exact. Now, at last, we know where to go. This address is the starting point of the whole journey.
Tap to ask DNS. The name you typed comes back as a number address (IP). It is the same DNS you learned before.
The name has become a number address. But knowing the address does not get us there at once; the way to it runs through countless forks.
The data to send is split into small pieces called packets, which pass through the router at home and then cross from router to router. On the way out, the home router uses NAT to swap the home address for the public address. Packets, route finding, and NAT are all things we learned earlier. Now it is time to make a real connection with the server.
Connect with TCP, lock with HTTPS
Now that we know the address, we make a connection with the server there. What makes this connection trustworthy is TCP. First the two sides trade greetings three times to check that both are ready; after that, missing pieces are sent again and scrambled order is put right, so everything arrives complete and in order.
Once the connection is solid, a lock is put on it. That lock is HTTPS. It checks with a certificate that the other side is real, agrees on a shared key, and locks everything that passes back and forth.
Tap to make the connection (TCP), then tap to set the lock (HTTPS). When both are done, a safe channel opens. These are the two agreements you learned, TCP and HTTPS, working in turn.
The connection is made and the lock is set. A channel that is solid, locked, and trustworthy is now open.
But what we really want is not the connection itself; it is the page at the other end. One last agreement remains, the one that lets us exchange the page over this channel.
Seeing the whole flow at a glance
The last agreement is HTTP. Over the safe channel, the browser sends a request, "May I have this page?", and the server sends the page back: "Here it is." The browser then requests, over the same channel, the images and styling files the page needs.
When all these pieces are gathered and drawn on the screen, the journey is finally over. Now let's gather the whole flow from the address bar to the page in one place. Light up the steps one at a time, starting from the bottom.
Tap the steps in order from the bottom to light them up: address bar → DNS → IP address → TCP → HTTPS → HTTP. When all are lit, the page arrives.
One step lit up after another, and at the very top the page arrived. Address bar, DNS, address, connection, lock, page: if any one of them is missing, the journey stops.
Each agreement trusts the one below it to do its job and does only its own job, exactly. HTTP does not need to know how TCP carries the pieces, and TCP does not need to know which roads the packets take. This stacking, layer upon layer, is the layering we learned earlier.
Summary
In short: when you type an address, DNS finds the number address from the name, and packets pass through the home router and other routers to that address.
TCP makes everything arrive complete and in order, HTTPS locks the channel, and HTTP exchanges the page on top. Packets, addresses, routes, layers, reliable delivery, and safety are all inside this one flow. This is how the internet works.
Tap the key ideas from this area in order to review. (packet → address → route → layers → trust → web → safety)
You have followed it all the way here. Now, when you type an address, you can picture what happens behind it: a name becomes an address, packets cross the roads, and the agreements join hands in turn.
The internet is not magic; it is a giant postal system in which small agreements come together and work as one. The network area ends here. In the next area, data, we look at how computers store, organize, and quickly find the data that travels like this.