Skip to content
AdminKit

CoAP

What is CoAP?

CoAP (Constrained Application Protocol, RFC 7252) is a lightweight, RESTful protocol for low-power IoT and sensor devices, running over UDP instead of a full HTTP/TCP stack, often without its optional DTLS encryption enabled. AdminKit's port check tool can confirm whether a device's CoAP port is reachable from the internet, where it is a known DDoS amplification target.

By AdminKit team, Netbase JSC · Updated

CoAP (Constrained Application Protocol, RFC 7252) is a lightweight, RESTful protocol built for low-power IoT and sensor devices, modeled on HTTP’s GET/PUT/POST methods but running over UDP for a much smaller footprint than a full HTTP/TCP stack. It supports an optional encrypted and authenticated mode, DTLS, but ships and is frequently deployed without it enabled. Because CoAP runs over UDP and a small request to its resource-discovery endpoint can trigger a disproportionately large response, an exposed CoAP service is attractive for DDoS amplification attacks — an attacker spoofs a victim’s IP as the source and lets the amplified responses flood that victim, a pattern researchers have documented at scale since 2019, with hundreds of thousands of exposed devices found in internet-wide scans. The nonprofit Shadowserver Foundation tracks this exposure in its Accessible CoAP Report, which identifies devices with CoAP accessible on port 5683/UDP. CoAP’s resource-discovery endpoint and other protocol options are listed in IANA’s CoRE parameters registry. The device itself can also be at risk, independent of its use in an attack on someone else — AdminKit’s guide on checking whether port 5683 is exposed and its port check tool both confirm reachability from the internet directly.

CoAP’s exposure risk mirrors other lightweight device protocols AdminKit tracks: MQTT is also built for constrained devices and commonly ships with no authentication, while DNP3 is the equivalent story on the industrial-control side.

AdminKit groups coAP under its machine protocols cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Is CoAP the same as MQTT?

No -- both are lightweight IoT protocols, but CoAP is a RESTful, UDP-based protocol modeled on HTTP methods, while MQTT is a publish-subscribe protocol that normally runs over TCP; they solve similar problems differently and aren't interchangeable.

Does CoAP encrypt its traffic?

Only optionally -- CoAP supports an encrypted and authenticated mode called DTLS, but devices frequently ship and get deployed with it disabled.

Why is an exposed CoAP device a DDoS risk to others, not just itself?

Because CoAP runs over UDP and a small request to its resource-discovery endpoint can trigger a disproportionately large response, attackers spoof a victim's IP as the source so the amplified replies flood that victim instead of the attacker -- a pattern researchers have documented at scale since 2019.

How do I check if my device's CoAP port is exposed?

AdminKit's guide on checking port 5683 walks through confirming whether a device's CoAP port is reachable from the internet.