Internet Protocols Explained — HTTP, HTTPS, FTP, SMTP, POP3, IMAP, DNS

Every Internet protocol explained — HTTP, HTTPS, FTP, SMTP, POP3, IMAP, TCP/IP, DNS, and which port each uses, with comparison tables and real-world examples.

Protocols are the rules that govern how data is sent and received over the Internet. Understanding these protocols is essential for CBSE students in Classes 9-12. This guide explains every protocol you need to know in simple language with real-world examples.

What is a Protocol?

A protocol is a set of rules and standards that define how data is transmitted between devices on a network. Without protocols, computers would not be able to communicate with each other.

Simple analogy: Think of protocols as languages. Just as two people need to speak the same language to communicate, two computers need to follow the same protocol to exchange data.

TCP/IP: The Foundation Protocol

TCP/IP (Transmission Control Protocol / Internet Protocol) is the fundamental protocol of the Internet. It defines how data is packaged, addressed, transmitted, routed, and received.

TCP (Transmission Control Protocol)

TCP handles the reliable transmission of data:

Breaks data into packets - Large data is divided into small packets
Numbers each packet - So they can be reassembled in order
Ensures delivery - Checks that all packets arrive correctly
Error checking - Resends packets if they are lost or corrupted
Connection-oriented - Establishes a connection before sending data

IP (Internet Protocol)

IP handles addressing and routing:

Assigns addresses - Every device gets a unique IP address
Routes packets - Directs packets from source to destination
Best-effort delivery - Tries to deliver but does not guarantee

How TCP/IP Works Together

Sender:
Data -> [TCP breaks into packets] -> [IP adds addresses] -> Internet

Internet:
[Routers forward packets using IP addresses]

Receiver:
Internet -> [IP delivers packets] -> [TCP reassembles in order] -> Data

IP Address

An IP Address is a unique numerical label for every device on the Internet.

Version	Format	Example	Bits
IPv4	Four numbers separated by dots	192.168.1.1	32-bit
IPv6	Eight groups of hexadecimal	2001:0db8:85a3:0000:0000:8a2e:0370:7334	128-bit

Why IPv6? IPv4 has about 4.3 billion addresses, which is not enough for all devices in the world. IPv6 provides trillions of trillions of addresses.

HTTP and HTTPS: Web Protocols

HTTP (HyperText Transfer Protocol)

HTTP is the protocol used for transferring web pages on the World Wide Web. When you type a website address in your browser, HTTP handles the request and response.

How HTTP works:

You type http://www.example.com in your browser
Your browser sends an HTTP request to the web server
The server processes the request
The server sends an HTTP response with the web page
Your browser displays the page

HTTPS (HTTP Secure)

HTTPS is the secure version of HTTP. It encrypts data using SSL/TLS protocols before transmission.

Feature	HTTP	HTTPS
Full form	HyperText Transfer Protocol	HyperText Transfer Protocol Secure
Security	No encryption	Encrypted using SSL/TLS
Port	Port 80	Port 443
URL prefix	`http://`	`https://`
Speed	Slightly faster	Slightly slower (due to encryption)
Usage	Non-sensitive pages	Banking, shopping, login pages
Indicator	No padlock	Padlock icon in address bar

Exam tip: Always mention that HTTPS uses SSL/TLS encryption and is indicated by a padlock icon.

FTP: File Transfer Protocol

FTP (File Transfer Protocol) is used to upload and download files between a client and a server.

How FTP works:

You connect to an FTP server using FTP client software
You authenticate with username and password
You can browse files on the server
Upload files from your computer to the server
Download files from the server to your computer

Feature	Detail
Purpose	File upload and download
Port	Port 20 (data) and Port 21 (control)
Security	Not encrypted by default
Secure version	SFTP (SSH File Transfer Protocol) or FTPS
Use case	Website hosting, large file transfers

Email Protocols: SMTP, POP3, IMAP

SMTP (Simple Mail Transfer Protocol)

SMTP is used for sending emails from the sender's device to the mail server and between mail servers.

Feature	Detail
Purpose	Sending emails
Port	Port 25 (default), Port 587 (with encryption)
Direction	From sender to server, server to server
Full form	Simple Mail Transfer Protocol

POP3 (Post Office Protocol version 3)

POP3 is used for receiving emails by downloading them from the server to your device.

Feature	Detail
Purpose	Downloading emails from server
Port	Port 110
Behavior	Downloads emails and usually deletes them from server
Best for	Single device email access

IMAP (Internet Message Access Protocol)

