Vol. I · No. 46The protocol sectionSat, 10 Oct 2026
Layer 4 · Transport protocol

UDP

the User Datagram Protocol

UDP is the fire-and-forget transport. It wraps data in a tiny header and sends it, with no handshake and no acknowledgements — and no promise it will arrive. What it trades away in safety it wins back in speed.

UDP sends datagrams with no setup and no guarantees — fast, thin, and best-effort.

You can run this one

Open the UDP lab →

No handshake, no guarantees. Four datagrams on a clean wire, then one that vanishes—and nobody reports it.

Beginner
Operates at
Layer 4
Transport
Protocol number
IP 17
rides on IP
Delivery
Best-effort
no ordering, no ACK
Connection
Stateless
no handshake

How it works

No handshake — just send and hope
SenderReceiver
Datagramjust the data, addressed to a port
Datagramnext one — no waiting for a reply
Datagram lostno retransmit — it’s simply gone
No connection, no ACK, no order — if it matters, the application must handle it
The whole header is just 8 bytes
016 bits31
Source port
Destination port
Length
Checksum
Data — the bytes being carried

Four small fields, then the data. There’s nothing to set up and nothing to remember — which is exactly why UDP is so fast and so cheap.

The main points

What UDP does, step by step

1
Skip the handshake

There’s no connection to open — the first packet is the data, sent immediately.

2
Wrap in a tiny header

Just source and destination ports, a length and a checksum — eight bytes in all.

3
Send and forget

The datagram goes out with no acknowledgement; a lost one is simply gone.

4
Leave the rest to the app

If order or reliability matter, the application (or a layer like QUIC) adds them on top.

In cybersecurity

Having no handshake makes UDP fast — and makes it trivial to spoof and a favourite tool for amplification attacks.

Amplification / reflection

A small spoofed request draws a huge reply to the victim — DNS and NTP are classic amplifiers.

Easy source spoofing

With no handshake to complete, the source address is never verified.

No confidentiality

UDP is plaintext — secure it with DTLS or ride it under QUIC.

Flood attacks

Stateless floods are cheap to send and hard to filter without rate limits.

Firewall handling

With no connection to track, stateful firewalls treat UDP with cruder rules.

Quiet scanning

Closed ports may not reply at all, so UDP scans are slow but stealthy.

Rides in the stack

IPUDPDNS, RTP, QUIC, …

Works with

TCPQUICDNS

See it on Linux

dignslookuphostssncnetstattraceroutemtrnmaptcpdumpnftiptablesufw

TCP or UDP?

TCPUDP
SetupHandshakeNone
ReliabilityGuaranteedBest-effort
OrderKeptNot kept
Best forWeb, mail, filesVoice, video, games