ProtoStackv0.1

Interactive Protocol Visualizer

Security & AuthProfessional trackAdvancedOSI: Application LayerDefault Port: 443 (HTTPS)Standard: RFC 8555

ACME

— Automatic Certificate Management Environment

ACME automates the entire certificate lifecycle for TLS servers. A client proves control of a domain to a certificate authority, submits a certificate signing request, and receives a signed X.509 certificate that can be renewed without human intervention.

Read first: HTTP / HTTPS, TLS 1.3Content reviewed 2026-11-18

Interactive Session: How ACME Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

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

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

Domain validation hijack

Spoofing

Control of the HTTP-01 path or DNS zone lets an attacker obtain a certificate for a domain they do not own.

Attackersimulated
ACMEtarget
Attack step 1 of 3
Take the validation path

The attacker gains control of the web root or DNS records.

What a defender can see

Unexpected changes to .well-known or DNS.

Impact if unmitigated

Trusted certificate misissuance for the domain.

Defences that matter
  • CAA records limiting issuers
  • DNS-01 with a secured zone
  • Certificate Transparency 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

  • JSON messages exchanged over HTTPS with replay protection through one-time nonces
  • Domain validation challenges such as http-01, dns-01, and tls-alpn-01
  • Account key pairs used to sign every request with JWS instead of passwords
  • Standardized order, authorization, and finalize resources for automated renewal

Real-World Use Cases

  • Free and automated TLS certificates from Let's Encrypt
  • Large fleets of web servers renewing certificates unattended
  • Internal PKI issuing certificates for service meshes and appliances

Advantages & Strengths

  • Removes manual CSR and renewal work from operations teams
  • Short-lived certificates reduce the impact of key compromise

Limitations & Vulnerabilities

  • The client needs a reachable HTTP endpoint or DNS API access for validation
  • Rate limits at public certificate authorities can block large bulk issuances