KFC Wi-Fi login steps
Use nossl.sh to get the Colonel’s Wi-Fi portal to appear and verify you are clear to browse.
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 |
Kick off the captive flow
Load nossl.sh to send a plain HTTP request that typically triggers the KFC splash page.
- Confirms DNS and routing from the restaurant network.
- Provides a timestamped record for the store manager.
- Helps identify blockers like content filters.
If the splash loops
Disable private relay, refresh the page, and check the scheme indicator for signs of HTTPS interception.
Can I test with curl?
Yes. `curl http://nossl.sh` returns your IP only—handy for CLI validation while on KFC Wi-Fi.
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