Connect your iPhone to Wi-Fi
Use nossl.sh as a lightweight captive portal trigger plus troubleshooting checklist.
Connection report
Headers
Request headers
10 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-kvcjn (squid/6.13) |
| x-forwarded-for | 216.73.216.118 |
| x-forwarded-proto | http |
| x-real-ip | 216.73.216.118 |
Before you open nossl.sh
Turn off Private Relay, disable VPNs, and forget any stale network profiles. Then join the Wi-Fi again.
What to look for on the page
Check that the status shows “Unsecure connection.” If it reports HTTPS, your phone may still be tunneling traffic.
- Confirm the IP matches the venue range.
- Tap copy to send headers to support.
- Reload after login to ensure the scheme flips to HTTP.
Do I need to disable content blockers?
Temporarily disable Safari content blockers until after you authenticate—they can block captive scripts required for 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