← Glossary

Security

What Is WebAuthn? The Web Standard Behind Passkeys and Security Keys

WebAuthn, the Web Authentication API standardised by the W3C, lets websites register and verify public-key credentials created on a user's authenticator, such as a security key or a device's passkey, instead of using passwords.

Key takeaways

What it is

WebAuthn is a web standard, defined by the W3C, that lets a website create and use public-key credentials. When you register, your authenticator, which can be a security key, a phone or a computer, generates a key pair for that site. The site keeps the public key. When you sign in, the site sends a challenge, the authenticator signs it with the private key after you confirm with a fingerprint, face or PIN, and the site verifies the signature.

Why it resists phishing

The specification scopes each credential to a relying party, meaning the site's identity. The browser only lets the authenticator use a credential for the site that created it. A fake site at a lookalike address cannot ask for the real site's credential, because the origin does not match, and there is no code you could type into the wrong page. That is a major improvement over passwords and one-time codes, which can be given away.

What the server stores

The site never receives your private key. Even if its database is stolen, the attacker gets public keys, which are useless for signing in. This removes the whole class of leaked-password attacks for accounts that use it.

Relation to passkeys

Passkeys are the user-friendly form of WebAuthn credentials, often synced between your devices. The mechanism underneath is the one WebAuthn defines. Both are about authenticating to accounts. Using one to sign in to a service is separate from controlling a crypto wallet's private key, which still needs its own backup and care.

Example

You register a security key with a website. The site stores a public key. At login it sends a random challenge, your key signs it after you touch it, and the site verifies it. On a lookalike phishing site, the key refuses because the origin differs.

Put it into practice

Use passkeys where they are offered

Scrypt Wallet supports passkeys for protecting your account. Add one so a leaked password or a fake site cannot take your wallet.

Create a free wallet Get Scrypt for Android

Sources and verification

Last reviewed 2026-10-02 by the Scrypt Wallet team. The factual claims on this page, and where each comes from:

  1. WebAuthn lets web applications create and use scoped public-key credentials. [1]
  2. Credentials are scoped to a relying party, which supports resistance to phishing. [1]
  3. NIST says manually entered one-time codes are not verifier-impersonation resistant. [2]

Sources

  1. Web Authentication: An API for accessing public key credentials (Level 3) · W3C · primary source
  2. NIST SP 800-63B: Digital identity guidelines, authentication · NIST · primary source

Primary sources are protocol papers, specifications, source code or a project's own documentation; secondary sources are wikis and explainers. We checked each claim against the source text on the review date. Found an error? Tell us and we will correct it.

Frequently asked questions

Is WebAuthn the same as a passkey?

A passkey is a WebAuthn credential, often synced across your devices. WebAuthn is the standard that defines how it works.

Does the website see my fingerprint?

No. The biometric check happens on your device. The site only receives a cryptographic signature.

Can it protect my wallet's private key?

It protects logins and access, but a wallet's private key still needs its own secure storage and backup.

Related terms

Go deeper

Written by the Scrypt Wallet team · Updated 2026-10-02. General education, not financial, tax or legal advice.