Passkeys for WordPress admins: how they work and when to use them
Passkeys replace the password with a key your phone or laptop keeps, bound to your site's domain. Why that defeats phishing, and what to watch out for.
Two-step login stops most attacks on WordPress accounts, but it has one weak spot: a convincing fake login page can ask for the code too, and pass it on to the real site within seconds. Phishing kits that do exactly that are common.
Passkeys close that gap. They are now supported by every major operating system and browser, and they are easier to use than passwords, which is rare for a security feature.
What a passkey is
A passkey is a pair of cryptographic keys. When you register one with a website, your device creates the pair, keeps the private key, and gives the site only the public key. When you sign in, the site sends a random challenge; your device signs it with the private key after you unlock it with your face, fingerprint or device PIN, and the site checks the signature with the public key it stored.
The standards behind this are WebAuthn, published by the W3C, and the FIDO Alliance's CTAP protocol for talking to authenticators such as phones and security keys. "Passkey" is the friendly name the industry settled on.
Why phishing stops working
Each passkey is tied to the domain it was created for. The browser will only offer the passkey for yoursite.com on yoursite.com. On yoursite-login.com, a perfect copy of your login page, there is simply nothing to use, and there is no code for you to type in by mistake.
The site also never stores anything secret. If its database leaked, attackers would get public keys, which are useless for signing in.
Synced or device-bound
Most passkeys today are synced: Apple, Google and Microsoft store them in the user's account and make them available on all of that person's devices. That solves the "I lost my phone" problem for most people.
Device-bound passkeys live on one device or a hardware security key and never leave it. They are the stronger choice for accounts that would be very damaging to lose, at the cost of needing a backup key.
What to watch out for
- Recovery is the weak point. If losing a passkey can be fixed by an emailed link, the account is only as safe as that inbox. Keep a second sign-in method, such as an authenticator app, and a second administrator.
- Shared accounts do not fit. Passkeys belong to a person. If several people share one admin login, give each of them their own account first. You should anyway.
- Not everyone is ready. Older devices and some corporate setups lag behind. Offer passkeys as the better option, alongside two-step login, rather than forcing them on day one.
- They protect the login, not the session. A malicious plugin or a stolen session cookie bypasses any login method.
Getting started
- Make sure two-step login is already working, as the fallback.
- Register a passkey for your own administrator account on the device you use most.
- Register a second one on another device or a security key.
- Invite other administrators, then editors.
In Ironhelm
Passkeys let people sign in with Face ID, Touch ID, Windows Hello or a security key instead of a password, and count as two-factor login. They work alongside authenticator-app codes, so nobody is locked out while they switch.
Sources
- FIDO Alliance, How FIDO works
- FIDO Alliance, Passkeys
- W3C, Web Authentication: An API for accessing Public Key Credentials, Level 2
- Trail of Bits, The cryptography behind passkeys (May 2025)
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.