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 |
How to use this page
Plain HTTP for quick checks
See your real IP, request method, and headers without HTTPS in the way. Great for captive portals, firewall tests, or debugging VPN/proxy quirks.
- Open http://nossl.sh to trigger captive portal pages.
- Share a snapshot link if support needs proof.
Need step-by-step help? Browse the full guide index for hotels, cafes, and mobile walkthroughs.
cURL examples
cURL IPv4/IPv6, any HTTP status
cURL your public IP - the alternative to ifconfig.me.
$ curl http://nossl.sh
→ 216.73.216.63
cURL your IPv6:
$ curl http://v6.nossl.sh
→ ipv6
Check any HTTP status:
$ curl -i http://nossl.sh/status/418
→ HTTP/1.1 418 I'm a Teapot
API references:
- /api/request-info — current IP, scheme, headers.
- /api/counters — request counters snapshot.
- /api/honeypot — honeypot hits as JSON.
- /status/:code — return any HTTP status; add
?location=for redirects.
Need the honeypot console? Visit the /honeypot dashboard.
FAQ
Why plain HTTP?
- Why no TLS?
- Captive portals and restrictive networks often block HTTPS handshakes. HTTP keeps the splash page visible.
- What can I use this for?
- Spot VPN or proxy issues, capture headers for debugging, and confirm whether the network is online.
- Is there an API?
- Yes — use the request info endpoint for JSON.