ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
IMAPLDAP
Application LayerProfessional trackBeginnerOSI: Application LayerDefault Port: 110 / 995Standard: RFC 1939

POP3

— Post Office Protocol version 3

POP3 was engineered in the early Internet era when continuous network connectivity and server storage were limited. It connects to the mailbox, downloads all messages to the local machine, marks them for deletion on the server, and disconnects.

Read first: TCPContent reviewed 2026-11-18

Interactive Session: How POP3 Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of POP3.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

Cleartext credential capture

Interception

POP3 without TLS sends usernames and passwords in plaintext across the local network.

Attackersimulated
POP3target
Attack step 1 of 3
Capture the session

The attacker sniffs the network during a mail check.

What a defender can see

POP3 traffic on port 110 instead of 995.

Impact if unmitigated

Credential theft and mailbox compromise.

Defences that matter
  • Require POP3S on port 995
  • Disable plaintext authentication
  • Network segmentation and MFA

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • Store-and-forward single-client retrieval model
  • Port 110 (plaintext) and Port 995 (POP3S over TLS)
  • Basic commands: USER, PASS, STAT, LIST, RETR, DELE, QUIT
  • Minimal server resource requirements

Real-World Use Cases

  • Offline email reading on a single primary computer
  • Conserving server storage by offloading all messages locally

Advantages & Strengths

  • Extremely simple protocol with tiny server storage footprint

Limitations & Vulnerabilities

  • Cannot synchronize read/unread states or folders across multiple devices; risk of losing emails if the client drive fails