IMAP is used for accessing emails stored on the server without downloading them.

Feature	Detail
Purpose	Accessing emails on the server
Port	Port 143
Behavior	Keeps emails on the server
Best for	Multiple device email access

Email Protocol Flow

Sending an email:
Sender -> [SMTP] -> Sender's Mail Server -> [SMTP] -> Receiver's Mail Server

Receiving an email:
Receiver's Mail Server -> [POP3 or IMAP] -> Receiver's Device

POP3 vs IMAP

Feature	POP3	IMAP
Full form	Post Office Protocol 3	Internet Message Access Protocol
Email storage	Downloads to device, deletes from server	Keeps on server
Multiple devices	Difficult (email on one device only)	Easy (same emails on all devices)
Internet requirement	Only needed to download	Needed to read emails
Storage	Uses device storage	Uses server storage
Speed	Faster (emails are local)	Slower (fetches from server)
Best for	Single computer users	Users with multiple devices

DNS: Domain Name System

DNS translates human-readable domain names into IP addresses that computers use.

Why DNS exists: Remembering 142.250.195.46 for Google is impossible. DNS lets you type google.com instead.

How DNS works:

You type www.google.com in your browser
Your computer asks a DNS server: "What is the IP address of google.com?"
The DNS server responds: 142.250.195.46
Your browser connects to that IP address
Google's server sends back the web page

Feature	Detail
Purpose	Converts domain names to IP addresses
Port	Port 53
Analogy	Phone book of the Internet
Cache	DNS results are cached for faster future lookups

DHCP: Dynamic Host Configuration Protocol

DHCP automatically assigns IP addresses to devices when they connect to a network.

Without DHCP: You would need to manually set an IP address on every device. With DHCP: Your phone, laptop, and other devices automatically get IP addresses when they connect to Wi-Fi.

Telnet and SSH

Telnet

Telnet allows remote access to another computer over a network. However, it sends data (including passwords) in plain text, making it insecure.

SSH (Secure Shell)

SSH is the secure replacement for Telnet. It encrypts all communication between the client and server.

Feature	Telnet	SSH
Security	Not encrypted	Encrypted
Port	Port 23	Port 22
Usage	Outdated, rarely used	Standard for remote access

Complete Protocol Reference Table

Protocol	Full Form	Port	Purpose
HTTP	HyperText Transfer Protocol	80	Web page transfer
HTTPS	HTTP Secure	443	Secure web page transfer
FTP	File Transfer Protocol	20, 21	File upload/download
SMTP	Simple Mail Transfer Protocol	25	Sending emails
POP3	Post Office Protocol 3	110	Downloading emails
IMAP	Internet Message Access Protocol	143	Accessing emails on server
DNS	Domain Name System	53	Domain to IP conversion
DHCP	Dynamic Host Configuration Protocol	67, 68	Auto IP assignment
Telnet	Teletype Network	23	Remote access (insecure)
SSH	Secure Shell	22	Secure remote access
TCP	Transmission Control Protocol	-	Reliable data delivery
IP	Internet Protocol	-	Addressing and routing
UDP	User Datagram Protocol	-	Fast but unreliable delivery

TCP vs UDP

Feature	TCP	UDP
Full form	Transmission Control Protocol	User Datagram Protocol
Connection	Connection-oriented	Connectionless
Reliability	Reliable (guarantees delivery)	Unreliable (no guarantee)
Speed	Slower	Faster
Error checking	Yes	Minimal
Order	Maintains order	No ordering
Use case	Web browsing, email, file transfer	Video streaming, online gaming, VoIP

Important Questions

Q1. What is TCP/IP? Why is it important?

TCP/IP (Transmission Control Protocol/Internet Protocol) is the fundamental communication protocol of the Internet. TCP ensures reliable, ordered delivery of data packets, while IP handles addressing and routing. It is important because it provides the rules that enable all Internet communication. Without TCP/IP, devices would not be able to communicate over the Internet.

Q2. Differentiate between HTTP and HTTPS.

HTTP transfers data in plain text without encryption, making it vulnerable to interception. HTTPS encrypts data using SSL/TLS before transmission, ensuring security and privacy. HTTPS uses port 443 while HTTP uses port 80. HTTPS is indicated by a padlock icon and is required for banking, shopping, and login pages.

Q3. Explain the role of DNS in Internet communication.

DNS (Domain Name System) acts as the phone book of the Internet. It translates human-readable domain names like google.com into machine-readable IP addresses like 142.250.195.46. When you type a URL in your browser, DNS resolves the domain name to an IP address so your computer can connect to the correct server.

