Skip to content
See the demoStart free
Networking

What is CAPPORT?

Definition

CAPPORT is an IETF standard that lets a network tell a device, in a structured way, that it is behind a captive portal, where the login page is, and what the session state is. It replaces the guesswork of connectivity probes with an explicit API, giving operating systems accurate portal prompts and session information.

The problem it solves

For years, devices discovered captive portals by accident. The operating system would request a known URL, expect a specific response, and infer from anything unexpected that a portal was in the way. It works often enough to have become universal, but it is fragile: HTTPS breaks interception, DNS-over-HTTPS bypasses the network resolver, and the device has no way to learn how much time or data is left in a session. CAPPORT defines a proper channel instead, in the IETF's RFC 8908 Captive Portal API (2020) and its companions RFC 8910 and RFC 8952. The network advertises an API endpoint during address configuration, and the device queries it directly.

What the API returns

The endpoint responds with a small JSON document describing whether the device is currently captive, the URL of the portal page to open if it is, and optionally when the session expires or how much data remains. That last part is the meaningful upgrade for guests: instead of a session silently dying and traffic mysteriously stopping, the device can surface remaining time or data in the system interface. It also means the portal prompt appears reliably and closes when authorisation actually completes.

Where it stands today

Support is arriving gradually. Major mobile platforms have implemented parts of the specification and several network vendors expose the API, but the installed base of hardware and firmware in real venues moves slowly. In practice a portal in 2026 should support CAPPORT where the hardware allows while continuing to work correctly for devices that only do the old probe-based detection. It is an additive improvement to the guest experience, not a replacement for a portal that already behaves well.

Run a guest WiFi login on your own network

VoqadoWiFi runs branded guest portals on TP-Link Omada and Ubiquiti UniFi networks. The Starter plan is free forever: one location, 500 logins a month, consent logging included.

Common questions about capport

Do I need to do anything to use CAPPORT?

It depends on your equipment. The network gear has to advertise the API endpoint and the portal platform has to serve the API responses. Where both are in place it works with no guest-side configuration.

Does CAPPORT replace the splash page?

No. It tells the device where the splash page is and what the session state is. The page itself, along with login and consent, still does the work.

Related terms

CAPPORT rarely comes up on its own. These are the entries operators usually read next.