Skip to content

Security Not yet confirmed elsewhere1 publisher 2 min read Published

Dashlane data puts passkeys at 28% of Google logins and 17% of Amazon's

Dashlane's annual report counts 2.5 million passkey authentications a month, nearly double last year. Most logins at the biggest sites still use another method, so passwords and one-time codes stay in play.

The Watch · Security desk

How we use AI Send a correction

Passkeys: majority of users, minority of logins Share of Dashlane users storing at least one passkey, now and last year, and share of Google and eBay logins made with a passkey.

Key figures from Dashlane's report: 57% of Dashlane users now store at least one passkey, compared with 40% last year. Passkeys account for 28% of Google logins and 8% of eBay logins, a minority on both sites.

Passkeys: majority of users, minority of logins
FigureValueNoteClaim
Dashlane users storing at least one passkey, now57%3
Dashlane users, last year40%3
Google logins by passkey28%4
eBay logins by passkey8%4

What happened

  • The same report puts passkeys at 18% of PayPal logins and 8% of eBay's.
  • AWS, Dropbox, isolved HCM and BambooHR are new entrants to the report's top 20 applications by passkey use.
  • LY Corporation has announced a spring 2027 deadline for Yahoo Japan users, and the report says forced adoption of this kind is rare.

Why it matters

  • exposure An account that keeps a password or one-time code fallback keeps the phishing target a passkey removes, so enrolment alone does not close the route.
  • constraint Security teams keep running password policy, reset flows and MFA beside passkeys, because most logins at the sites listed still use another method.
  • decision Site owners now choose when to disable passwords and one-time codes. Dashlane lists removal and a mandatory deadline as the steps still to take.
  • cost The help-desk saving from fewer password resets reaches only users who enrol, and 43% of Dashlane users hold no passkey.

Passkeys protect the logins that use them. At Google, Dashlane's data puts that share at 28% [4], which leaves 72% of those logins on something else [14]. The report lists one-time passcodes and passwords as the alternatives to start removing [10].

A passkey has no password to guess or steal [5]. It is cryptographically tied to the legitimate website, and the private key stays on the user's device, so a breach of the site does not hand an attacker a usable key [6]. An attacker facing a passkey-only account has nothing to phish, while one facing an account that still accepts a password has the old target. In our view, the exposure shrinks only where the fallback is switched off.

Users storing at least one passkey rose from 40% to 57% [3], a gain of 17 points [15]. The other 43% hold none [16]. Monthly authentications nearly doubled to 2.5 million [2], measured over July 2025 to June 2026 [1].

Those figures describe Dashlane users. People who run a password manager are likely to be early adopters, and we'd expect the rate across all users of those sites to be lower. Infosecurity Magazine's account does not say how the per-site shares were calculated.

The business case in the report is administrative. Dashlane says passkeys can reduce the password-reset workload for IT support [7]. HubSpot and Cisco Duo led by authentication volume [8]. AWS, Dropbox, isolved HCM and BambooHR are new to the top 20 [9].

Dashlane's fourth recommendation is a deadline for mandatory passkey use [10]. The report noted that developers forcing users onto passkeys are few, and named one: LY Corporation has announced a spring 2027 deadline for Yahoo Japan users [11]. Until more deadlines like that appear, password resets, one-time codes and MFA stay in the stack.

Dashlane's chief product officer, Christophe Frenet, said "Despite sustained growth, we're not on the other side yet" [12]. He added that "more companies need to go from soft adoption to enforcing the change" [13].

What to watch

  • Whether Yahoo Japan's spring 2027 deadline holds and other operators announce dates of their own.
  • Whether Dashlane's next annual report shows passkey share at Google above 28% and holders above 57%.
  • Whether any top-20 service begins removing password or one-time-passcode login for accounts with a passkey.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence55
Adoption45
Hype gap−5
Incentives60
Confidence60
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Dashlane analyzed millions of aggregated, anonymized passkey authentications that it managed between July 2025 and June 2026 to compile its third annual Passkey Power 20 report.

    Reported Supported Source: Infosecurity Magazine reporting on Dashlane's Passkey Power 20 reportView cited source
  2. [2]

    Passkey authentications by Dashlane users nearly doubled year on year, reaching 2.5 million per month in 2026.

    Reported Supported Source: Dashlane Passkey Power 20 report, via Infosecurity MagazineView cited source
  3. [3]

    Over half (57%) of Dashlane users now store at least one passkey, compared with 40% last year.

    Reported Supported Source: Dashlane Passkey Power 20 report, via Infosecurity MagazineView cited source

Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.

Add to ChatGPTAdd to Claude

Sources

1 independent publisher whose own reporting we read for this story.

  1. infosecurity-magazine.com

    1 article · October 14, 2026

    Passkey Authentications Double but Adoption Remains Slow

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Entities

Loading related stories