OSI Model — Application Layer
The application layer is Layer 7 of the OSI model and the layer closest to you. Everything a user actually does on a network — loading a page, sending mail, resolving a name — is delivered by the protocols that live here. This lesson identifies those protocols and explains where the layer starts and stops.
Where the layer sits
The OSI model has seven layers. The application layer is Layer 7, the top of the stack, and it is described as the layer closest to the user. That does not mean it is the software on your screen; it means it is the layer whose protocols the user’s software talks to directly. Below it, Layers 6 down to 1 exist purely to carry the messages that the application layer produces.
Think of the stack as a delivery business. The application layer writes the letters; the layers underneath address, sort, and physically carry them. The application layer is where the meaning of a message lives; the lower layers never interpret that meaning.
What the layer does
The application layer defines the protocols, message formats, and services that applications use. Its work includes, for example:
- Web access — requesting and delivering web pages.
- File transfer — moving files between hosts.
- Name resolution — turning a human-readable name into an IP address.
- Email — sending and retrieving messages.
- Remote access — running a command line on another machine.
- Dynamic addressing — giving a host its IP configuration automatically.
- Network management — monitoring and configuring devices.
What it does not do is move bits. Reliability, addressing, and the physical signal are all handled further down. The application layer works at the level of meaning: what the user asked for and what the far side should understand.
The application is not the layer
This distinction is tested and frequently misunderstood. A web browser, an email client, or a game is software. It is not one of the seven OSI layers. The application layer is the set of protocols and services that software uses.
Your browser does not become HTTP; it uses the HTTP protocol, which operates at the application layer. Likewise, an FTP client uses FTP, and a mail client uses SMTP and either POP3 or IMAP4.
The protocols that live here
The application layer is home to many well-known protocols. Learn the one-line job of each; the port numbers are repeated here for convenience and are fully covered in Lesson 14 (Transport Layer) and Week 8.
| Protocol | What it does | Transport · port |
|---|---|---|
| HTTP | Transfers web content between a browser (client) and a web server; unencrypted. | TCP · 80 |
| HTTPS | HTTP protected by TLS for encryption and server authentication. | TCP · 443 |
| FTP | Transfers files between hosts using separate control and data connections. | TCP · 21 (control) / 20 (data) |
| TFTP | Trivial File Transfer Protocol: simple file transfer with no authentication. | UDP · 69 |
| DNS | Resolves host names (for example www.example.com) to IP addresses. | UDP/TCP · 53 |
| SMTP | Sends and relays email (client to server, and server to server). | TCP · 25 |
| POP3 | Retrieves email, typically downloading and removing it from the server. | TCP · 110 |
| IMAP4 | Retrieves email while leaving it on the server so devices stay in sync. | TCP · 143 |
| DHCP | Provides IP address, mask, gateway, and DNS settings automatically. | UDP · 67 (server) / 68 (client) |
| SSH | Encrypted remote command-line access and secure file transfer. | TCP · 22 |
| Telnet | Unencrypted remote command-line access. | TCP · 23 |
| SNMP | Monitors and manages network devices. | UDP · 161 (agent) / 162 (traps) |
TCP or UDP? A quick map
Application-layer protocols must choose a transport. Some need reliability and ordering and use TCP; others value speed and low overhead and use UDP; a few use both.
- Use TCP: HTTP, HTTPS, FTP, SSH, Telnet, SMTP, POP3, IMAP4.
- Use UDP: TFTP, DHCP, SNMP.
- Use both: DNS — ordinary queries use UDP, while large responses and zone transfers use TCP.
The reason is that TCP provides acknowledgements, ordering, and retransmission, while UDP sends datagrams with no guarantee of delivery. That trade-off is the subject of Week 8.
67 on the server and 68 on the client.Client, server, and peer roles
Application-layer protocols run inside roles. In the client–server model, a client requests a service and a server provides it; the server is centralised and managed. HTTP, FTP, SMTP, POP3, and IMAP4 are classic examples: a browser (client) asks a web server, and a mail client asks a mail server.
The role is a behaviour, not a type of hardware: the same laptop is a client when it browses and a server when it shares a file.
Review
Check what you have learned with these review questions. The key terms and sources from this lesson are listed below the quiz.
| Key term | Meaning |
|---|---|
| Application layer | Layer 7 of OSI; provides network services to application processes. |
| Application protocol | A protocol that operates at Layer 7, such as HTTP, DNS, or SMTP. |
| Client | The role that requests a service. |
| Server | The role that provides a service. |
| Peer-to-peer | A model in which a host acts as both client and server. |
| Well-known protocol | An internet protocol standardised with an assigned port (for example HTTP on TCP 80). |
Sources & references
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), which defines the layering model used on the Internet. rfc-editor.org/rfc/rfc1122.
- IANA. Service Name and Transport Protocol Port Number Registry. iana.org.
- ISO/IEC 7498-1. Information technology — Open Systems Interconnection — Basic Reference Model. iso.org.
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.