When you connect a laptop to Wi-Fi and open a website, several conversations happen before the page appears. Your device obtains network settings, finds the website’s address, delivers traffic to a router, establishes a protected connection, and requests the page.
Each task follows a network protocol. Understanding these protocols helps explain how networks work and why a connection can fail even when a device says it is connected.
1. What Is a Network Protocol?
A network protocol is a set of rules that devices follow to communicate. It defines message formats, what those messages mean, and how participants respond. Depending on the protocol, it may also describe timing, error handling, and how a conversation begins or ends.
Think of a conversation between two people. Knowing the same vocabulary is helpful, but they also need to understand who is asking a question and what counts as an answer. Protocols give computers that shared structure.
Many Internet protocols are documented in RFCs, short for Request for Comments. These documents allow developers to build compatible implementations. However, not every protocol is an Internet standard, and not every RFC defines a standard.
2. Hosts, Clients, and Servers
A host is a network endpoint that sends or receives data. Laptops, phones, printers, and servers can all be hosts.
A client is software that requests a service, while a server is software that provides one. A browser acts as a client when it requests a page from web server software. People also use “server” to describe the computer running that software.
These are roles, not permanent categories of hardware. One computer can run both client and server software. A web server can also become a client when it contacts another service.
An IP address helps identify a network interface for communication across IP networks. A port number helps the receiving operating system direct traffic to the appropriate service. One machine can therefore provide several services at the same IP address.
3. ARP: Finding a Local MAC Address
ARP stands for Address Resolution Protocol. On typical IPv4 Ethernet networks, it discovers the MAC address associated with an IPv4 address on the local link. A MAC address is an address used to deliver network frames locally; a frame is a unit of data transmitted over that link.
Suppose a laptop needs to reach a local printer at 192.168.1.50. If the mapping is missing from its ARP cache, a temporary store of known mappings, the laptop broadcasts a request asking which device has that address. The printer replies with its MAC address.
The laptop can then address local frames to the printer.
For an Internet destination, the laptop normally discovers the MAC address of its local router, not the remote website. The router is the next hop: the next device responsible for forwarding the packet toward its destination.
ARP requests normally stay within the local broadcast domain. IPv6 uses Neighbor Discovery instead of ARP.
Remember: ARP helps deliver IPv4 traffic to the next device on the local link.
4. FTP: Transferring Files
FTP stands for File Transfer Protocol. It allows a client to upload, download, and manage files on a server.
An FTP client might use RETR, short for retrieve, to request a download, or STOR to upload a file. These commands have defined meanings that both sides understand.
FTP uses separate connections for commands and data. Its control connection normally uses TCP port 21. TCP, the Transmission Control Protocol, provides reliable, ordered delivery of a stream of bytes. The data connection depends on the FTP mode and negotiated connection details.
Traditional FTP does not encrypt login credentials or file contents. FTPS adds TLS protection to FTP. SFTP, the SSH File Transfer Protocol, is a different protocol that operates over SSH, a system for secure remote communication.
Remember: FTP transfers files, but ordinary FTP does not provide encryption.
5. SMTP: Sending and Relaying Email
SMTP stands for Simple Mail Transfer Protocol. It handles email submission and transfer between mail systems.
When you send a message, your email application typically submits it to a mail server. Mail servers then use SMTP to relay it toward the recipient’s system.
An SMTP exchange begins with a server greeting. The client normally identifies itself using EHLO, after which commands such as MAIL FROM, RCPT TO, and DATA describe the sender, recipient, and message. Servers return numeric replies indicating success, intermediate steps, or errors.
SMTP is not normally the protocol used to synchronize your inbox. Email applications commonly use IMAP for that purpose; POP3 is another retrieval protocol. A webmail browser communicates with the website over HTTPS while the provider handles mail transport behind the scenes.
SMTP can use TLS to protect a connection, but protection between two mail systems is not automatically end-to-end encryption between the people exchanging messages.
Remember: SMTP sends and relays email; reading an inbox is a separate job.
6. HTTP: Requesting Web Resources
HTTP stands for Hypertext Transfer Protocol. It defines how clients request resources and how servers respond.
A resource can be an HTML page, image, document, video segment, or application data. HTML, or Hypertext Markup Language, describes the structure of a webpage. HTTP is the communication protocol used to request and transfer resources.
When you visit a page, your browser may send a GET request. If the request succeeds, the server commonly responds with 200 OK and the requested content. Other responses can indicate a redirect, missing resource, or server error.
HTTP also defines methods such as POST, often used to submit information. Requests and responses include headers, which carry information about the message, and may include a body containing the actual content.
A webpage usually involves multiple requests. After receiving the main HTML document, the browser may fetch images, stylesheets that control appearance, and JavaScript programs that add behavior.
Remember: HTTP defines the web’s requests and responses.
7. SSL: The Older Security Protocol
SSL stands for Secure Sockets Layer. It was developed to protect communication over networks and was the predecessor to TLS.
SSL is obsolete and should not be used for modern secure connections. Although hosting companies still commonly sell “SSL certificates,” modern HTTPS connections use TLS.
The familiar commercial name does not mean that a website is running the old SSL protocol.
Remember: SSL is an older protocol name that survives in everyday terminology.
8. TLS: Protecting Communication
TLS stands for Transport Layer Security. It protects data exchanged over a connection.
Its main goals include confidentiality, which prevents outsiders from reading protected content; integrity, which helps detect unauthorized changes; and authentication, which helps establish the identity of the other party.
During a TLS handshake, the participants agree on connection parameters and establish cryptographic keys. In a typical website connection, the server presents a digital certificate, and the browser checks whether it is valid for the requested hostname and trusted under the browser’s rules.
TLS can protect several application protocols, including HTTP and SMTP. It protects data in transit between TLS endpoints; it does not automatically protect data after an endpoint decrypts it.
Remember: TLS provides the security used by modern HTTPS connections.
9. HTTPS: HTTP with Transport Security
HTTPS means HTTP protected using TLS. It preserves HTTP’s requests, responses, methods, and status codes while protecting the exchange.
When you enter an HTTPS address, your browser establishes a protected connection before sending ordinary application requests over it.
HTTP/1.1 and HTTP/2 commonly use TLS over TCP. HTTP/3 uses QUIC, a transport protocol built over UDP with TLS 1.3 integrated into its security design. UDP, the User Datagram Protocol, carries datagrams without TCP’s built-in reliable stream; QUIC adds the transport features HTTP/3 needs.
HTTPS protects communication with the endpoint authenticated for the hostname. It does not guarantee that the site’s owner is honest or that its content is accurate.
Remember: HTTPS combines web communication with transport security.
10. DNS: Looking Up Names
DNS stands for Domain Name System. It is a distributed naming system and a family of protocols for looking up records associated with domain names.
A browser needs address information to connect to a hostname such as www.hostsdepot.com. If a usable answer is not already cached, the device typically asks a recursive resolver, a DNS service that finds answers on its behalf. The resolver can consult authoritative nameservers, which publish records for the relevant domain.
An A record contains an IPv4 address; an AAAA record contains an IPv6 address. One hostname can have multiple addresses.
DNS also helps route email. A sending mail server looks up MX records for the recipient’s domain to find the designated mail servers, then resolves their hostnames to addresses. DNS does not translate an entire email address into an IP address.
Remember: DNS looks up information associated with names, including addresses and mail-routing records.
11. Four Common IPv4 Network Settings
For a typical IPv4 home or office connection, four settings explain much of how a device reaches Internet services.
IP address: An address such as 192.168.1.100 identifies the device’s interface on that network. This example is a private address, not a globally unique Internet identity.
Subnet mask: A mask such as 255.255.255.0 identifies the network portion of an IPv4 address. The equivalent prefix notation is /24. With this configuration, 192.168.1.100 belongs to the 192.168.1.0/24 subnet.
Default gateway: Usually a local router address, such as 192.168.1.1. The device uses the default route when no more specific route matches the destination.
DNS resolver: The service used to look up names. A home router may forward these queries to another resolver.
These settings are a common configuration pattern, not an absolute requirement for every network interaction. Local communication may need no default gateway, and communication using known IP addresses may need no DNS lookup. Correct settings also do not guarantee that upstream connectivity works.
IPv6 uses different configuration mechanisms, including Router Advertisements and, depending on the network, SLAAC or DHCPv6. The IPv4 explanation should not be applied unchanged to IPv6.
12. DHCP: Obtaining Settings Automatically
DHCP stands for Dynamic Host Configuration Protocol. DHCPv4 can provide an IPv4 address, subnet mask, router information, and DNS settings automatically.
A common initial exchange follows four steps, remembered as DORA:
- Discover: The client searches for DHCP servers.
- Offer: A server proposes an address and configuration.
- Request: The client requests the selected offer.
- Acknowledgment: The server confirms the assignment.
The address is usually leased for a limited time. Clients renew leases so they can continue using their addresses. Renewal and reconnection do not always repeat the full initial exchange.
A home router often provides DHCP service. Larger networks may use dedicated servers and DHCP relays, which forward messages between clients and servers on different networks.
DHCP supplies configuration; it does not carry the device’s subsequent web traffic.
Remember: DHCP configures the device, while DNS helps it look up destinations.
13. Putting It Together: Opening a Website
Imagine connecting a laptop to a typical IPv4 Wi-Fi network and opening https://www.hostsdepot.com. Assume there are no reusable connections or cached answers.
First, the laptop joins the wireless network. DHCP then supplies its IPv4 configuration.
Next, the laptop needs to contact its DNS resolver. Before sending local frames, it may use ARP to learn the resolver’s MAC address if the resolver is local, or the gateway’s MAC address if the resolver is reached through a router.
DNS supplies address information for the website. The laptop’s routing decision determines where to send the website traffic. For a remote server, this is normally through its default gateway; ARP supplies the gateway’s MAC address if needed.
The browser establishes an appropriate secure connection, such as TCP with TLS for HTTP/2 or QUIC for HTTP/3. It then sends HTTP requests, receives responses, and renders the page.
The precise order varies with caching, connection reuse, and network configuration. ARP may already have been needed for the DNS query; it is not simply a step that always happens after DNS.
Each protocol solves one part of the larger task. Knowing those roles makes networking easier to understand: DHCP provides configuration, ARP supports local delivery, DNS supplies naming information, HTTP exchanges web resources, and TLS protects communication. FTP handles file transfer, while SMTP handles outgoing and relayed email.