How to spot a fake login page before you type your password

Close-up of the Google homepage on a screen showing search options.

Photo by Sarah Blocksidge on Pexels

A fake login page is built for one purpose: to capture your username and password the moment you type them. The page looks like a real sign-in screen for Google, Microsoft, your bank, or whatever service an attacker has decided to impersonate. Submit your credentials and they go straight to the attacker, not the site you thought you were using. The real site never sees you.

This kind of attack sits inside a broader category of phishing emails and online scams, but fake login pages deserve their own attention because the visual deception is so good. Modern credential-phishing kits can replicate a corporate login screen in minutes, including logos, fonts, and even working password-reveal toggles. Spotting them isn't about looking harder. It's about knowing where to look.

Check the address bar first, every time

The URL is the single most reliable signal. Attackers can copy every pixel of a login page, but they can't take ownership of a domain they don't control. Before typing anything, read the full address in your browser's address bar.

The real Microsoft login lives at login.microsoftonline.com. A fake version might sit at login-microsoftonline.com, microsoftonline.com.auth-verify.net, or something like microsoft-secure-login.pages.dev. The brand name appears in all three, which is exactly the point. Train yourself to read from the right side of the domain: the registrable domain is the part just before the first single slash. Everything to the left of it is a subdomain the attacker can set to anything.

Three specific patterns to watch for:

  • Extra words inserted around a brand name (paypal-verify.com, secure-apple.com)
  • The real brand name used as a subdomain (google.com.phish-domain.xyz)
  • Lookalike characters that swap one letter for a visually similar one, like a lowercase "l" for a capital "I"

HTTPS doesn't mean the site is legitimate

A padlock icon in the address bar tells you the connection is encrypted. It says nothing about who owns the site. Attackers routinely obtain free TLS certificates from services like Let's Encrypt for their phishing domains. The padlock on a fake login page is real. The site behind it isn't.

This is worth repeating plainly: HTTPS confirms encryption, not identity. Stop using the padlock as a trust signal. Use the domain name instead.

Watch how you arrived at the page

How you got to a login page matters as much as what it looks like. Legitimate services don't send you an urgent email and ask you to log in through a link to verify your account, confirm a payment, or avoid suspension. That pattern is the attack. The email creates panic; the link delivers the fake page.

If a message pushed you toward a login screen, don't use the link. Open a new browser tab, type the site's address directly, or use a bookmarked URL you saved previously. That way you know exactly where you're going. This is especially relevant for Microsoft 365 users: securing your Microsoft 365 account starts with not logging in through links you didn't initiate yourself.

Use a password manager as a passive detector

A password manager autofills credentials only when the domain in the address bar matches the domain the credentials were saved for. If you land on a fake login page and your password manager doesn't autofill, that's a warning. The manager saw something the domain didn't match.

This isn't foolproof, but it adds a layer of verification that doesn't require any active attention from you. The mismatch surfaces automatically. It won't catch every case, but it catches the majority of credential-phishing attacks that rely on slightly altered domains.

Enable two-factor authentication, then understand its limits

Two-factor authentication (2FA) makes credential theft harder. If your password is captured on a fake login page, the attacker still needs the second factor to get in. For most attack kits, that creates a window you can close. Set up 2FA on every account that offers it. Two-factor authentication stops most account takeovers that a stolen password would otherwise allow.

That said, real-time phishing proxies can relay your 2FA code in the same session, before it expires. These attacks are more sophisticated and less common, but they exist. Don't treat 2FA as a complete substitute for verifying the domain. It's a second layer, not a replacement for the first one.

What to do if you've already typed your credentials

Speed matters. If you submitted credentials on a page you now suspect was fake, change your password on the real site immediately using a separate, trusted device or connection. Then check whether the account shows any recent login activity you don't recognise. If the service supports it, revoke all active sessions from the account settings panel.

If the compromised account uses the same password anywhere else, change those too. Password reuse is what turns a single phishing capture into several compromised accounts.

Report the fake page to your browser vendor. Both Google Safe Browsing and Microsoft Defender SmartScreen accept user-submitted phishing reports. Those submissions help get the page blocked faster for everyone else.

Keep the habit consistent

Fake login pages work because they catch people in a moment of distraction or urgency. Attackers engineer both. The habit that defeats them is boring and takes about three seconds: read the domain in the address bar before you type. Not the padlock. Not the logo. The domain. Do that every single time and most credential-phishing attempts stop working against you.