Captive portal test URL
One plain-HTTP address you can open, curl, or embed in docs to wake up captive portals.
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 |
Bookmark the universal trigger
Captive portals expect a simple HTTP request. Loading nossl.sh gives gateways that exact handshake so they can redirect you to their login screen.
- Works on laptops, phones, kiosks, and embedded devices.
- Lightweight markup loads even on throttled guest Wi-Fi.
- Counters prove the request landed if support asks.
Use it in scripts and training
Share the URL with teammates or wrap it in curl commands when you need repeatable captive portal tests.
- curl http://nossl.sh
- curl -i "http://nossl.sh/status/302?location=http://example.com"
- Fetch /api/request-info for JSON snapshots.
Why does the test URL avoid HTTPS?
HTTPS requests are hard to intercept, so captive portals often ignore them. HTTP ensures the gateway can catch the request and show the splash page.
Will this link change over time?
No. http://nossl.sh is maintained as a stable, plain-HTTP endpoint you can rely on during onboarding or documentation.
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