nossl.sh

Forever plain HTTP. No TLS. No HTTPS.

HTTP-only disclaimer

nossl.sh will always, forever, infinitely stay plain HTTP - no SSL, no TLS, no HTTPS - on purpose.

nossl.sh exists to surface captive portals and inspect network behavior. To keep that predictable, everything here lives on raw port 80 with zero TLS, zero HSTS, and zero HTTPS redirects.

  • No SSL certificates now or later; no TLS handshakes or HTTPS endpoints at all.
  • No auto-redirects, no mixed modes, no accidental HSTS or preload flags.
  • Purpose-built for portal triggers, header checks, and IP lookups - not for sensitive data.

Current connection: HTTP. You are already on the intended plain HTTP path.

Why stay HTTP-only?

Captive portals and strict firewalls often block TLS handshakes, hide SNI, or break HSTS preloads. Staying on plain HTTP keeps splash screens, login prompts, and diagnostics predictable for every device.

What you should expect

  • No encryption. Everything you send can be observed by the network.
  • If a client forces HTTPS, that client or your network is rewriting the request.
  • APIs such as /api/request-info remain HTTP-only as well.

Keep working

Main diagnostics

See your live IP, headers, and counters on the HTTP-only dashboard.

[ OPEN MAIN PAGE ]

JSON snapshot

Grab your current scheme, IP, and headers via the API for scripts or support.

[ CALL /api/request-info ]