HTTP status code tester
Call /status/:code to simulate responses and redirects over plain HTTP.
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 |
Simulate responses in one call
Need to see how a browser, client, or load balancer reacts to a code? Hit /status/503, /status/418, or any code from 100-599.
Bodies are omitted for 1xx, 204, and 304 so they match real servers.
- curl -i http://nossl.sh/status/418
- curl -i http://nossl.sh/status/204
- Cache-control disabled so every request is fresh.
Test redirects with Location
Add a location query parameter to set the Location header on 3xx codes. Useful for SSO flows, CDN rules, or captive portal rewrites.
- curl -i "http://nossl.sh/status/302?location=https://example.com"
- Supports 300, 301, 302, 303, 307, 308 status codes.
- Plain HTTP keeps captive portals and proxies from blocking the test.
What input is allowed?
Status codes must be integers between 100 and 599. Location values are sanitized to strip newlines before returning.
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