IMAP
— Internet Message Access ProtocolIMAP enables email clients to access and manipulate messages stored on a remote mail server. Unlike POP3 which downloads and deletes, IMAP synchronizes folders, read/unread states, and flags across multiple devices simultaneously.
Interactive Session: How IMAP Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of IMAP.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
Credential stuffing
Credential attackPasswords leaked from another breach are replayed against IMAP, which often lacks MFA.
Reuse leaked credentials
The attacker tries email/password pairs from a breach list.
Many failed logins across distinct accounts.
Mailbox takeover and downstream account resets.
Defences that matter
- MFA and OAuth-based mail access
- Block legacy authentication
- Rate limiting and impossible-travel alerts
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
- Two-way multi-device state synchronization
- Server-side mailbox folders and message search
- Partial message fetching (fetch headers without large attachments)
- IDLE command (RFC 2177) for real-time push email notifications
Real-World Use Cases
- Smartphone and desktop email clients syncing a shared mailbox
- Webmail interfaces (Gmail, Outlook, Roundcube)
Advantages & Strengths
- Access all emails from phone, laptop, and webmail simultaneously with identical state
Limitations & Vulnerabilities
- Requires significant server-side disk storage and memory for large mailboxes