CapPo
Sign-in page? I know a guy.
Keep encrypted DNS on, and still sign in to Captive Portals (hotel, library and café Wi-Fi).
Encrypted DNS, with no exceptions
You've set Windows to encrypted DNS (DNS over HTTPS, e.g. NextDNS or Cloudflare), with fallback to plain DNS turned off. Then you join hotel Wi-Fi, and the sign-in page never appears: the network blocks encrypted DNS until you sign in, and you can't sign in without its DNS. Without CapPo, you're left with three choices, and each one weakens the protection:
- Allow fallback to plain DNS. Your lookups leak exactly on strange networks, where it matters most.
- Turn encrypted DNS off for new networks. Then it only protects you at home.
- Keep exceptions by hand. Turn it off, sign in, and remember to turn it back on. Every time.
CapPo doesn't encrypt anything itself: Windows does. CapPo is the reason you can leave it on. It notices the sign-in page, opens it in its own window, and closes the window once you're online.
Makes captive portals an offer they can't refuse.
How it works
- The network's DNS, inside the sign-in window only. CapPo reads the DNS servers the network handed out (DHCP) and runs a small proxy on your PC (127.0.0.1) that looks names up with them. Only CapPo's sign-in window uses that proxy. Everything else keeps using your encrypted DNS.
- Your system DNS is never touched. CapPo doesn't change Windows' DNS settings, and it needs no administrator rights.
- It checks the way Windows does. CapPo fetches Microsoft's connectivity test page through its proxy. If something else answers, a portal is in the way. It also supports networks that announce their portal (RFC 8910 / RFC 8908).
- It notices when you're through. Once you're online, CapPo closes the window and flushes Windows' DNS cache, which still holds the failed lookups from before. Later it checks again, for portals that capture you again when a session runs out.
Always running, or on demand
CapPo can stay in the notification area and react to network changes at once. Or it can stay out of the way: Windows starts it when a network connects, for a check that takes about a second, and you only see it when there's a sign-in page.
Do you need it?
Windows 11 keeps DNS settings per Wi-Fi network, so where you set encrypted DNS decides it:
| Where encrypted DNS is set | On a new hotel network | CapPo |
|---|---|---|
| For all Wi-Fi networks, unencrypted fallback off | The sign-in page never loads | Needed |
| By policy, "Require DoH" (Group Policy or Intune) | Same | Needed |
| Only for your home network | The page loads, but nothing you look up there is encrypted | Not needed |
| Any network, unencrypted fallback allowed | The page loads, and anyone who can block encrypted DNS can switch you to plain DNS | Not needed |
CapPo is for Windows' built-in encrypted DNS. Apps that take over DNS themselves (VPNs, DNS filtering apps) have their own ways around portals.
Get it
| Microsoft Store | GitHub | |
|---|---|---|
| Price | Paid, with a free trial | Free |
| Updates | Automatic | Manual |
| Code signed | Yes | No (Windows may warn you the first time) |
| License | GPL-3.0 | GPL-3.0 |
Both are built from the same code and work the same way. The Store version is how you can support development if you like it; the GitHub version has no license checks, reminders or limits.
Needs Windows 10 version 2004 or later, or Windows 11. The sign-in window uses the Microsoft Edge WebView2 Runtime, which comes with Windows 11.