What happens when you type “google.com”?
You press Enter. In less than a second, Google appears.
But what actually happened? Your request just traveled thousands of miles, passed through dozens of computers, and came back with millions of bytes of data.
All in under 200 milliseconds.
By the end of this guide, you’ll understand:
- ✅ How your computer finds Google (DNS)
- ✅ How data travels across the internet (TCP/IP)
- ✅ Why the internet is so fast and reliable
- ✅ What happens at each step of the journey
Let’s follow your data on its incredible journey.
The Hidden Physical Layer
Before we talk about software, remember: The internet is physical.
The internet is 99% underwater fiber-optic cables connecting continents. Your WiFi is just the last 50 feet.
The Analogy: Sending a Package Across the World
Imagine you want to send a birthday present to a friend in Tokyo.
You can’t just throw it in their direction and hope it arrives. You need:
- Their address (Where does it go?)
- A shipping company (Who carries it?)
- Packaging (How is it protected?)
- Tracking (Did it arrive?)
The internet works the same way:
- DNS = The address book (finds where things are)
- IP = The shipping label (the actual address)
- TCP = The shipping company (reliable delivery)
- Packets = The boxes (your data, broken into pieces)
The Big Picture: Your Data’s Journey
Every time you load a webpage, your data completes an incredible round-trip in milliseconds:
Your Browser → DNS → TCP → IP Network → Server → Back
The 4 steps below break down exactly what happens at each stage.
When you type google.com, your data goes through 4 major steps:
| Step | What Happens | Real-World Analogy |
|---|---|---|
| 1. DNS Lookup | ”What’s Google’s address?” | Looking up a phone number |
| 2. Connection | ”Hello Google, can we talk?” | Calling and waiting for pickup |
| 3. Request | ”Send me your homepage” | Placing your order |
| 4. Response | ”Here’s the data!” | Receiving your package |
Let’s explore each step.
Step 1: DNS — The Internet’s Phone Book
Your computer doesn’t understand “google.com”. It only understands IP addresses — numbers like 142.250.185.14.
DNS is like a giant phone book.
You know your friend’s name (“Google”), but you need their phone number (IP address) to call them.
DNS converts names into numbers:
google.com→142.250.185.14youtube.com→142.250.190.78github.com→140.82.121.4
How DNS Works
(Want the deep dive? Read our full guide on How DNS Works)
- You type:
google.com - Your computer asks: “Hey DNS, what’s the IP for google.com?”
- DNS responds: “It’s
142.250.185.14” - Your computer: “Great, now I can connect!”
Ask DNS for an IP address
nslookup [domain]nslookup google.comName: google.com Address: 142.250.185.14
- •Try this with any website to see its IP
- •Some sites have multiple IPs for load balancing
- •Works on Windows, Mac, and Linux
🎉 You just learned: DNS converts human-friendly names into computer-friendly numbers!
Step 2: TCP — The Reliable Messenger
Now your computer knows Google’s IP address. But how does it actually send data?
This is where TCP (Transmission Control Protocol) comes in.
TCP is like a reliable courier service.
Imagine you’re sending a 10-page letter, but the post office only accepts 1 page at a time. You would:
- Number each page (1 of 10, 2 of 10…)
- Send them separately
- Receiver confirms each page arrived
- Reassemble in the correct order
TCP does exactly this with your data. It:
- Breaks data into packets (small pieces)
- Numbers them so they can be reassembled
- Confirms each one arrives
- Resends any that get lost
The TCP Handshake
Before sending data, TCP does a “handshake” — like a polite greeting:
| Step | Your Computer | |
|---|---|---|
| 1. SYN | ”Hey, can we talk?“ | |
| 2. SYN-ACK | ”Sure! I’m ready.” | |
| 3. ACK | ”Great, let’s start!” |
This takes just 30 milliseconds but ensures both sides are ready.
See the path your data takes to reach a server
tracert [destination]tracert google.com1 <1 ms router.local [192.168.1.1] 2 5 ms isp-gateway [10.0.0.1] 3 12 ms city-router [72.14.233.1] 4 25 ms google-edge [142.250.185.14]
- •On Mac/Linux, use 'traceroute' instead
- •Each line is a 'hop' - a router your data passed through
- •The numbers show how long each hop takes
🎉 You just learned: TCP is the reliable delivery service that makes sure your data arrives complete and in order!
Step 3: IP — The Address System
IP (Internet Protocol) is the addressing system of the internet.
IPv4: The classic format (running out!)
- Looks like:
192.168.1.100 - About 4.3 billion possible addresses
IPv6: The new format (practically unlimited)
- Looks like:
2001:0db8:85a3:0000:0000:8a2e:0370:7334 - About 340 undecillion addresses (that’s 340 followed by 36 zeros!)
Your Computer Has an IP Too
Every device on the internet has an IP address. Yes, even your phone.
See your computer's IP address
ipconfigipconfigIPv4 Address: 192.168.1.105 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.1.1
- •On Mac/Linux, use 'ifconfig' or 'ip addr'
- •192.168.x.x is usually your local network address
- •Your 'public' IP is different - search 'what is my IP'
🎉 You just learned: Every device has a unique IP address, like a home address for the internet!
Step 4: Packets — Breaking Data into Pieces
Your data doesn’t travel as one big chunk. It’s broken into small packets.
Imagine sending a large painting through the mail.
The post office says: “Too big! Cut it into pieces.”
So you:
- Cut the painting into 100 small squares
- Number each square (1-100)
- Mail them separately
- Your friend reassembles the puzzle
This is exactly how internet data works!
- Large files → Many small packets
- Each packet finds its own route
- They might arrive out of order
- TCP reassembles them correctly
Why Packets Are Brilliant
| Benefit | Explanation |
|---|---|
| Speed | Multiple routes = faster delivery |
| Reliability | Lost packet? Just resend that one |
| Efficiency | Network can handle many users at once |
| Resilience | One broken route? Packets go around it |
Troubleshooting: When the Internet Breaks
| Problem | Meaning | Solution |
|---|---|---|
| ”DNS not responding” | Can’t look up addresses | Try DNS 8.8.8.8 (Google’s DNS) |
| “Connection timed out” | Server not responding | Check if the site is down |
| ”Packet loss” | Data not arriving | Check your WiFi signal |
| ”High latency” | Slow response | Too many hops or congested network |
“The internet is down!” usually means:
- Your WiFi is disconnected
- Your router needs a restart
- Your ISP has an outage
The actual internet almost never goes down. It was designed to survive a nuclear war!
Test if a server is reachable
ping [destination]ping google.comReply from 142.250.185.14: bytes=32 time=24ms TTL=117 Reply from 142.250.185.14: bytes=32 time=23ms TTL=117
- •Low time (ms) = fast connection
- •Request timed out = can't reach server
- •Press Ctrl+C to stop
Key Takeaways
You just learned how the entire internet works! Here’s the summary:
- ✅ DNS converts domain names (google.com) to IP addresses (142.250.185.14)
- ✅ TCP ensures reliable, ordered delivery of your data
- ✅ IP is the addressing system that routes your data
- ✅ Packets break your data into small pieces for efficient transmission
- ✅ The internet is resilient — designed to route around problems
Every time you load a webpage, all of this happens in under a second. The internet is truly a marvel of engineering.
🧠 Check Your Understanding
Internet Mastery Check
Take a quick 3-question quiz to check your understanding.
What’s Next?
Ready to go deeper? Here’s where to explore:
- DNS Deep Dive: How DNS servers talk to each other
- TCP vs UDP: When reliability matters (and when speed wins)
- How HTTPS Works: Adding encryption to your connection
Found this helpful? Explore more in the Networking Hub!