Forcing the Wi-Fi Login Page
Use plain HTTP to make captive portals like NeverSSL and nossl.sh appear.
Use plain HTTP to make captive portals like NeverSSL and nossl.sh appear.
Live snapshot
IP address
IPv6 address
IPv6 address
🇺🇸 United States
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 |
Captive portals work by intercepting your first web request and redirecting you to a login page. However, they can only intercept unencrypted, plain HTTP traffic.
Modern websites almost all use HTTPS, which is encrypted. If you try to visit an HTTPS site, the captive portal cannot intercept it, and the login page will never appear.
Sites like neverssl.com and nossl.sh are intentionally served over HTTP, giving the captive portal a request it can redirect.
If the login page does not appear, try disabling any VPN or private relay service you might be using. These services can also prevent the captive portal from intercepting your traffic.
You can also try "forgetting" the Wi-Fi network and reconnecting.
For the purpose of triggering a captive portal, yes. These sites are not designed for sensitive information. Once you have logged in through the portal, you should use secure, HTTPS websites as usual.
Both serve the same purpose. nossl.sh provides additional diagnostic information about your connection, which can be helpful for troubleshooting.
Open the official Apple CNA page to force the captive assistant on iOS and macOS devices.
Open Apple captive portalUse the Android connectivity check URL that devices call before presenting the portal dialog.
Open Android captive portal