Download websites that use LoginRadius

About LoginRadius

Replacing a login screen is one of the least casual decisions a web team makes. Passwords, sessions, account recovery, consent records and the audit trail behind all of them move together, and once an outside identity provider is wired into the signup flow it tends to stay wired in for years. LoginRadius occupies exactly that position in the Authentication layer of the sites that run it, which makes its presence a durable fact about a business rather than a passing choice of library.

As of September 2026 we detect LoginRadius on 193 sites. Counts in this category are always smaller than counts for analytics tags or edge networks, because managed identity is only worth buying when there are real accounts behind the front page. Retailers with saved carts, publishers with registered readers, subscription products, member portals and support communities are the shapes that keep appearing. A brochure site has no user directory to delegate, so the population visible here is already filtered down to properties that maintain a logged-in surface, and that filtering is most of what the list is worth.

LoginRadius Inc. has offered the product under a Proprietary license since 2012, which is long enough for a customer base to settle into place. Identity vendors that last that long accumulate integrations, and integrations accumulate switching costs. For anyone selling into the same buyers, an existing deployment is therefore a strong qualifier. The organisation has already accepted the idea of outsourcing authentication, has already put a third party through a security review, and has a renewal date somewhere in its calendar.

Detection here is inferential and we would rather say so plainly. Hosted authentication is frequently served from a subdomain or a vendor-branded page that a crawl of the main hostname never reaches, and some integrations run entirely server to server, leaving nothing in the delivered markup to match against. Our figure should be read as sites where a public fingerprint was visible, not as a vendor customer count, and the real installed base is larger than what we can see.

The question the downloadable list answers is the one a per-domain lookup cannot. Checking a single company tells you what that company uses. A file of every domain where the fingerprint appears tells you how large the footprint is, which industries and country code suffixes it clusters in, and which of your own prospects or competitors have already made this decision and locked themselves into it. Analysts sizing the identity market, partner teams hunting for integration targets and security researchers mapping shared authentication dependencies all start from the same file.