Companies Using Cisco Duo

Cisco Duo is easier to count than most identity products, and the reason says something useful about how it is bought. TechnologyChecker.io verifies 21,045 organizations publishing a Duo Single Sign-On domain record as of August 24, 2026, and we matched 20,032 of them to a company profile. That 90.8% match rate is the highest of any technology we have profiled. Nothing about Duo makes its customers more findable. The detection surface does.

Why this count behaves differently from Okta's

Duo Single Sign-On requires an organization to prove it controls the email domains its people log in with. Cisco's documentation is explicit about the method: you add a DNS TXT record to that domain's public DNS, then Duo queries for it before it will accept logins from that domain. The record sits on the customer's own domain, in public DNS, and it carries a token unique to that organization. We checked 40 of the largest accounts on this page by hand and found the record still resolving on 39, each with its own token.

Compare that with how Okta becomes visible. Okta's workforce product runs on tenants Okta hosts, so an employee signing into Salesforce through Okta never touches their employer's public web presence. We see Okta only when a company puts a branded sign-in page on its own domain, which is why our Okta count is 1,529 against a customer base the company reports near 20,000. Duo's 21,045 and Okta's 1,529 are not a market share statement. They are two different questions answered by two different mechanisms.

The 13x gap between our Duo and Okta counts reflects where each product leaves a public trace, not how many customers each one has. Anyone quoting it as a competitive fact is reading the wrong thing off the page.

Duo's number carries its own limits, and they run in one direction. The DNS record is required for Duo Single Sign-On, not for Duo's multi-factor authentication on its own, so any organization using Duo Push without the SSO product is invisible here. Cisco's documentation also states that the record may be deleted once verification succeeds, so accounts that tidied up their DNS drop out of view. Both effects push the same way. Treat 21,045 as a floor on Duo Single Sign-On deployments, and Duo Single Sign-On as a subset of Duo overall.

The base is smaller than the logo wall suggests

The companies listed on this page skew enormous: HCLTech, Reliance Industries, Shell, Tech Mahindra, Orange, Uber, Honeywell. Sorting by headcount always produces that list. The distribution tells a different story. Organizations with 51 to 200 staff are 27.12% of the base and those with 11 to 50 are 26.10%, so 53% of Duo customers sit under 200 people. Companies above 1,000 staff are 9.73%, and above 10,000 just 1.39%.

Reading that as evidence that Duo is weaker in the enterprise than its rivals would be a mistake, because the comparison has to hold the detection method still. 1Password is the right control: same category, same domain verification record, 20,876 domains against Duo's 21,045. On that peer, organizations above 1,000 staff are 5.17% and above 10,000 are 0.71%. Duo carries close to twice the enterprise weight of a peer measured identically. The mid-market skew is real, and Duo is still the more enterprise product of the two.

Compliance is doing the selling

The industry mix is where Duo separates from everything around it. Law practices are 3.73% of Duo's base. On 1Password, detected the same way, they are 0.77%. Government administration runs 4.06% against 0.64%. Accounting is 2.10% against 0.88%. Hospitals and health care reach 4.96% against 2.07%. These are not small differences and they survive the control, so they describe Duo's buyers rather than an artifact of how we find them.

Those four verticals have something in common that has little to do with technology. They are the organizations most likely to be told to deploy multi-factor authentication by someone outside the building: a cyber insurance underwriter at renewal, a corporate client sending a security questionnaire, a state or federal records rule, a health privacy audit. They are also small, sitting in exactly the 11 to 200 staff bands where nobody has an identity team. Duo suits that buyer because it goes in front of the logins already in place instead of replacing the directory beneath them.

Duo's strongest verticals are the ones where somebody else decides that multi-factor authentication is mandatory. That is a different sales motion from platform identity, and it explains the age profile: 26.51% of these organizations were founded before 1960.

What the surrounding stack tells a seller

Duo accounts are Microsoft accounts. Microsoft 365 appears on 41.36% of Duo domains against 6.88% running Google Workspace. A six to one split is far outside the market norm and it makes sense given where Duo is usually installed, in front of Active Directory and Microsoft-centred application estates. Dedicated email security is common on top: Mimecast 9.83%, Barracuda 8.65%, Microsoft Defender 7.19%, Proofpoint 5.72%, Sophos 4.15%. These are organizations already paying for layered security.

One overlap deserves attention from anyone selling the Cisco portfolio. Webex appears on 8.47% of Duo domains and Zoom on 5.94%, yet across our full corpus Zoom is much the larger product, 44,288 domains against Webex's 26,661. Correcting for that, a Duo account is about twice as likely to be a Webex account as the market would predict. Both products are detected through the same kind of domain record, so the comparison is clean. Cisco cross-sell is visible in the data.

Churn, and what we can honestly say about it

TechnologyChecker.io began tracking Duo in March 2026, so our churn history is five months deep and the counts are correspondingly small. In that window 194 domains stopped publishing a Duo record. Twelve domains running Duo dropped a competing identity product while we watched, three each from Microsoft Entra ID and Okta, two from Microsoft's authentication library, and one each from 1Password, NordPass, SimpleSAMLphp and Auth0. One went the other way, to 1Password. The direction favours Duo. The sample does not yet support calling it a trend, and we would rather say that than dress up twelve domains as a migration wave.

How to use this list

If you sell security to the mid-market, this is a qualified list in a way most technology footprints are not. Every domain here belongs to an organization that completed a DNS change to finish an identity rollout, which means budget was approved and somebody owns it. Filter to law, accounting, health care and local government under 200 staff and you have the compliance-driven buyer. Filter to Microsoft 365 without a dedicated email gateway and you have an obvious gap. If you sell against Duo, the 1Password overlap and the Entra ID movement are the two places where accounts are actually changing hands.