If a public Wi-Fi login page will not appear, use your device’s network sign-in prompt first. If that does not work, open http://neverssl.com in a browser. Its plain HTTP connection can let the network redirect you to its sign-in page. This can help at hotels, airports and cafés, but there is no single login address that works on every network.
Last updated:

Try these steps in order
- Confirm the network name with the venue. Connect to its actual guest network, not a similarly named hotspot.
- Look for a sign-in notice. Windows or Android may show “Sign in” or “Action needed.” Open that prompt.
- On iPhone or iPad, reopen Wi-Fi settings. Tap the network, or its information button and Join Network where offered. Apple’s captive Wi-Fi guide explains these controls.
- Try a plain HTTP page. Type
http://neverssl.comdirectly in the address bar. Includehttp://so it is an address rather than a search. - Complete the venue’s login. Read the address and the terms before entering the details it requests.
- Check an ordinary HTTPS website afterward. If it opens normally, the sign-in probably completed.
NeverSSL deliberately uses an unencrypted page to help trigger these network redirects. You do not enter your Wi-Fi password into NeverSSL itself.
Why is Wi-Fi connected but the internet blocked?
Connecting to the access point and getting internet access are separate steps. A guest network may require you to accept terms, enter a room code or complete another sign-in step. Until then, the connection can show as connected while normal browsing fails.
An HTTPS page is a poor target for a network to silently replace with a different login page. The network’s own sign-in window or a simple HTTP request can help bring up the portal without asking you to ignore a certificate warning.
If the portal still does not open
| What happens | What to try |
|---|---|
| No sign-in prompt appears | Disconnect and reconnect, then reopen the network’s settings. |
| The same old login page keeps returning | Close that tab, reconnect and request a fresh sign-in page. |
| Only one device fails | Compare it with another device on the same guest network, if available. |
| A managed VPN or security tool blocks access | Use its approved captive-portal process or ask your administrator. |
| Every device fails | Ask the venue whether its guest internet or login system is down. |
You can also forget the guest network and join again, provided you still have the details needed to reconnect. Do not forget a managed network or change work security settings without the relevant instructions.
Do localhost or random router addresses help?
localhost and addresses in the 127.x.x.x range point back to your own device. They are not general hotel Wi-Fi login addresses. Nor is a guessed address such as 192.168.1.1 guaranteed to belong to the venue’s portal.
If the venue provides a specific portal address, use that. Otherwise, follow the network prompt or ask staff for the correct address rather than trying lists of unrelated IP addresses.
Check the login page before using it
- Confirm the expected network and sign-in details with the venue.
- Do not ignore a certificate error to submit passwords or payment details.
- If a page asks you to install software or a certificate, ask why before continuing.
- Use a trusted connection for sensitive tasks if you cannot verify the guest network.
A prefix such as www2 alone does not prove that a portal is real or fake. Our WWW2 address guide explains what to check. If you are typing a settings address into Chrome instead, our Chrome address guide explains the difference between a browser page and a website.