Q4. Differentiate between POP3 and IMAP.

POP3 downloads emails from the server to the local device and typically deletes them from the server, making them accessible from only one device. IMAP keeps emails on the server, allowing access from multiple devices. POP3 requires Internet only for downloading, while IMAP requires Internet for reading. IMAP is better for users who access email from multiple devices.

Quick Revision

TCP/IP = foundation protocol of the Internet
HTTP = web pages (port 80); HTTPS = secure web pages (port 443)
FTP = file transfer (ports 20, 21)
SMTP = sending email (port 25)
POP3 = downloading email (port 110); IMAP = accessing email on server (port 143)
DNS = converts domain names to IP addresses (port 53)
DHCP = auto-assigns IP addresses
SSH = secure remote access (replaces Telnet)
TCP = reliable, ordered; UDP = fast, unreliable
IPv4 = 32-bit; IPv6 = 128-bit

Frequently Asked Questions

What is the difference between HTTP and HTTPS?

HTTP sends data in plain text — anyone on the network can read it. HTTPS wraps HTTP in TLS encryption, so the connection between your browser and the server is encrypted end-to-end. HTTPS also authenticates the server using a certificate, so you know you're talking to the real google.com and not an imposter. Modern browsers mark HTTP sites as "Not secure" to push everyone to HTTPS.

What port does each protocol use?

Protocol	Port	What it does
HTTP	80	Web pages (unencrypted)
HTTPS	443	Web pages (encrypted)
FTP	20, 21	File transfer
SSH	22	Secure remote login
SMTP	25 (or 587 with TLS)	Sending email
DNS	53	Domain name lookup
DHCP	67, 68	Auto IP address
POP3	110 (or 995 with TLS)	Downloading email
IMAP	143 (or 993 with TLS)	Accessing email

Ports below 1024 are "well-known ports" reserved for these standard services.

Is HTTP/3 different from HTTP/2?

Yes. HTTP/2 runs on top of TCP; HTTP/3 runs on top of QUIC (which is built on UDP). HTTP/3's main wins are faster connection setup (zero round trips for repeat connections), better mobile performance (no head-of-line blocking when packets are lost), and built-in encryption. Google, Cloudflare, and Facebook already serve a large fraction of traffic over HTTP/3.

What is DNS and how does it work?

DNS (Domain Name System) is the Internet's phone book. When you type youtube.com, your computer asks a DNS resolver: "what IP address is youtube.com?" The resolver asks the root name server, then the .com server, then YouTube's name server, and finally returns an IP like 142.250.195.46. Your browser then opens a connection to that IP. The whole lookup usually takes 10-50 ms and is cached aggressively.

Why are emails sent with SMTP but received with POP3 or IMAP?

SMTP is push-based: your mail server pushes outgoing email to the recipient's server. POP3/IMAP are pull-based: your client pulls email from your server when you ask. Different jobs need different protocols. SMTP is the post-office handing off mail to the next post office; POP3/IMAP is you walking to your mailbox to collect what's waiting.

What is the difference between TCP/IP and OSI?

OSI is a 7-layer reference model (Physical, Data Link, Network, Transport, Session, Presentation, Application). TCP/IP is the 4-layer model the actual Internet uses (Link, Internet, Transport, Application). OSI is the textbook ideal; TCP/IP is what's running. Most "OSI vs TCP/IP" exam questions are about the layer mapping: OSI's top 3 layers all collapse into TCP/IP's Application layer.

What does FTP do that HTTP can't?

In practice, very little — HTTP can transfer any file. Historically, FTP had two advantages: dedicated commands for navigating directories (LIST, CWD, etc.) and resumable uploads. But FTP is plain-text by default (passwords visible on the wire) and modern alternatives (SFTP, HTTPS, cloud storage APIs) have replaced it almost everywhere. New systems should not use plain FTP.

What is the difference between a URL, URI, and URN?

URL (Uniform Resource Locator) = an address that tells you where something is and how to get it: https://example.com/page. URI (Uniform Resource Identifier) = a broader term that includes URLs AND URNs. URN (Uniform Resource Name) = a name that identifies a resource without specifying location: urn:isbn:0451450523. In daily speech, "URL" and "URI" are often used interchangeably.

Is the Internet the same as the World Wide Web?

No. The Internet is the global network of connected computers. The World Wide Web is just one service running on the Internet — the system of linked web pages accessed via HTTP. Email, video calls, gaming, file sharing, and DNS are all separate services on the same Internet. The Web is what most people see, but it's not the only thing happening.