NTP
— Network Time ProtocolNTP synchronizes computer system clocks to coordinated universal time (UTC) across variable latency IP networks using a hierarchical system of time sources called clock strata (Stratum 0 atomic clocks down to Stratum 3 servers).
Interactive Session: How NTP Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of NTP.
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.
Time spoofing and monlist amplification
Denial of serviceForged NTP replies shift a client clock, while legacy monlist queries amplify traffic.
Answer a request
The attacker replies to an NTP query with a forged timestamp before the real server.
Clients syncing to an unapproved server.
Authentication failures, log corruption and reflected traffic.
Defences that matter
- NTS or authenticated NTP
- Multiple trusted time sources
- Disable monlist and rate limit NTP
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
- Hierarchical stratum clock model (Stratum 0 to 15)
- Uses UDP port 123
- Jitter and network delay jitter compensation filters
- Slews clock frequency smoothly without sudden time jumps
Real-World Use Cases
- Financial transaction timestamping
- Distributed database log ordering
- TLS certificate validity checks
Advantages & Strengths
- Sub-millisecond accuracy over local LANs
- Robust against packet jitter
Limitations & Vulnerabilities
- Unauthenticated NTP is vulnerable to amplification denial-of-service attacks