ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
SNMPFTP
Application LayerProfessional trackIntermediateOSI: Application LayerDefault Port: 25 / 587Standard: RFC 5321

SMTP

— Simple Mail Transfer Protocol

SMTP is used by mail servers and email clients to send messages across networks. While IMAP/POP3 are used to retrieve email from a mailbox, SMTP handles mail delivery between mail transfer agents (MTAs).

Read first: TCP, DNSContent reviewed 2026-11-18

Interactive Session: How SMTP Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

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

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

Sender spoofing and open relay

Feature abuse

A misconfigured mail server relays mail for anyone or accepts a forged sender identity.

Attackersimulated
SMTPtarget
Attack step 1 of 3
Probe for relay

The attacker tests whether the server forwards mail to an external domain.

What a defender can see

Relay attempts and unusual RCPT TO domains.

Impact if unmitigated

Phishing delivery and reputational damage.

Defences that matter
  • Require authentication for submission
  • SPF, DKIM and DMARC enforcement
  • Outbound rate limits and monitoring

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

  • Text-based command/response protocol (HELO, MAIL FROM, RCPT TO, DATA)
  • Port 25 (MTA-to-MTA relay) and Port 587 (Client email submission with STARTTLS)
  • MIME extension support for attachments, HTML body, and Unicode
  • DKIM, SPF, and DMARC authentication integration

Real-World Use Cases

  • Sending transactional emails (password resets, notifications)
  • Inter-server email routing (Gmail to Outlook)

Advantages & Strengths

  • Universal standard for all worldwide email transport

Limitations & Vulnerabilities

  • Inherently lacks sender verification without SPF/DKIM/DMARC, enabling spam spoofing