How the Internet Works

Understanding How the Internet Works

Internet communication is organised in layers. Each layer has one job and adds useful information to the data it carries. A browser creates a request for a resource such as a page, image, or video segment.

HTTP describes the request and response format. TCP divides the content into numbered pieces and checks whether the pieces arrive. IP places source and destination addresses on each piece so networks can forward it.

At the local level, technologies such as Ethernet or Wi-Fi move data between nearby devices. This layered design matters because a web page can work over fibre, copper cable, mobile radio, or satellite without changing how the browser requests it.

Reliable delivery is more complicated than simply resending missing data. TCP uses acknowledgments to learn which numbered pieces reached the destination. If an acknowledgment does not arrive in time, TCP assumes a piece may be lost and sends it again.

It also controls its sending rate. When too much traffic enters a network, routers may discard packets because their temporary memory is full. TCP treats this as a sign of congestion and slows down.

This prevents one fast sender from overwhelming a shared connection. Video calls and online games often use UDP for some traffic instead. UDP has less checking, so late data can be ignored rather than delaying newer sound or movement updates.

DNS works like a distributed directory, not one giant list stored in one place. Your device often asks a nearby resolver run by a school, home router, or internet provider. That resolver can use cached results if it learned an address recently.

If it does not know, it follows a chain of DNS servers that leads toward the server responsible for the domain. Cached records have an expiry time called a time to live. This reduces repeated work, though it means changes to a domain can take time to appear everywhere.

DNS is important for safety because attackers may try to send users to a false address. Secure DNS methods can help verify that answers have not been changed.

HTTPS protects web traffic using TLS. Before private page data is exchanged, the browser checks a digital certificate presented by the site. The certificate links the site name to a public cryptographic key and is signed by a trusted certificate authority.

The browser and server then create shared session keys for encryption. Encryption hides the contents from people watching the network, while integrity checks reveal unwanted changes.

HTTPS does not prove that a website is honest or that every link is safe. Students should still inspect domain names carefully, avoid entering passwords on suspicious pages, and understand that a padlock means the connection is protected rather than the site being trustworthy.

Speed depends on more than the advertised bandwidth of a connection. Bandwidth is the amount of data a link can carry each second. Latency is the time spent waiting for signals to travel and for devices to process them.

A large download benefits strongly from high bandwidth. A game can feel slow even on a fast connection if latency is high. Distance matters because signals need time to cross cables, and each network device adds a small delay.

Weak Wi-Fi, crowded school networks, background downloads, and overloaded servers can add delays or packet loss. When investigating a slow connection, separate the time needed to find a name, establish a secure connection, wait for a server response, and transfer the actual content.