Two pages say abc8. Which address should you use to sign in?
Use the sign-in page you reach through a trusted route independent of either search result. Before entering a password or code, confirm that the full hostname matches the one you independently verified and that the page uses HTTPS. Stop if the browser shows a certificate or connection warning, or if a redirect takes you to a hostname you haven’t verified.

Read the address on the page that asks for your password
Imagine two search results lead to pages with the same abc8 name, colors, and sign-in button. One result appears to come from a Philippine university website, and the other opens a page that looks familiar. Once the pages finish loading, tap the address bar to reveal the full address. The hostname on the page asking for your password is the one you need to verify.
Links on a university or government site can lead elsewhere, and a compromised page can use an institution’s familiar address to draw readers in. A page about betting that seems out of place on an institutional site is a reason to pause. Check the final destination independently even if you recognize the address where the search result started.
Separate the hostname from the words around it
In the example https://signin.example/abc8, the hostname is signin.example. The /abc8 part comes after the hostname and is part of the page path. In https://abc8.signin.example/, the hostname is abc8.signin.example. Here the brand name appears in the hostname itself, but it still doesn’t establish a relationship with abc8. Both addresses are fictional examples for reading practice.
Give each clue the weight it deserves
| Clue | What it tells you | What to do with it |
|---|---|---|
| Brand name or logo | What the page calls itself. | Check the browser address even when the page looks familiar. |
| Institutional search result | Where the link appears to start. | Check where the browser lands after any redirect. |
| HTTPS | Your browser’s connection to the displayed hostname is encrypted when it loads without a certificate warning. | Verify the hostname separately and stop if the browser warns you about the connection. |
| Exact hostname match | Whether the address matches the one you independently verified for account access. | Compare every part of the hostname before entering information. |
Start over from a route you already trust
Similar spellings and domain endings can make an unfamiliar address look familiar. Compare the full hostname with one you independently verified. Use a bookmark you saved after verifying the address, if you have one. A link labeled “official” on the unfamiliar page, or a second result that leads to the same place, gives you no independent confirmation.
- Leave both forms empty while you compare the addresses. On a phone, expand the address bar so you can see the whole hostname.
- Open your independently verified route in a separate tab. Compare its hostname with the one on the page requesting your credentials, including subdomains, digits, and the ending.
- If either route redirects to a different hostname, verify that final destination before signing in. If you can’t verify it, close the page with the form and leave account access for later.
The address bar identifies the page you’re viewing. The form may send your details to a different address. If the form seems suspicious, leave it empty and use your independently verified route.
Questions that come up at the sign-in screen
What if only the part after the slash is different?
Two paths can lead to different pages on the same hostname. Check that you reached the sign-in page through your verified route and that the hostname still matches when the form appears.
What if a page asks for a one-time code before I can verify the address?
Leave the form empty. A one-time code is sensitive account information. Check the destination independently before sharing it through a form.
What if I already entered something on the page?
If you shared a wallet PIN, MPIN, or one-time code issued by your wallet provider, contact that provider immediately through its independently verified official help channel and request an account freeze. Preserve any evidence you already have, such as screenshots or the suspicious address, without reopening the page or delaying contact. If you shared an abc8 sign-in code, contact abc8 support through an independently verified channel. For a code from another service, contact the service that issued it. If you submitted a password, use a separately verified route to change it on the affected service. If you reused it elsewhere, change it on those services as well.
Make the address your last check
Before entering any account or payment details, including a password or code, check that the page you reached through your independently verified route uses HTTPS and that the full hostname still matches. HTTPS encrypts the connection. Establish the site’s identity through your verified route. If the page uses HTTP, the browser shows a certificate or connection warning, or the hostname is unfamiliar, leave the form empty and close the tab.