Fix Apple captive portal issues
Works with iPhone, iPad, and macOS to trigger the login screen when the captive assistant fails.
Live snapshot
Connection report
IP address
IPv6 address
IPv6 address
🇺🇸 United States
Headers
Request headers
8 headers
| Header | Value |
|---|---|
| accept | */* |
| accept-encoding | gzip, br, zstd, deflate |
| cache-control | max-age=259200 |
| connection | close |
| host | nossl.sh |
| user-agent | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com) |
| via | 1.1 squid-proxy-5b5d847c96-788gb (squid/6.13) |
| x-forwarded-for | 216.73.216.63 |
When the captive assistant stalls
Open Safari and load nossl.sh directly. The site provides the HTTP handshake that macOS and iOS expect from Apple's original test domains.
Share diagnostics with IT
Export the JSON headers and send them to your help desk so they can compare against Apple CNA behavior.
Can I reset the Apple captive portal cache?
Toggle Wi-Fi off and on, forget the network, or reboot the device. Loading nossl.sh after that sequence usually forces a fresh login.
Quick steps to trigger captive portals
Apple captive portal check
Open the official Apple CNA page to force the captive assistant on iOS and macOS devices.
Open Apple captive portalAndroid captive portal check
Use the Android connectivity check URL that devices call before presenting the portal dialog.
Open Android captive portal