Layer 7: Application
Provides network services to applications.
Examples: HTTP, HTTPS, DNS, SMTP
Opening a website or resolving a domain.
Learn computer networks, Wi-Fi, routers, IP addressing, network protocols, troubleshooting, and network security through practical guides and step-by-step explanations.
Understand how devices communicate, how network layers work, which protocols use common ports, and how to troubleshoot real connections using practical commands.
A network protocol is a set of rules that defines how devices exchange information. Protocols specify details such as message formats, addressing, connection behavior, error handling, and communication procedures.
Web communication
Transport of application data
Addressing and routing
Network architecture describes how devices, network services, communication protocols, and infrastructure are organized to work together.
A client requests a service, and a server processes the request. Browsers and web servers are a common example.
Devices can communicate or share resources directly without relying on one central server for every exchange.
Applications may separate presentation, application logic, and data storage into distinct tiers.
Describes how devices and links are arranged, such as star, mesh, bus, or ring.
The OSI model is a reference model used to understand and troubleshoot communication. Real protocols do not always fit neatly into a single layer.
Provides network services to applications.
Examples: HTTP, HTTPS, DNS, SMTP
Opening a website or resolving a domain.
Represents, encodes, or transforms application data.
Examples: TLS-related presentation functions, data formats
Character encoding and data serialization.
Describes the establishment and management of communication sessions.
Examples: Session-management concepts
Maintaining a logical dialog between applications.
Provides transport between application endpoints.
Examples: TCP, UDP
Reliable delivery with TCP or datagrams with UDP.
Handles logical addressing and routing between networks.
Examples: IPv4, IPv6, ICMP
A router forwarding an IP packet.
Handles local-link frames and hardware addressing.
Examples: Ethernet, Wi-Fi MAC, ARP
A frame traveling across a local Ethernet network.
Carries signals across a physical medium.
Examples: Ethernet physical media, radio, fiber
Electrical, optical, or wireless signals.
Top to bottom: Application → Presentation → Session → Transport → Network → Data Link → Physical.
The TCP/IP model describes the layers commonly used by Internet communication. It is usually represented using four layers.
Protocols: HTTP, HTTPS, DNS, SSH, SMTP
Data unit: Application data
Protocols: TCP, UDP
Data unit: TCP segment / UDP datagram
Protocols: IPv4, IPv6, ICMP
Data unit: IP packet
Protocols: Ethernet, Wi-Fi
Data unit: Frame and physical signals
When you open a website, multiple protocols cooperate to establish communication and deliver the requested content.
Encapsulation occurs when each network layer adds information needed to deliver or process data. The receiving device processes the layers in reverse through decapsulation.
This is a simplified TCP-based example. UDP uses a UDP datagram, and actual encapsulation depends on the protocols involved.
These are common default port assignments. Actual services can use different ports, and some protocols do not use TCP or UDP ports.
| Protocol | Port | Purpose |
|---|---|---|
| HTTP | 80/TCP | Transfers web content; unencrypted by itself. |
| HTTPS | 443/TCP | HTTP protected by TLS, usually over TCP. |
| DNS | 53/UDP, TCP | Resolves domain names; TCP is also used in several cases. |
| DHCPv4 | 67/UDP, 68/UDP | Assigns IPv4 configuration to clients. |
| SSH | 22/TCP | Secure remote shell and administration. |
| FTP | 21/TCP control | File transfer protocol; standard FTP is not encrypted. |
| SFTP | 22/TCP typically | File transfer over SSH. |
| SMTP | 25/TCP commonly | Mail transfer between mail servers. |
| IMAP | 143/TCP | Accesses and manages email; TLS can be added. |
| IMAPS | 993/TCP | IMAP over TLS. |
| POP3 | 110/TCP | Retrieves email; TLS can be added. |
| POP3S | 995/TCP | POP3 over TLS. |
| NTP | 123/UDP | Synchronizes system clocks. |
| SNMP | 161/UDP commonly | Monitors and manages network devices. |
| RDP | 3389/TCP, UDP | Remote Desktop services; configurations vary. |
| SMB | 445/TCP | File and printer sharing, commonly on Windows networks. |
| LDAP | 389/TCP, UDP | Directory access; TCP is common for LDAP queries. |
| LDAPS | 636/TCP | LDAP protected by TLS. |
| ICMP | No TCP/UDP port | Carries diagnostic and network-control messages. |
| ARP | No TCP/UDP port | Maps IPv4 addresses to link-layer addresses on a local link. |
Regenerates or repeats signals.
Repeats incoming bits to other ports; generally obsolete.
Forwards Ethernet frames using MAC address information.
Forwards IP packets between networks.
Enforces traffic policies using addresses, ports, connections, or application data.
Connects wireless clients to a network.
Relays requests on behalf of clients or servers.
Distributes traffic across backend servers.
ipconfig /allip addrip routeping 1.1.1.1tracert example.comtracepath example.comnslookup example.comss -tunTest-NetConnection example.com -Port 443Use systems and services you own or are authorized to test. Command availability differs between Windows and Linux.
Use these exercises to connect networking theory with real output.
ipconfig /allOn Windows, identify the IPv4 address, subnet mask, default gateway, and DNS servers. Compare these values with your router's local network configuration.
nslookup example.comRecord the DNS server and the returned addresses. Run the command again and compare the results. Cached answers and load-balanced destinations can affect what you see.
Test-NetConnection example.com -Port 443Examine the DNS result, remote address, and TcpTestSucceeded field. A successful TCP connection does not by itself prove that TLS negotiation or the website will succeed.
dns.tcp or tls.Check power, cables, Wi-Fi signal, and link status.
Check Wi-Fi association, VLAN configuration, and local-link reachability.
Check IP settings, subnet masks, gateways, and routes.
Check whether the required TCP port is reachable and whether a firewall blocks it.
Check DNS, TLS certificates, server responses, and application logs.
Learn what each protocol does, identify its place in the communication process, and verify your understanding using terminal commands and packet captures. These fundamentals support network administration, troubleshooting, and defensive security.
Continue Learning
Build your networking knowledge with focused guides on network types, IP addressing, Wi-Fi troubleshooting, and defensive network security.