| Google Authenticator | |||||
|---|---|---|---|---|---|
| Developer | |||||
| Release | September 20, 2010 | ||||
| Stable release(s) [±] | |||||
| |||||
| Written in |
| ||||
| Operating system | Android 9+, iOS 17+ Discontinued
| ||||
| License | Proprietary freeware (some versions were under Apache License 2.0) | ||||
| Repository | github | ||||
Google Authenticator is a software-based authenticator by Google. It implements multi-factor authentication services using the time-based one-time password (TOTP; specified in RFC 6238) and HMAC-based one-time password (HOTP; specified in RFC 4226), for authenticating users of software applications.
When logging into a site supporting Authenticator (including Google services) or using Authenticator-supporting third-party applications such as password managers or file hosting services,[citation needed] Authenticator generates a six-digit one-time password which users must enter in addition to their usual login details.
Google provides Android, BlackBerry, and iOS versions of Authenticator. Authenticator started backing-up to the cloud in 2023 for logged-in users making it easier to switch devices. It does not make it easy to switch between competitor products and collects more data than some of its competitors like Aegis or Stratum. The app is relatively easy-to-use and was the most prominent app for multi-factor authentication as of 2023.
An official open source fork of the Android app is available on GitHub. However, this fork was archived in April 6, 2021 and is now read only. Current software releases are proprietary software. Google does not end-to-end encrypt backups.


The app is first installed on a smartphone to use Authenticator. It must be set up for each site with which it is to be used: the site provides a shared secret key to the user over a secure channel, to be stored in the Authenticator app. This secret key will be used for all future logins to the site.[citation needed]
To log into a site or service that uses two-factor authentication and supports Authenticator, the user provides a username and password to the site. The site then computes (but does not display) the required six-digit one-time password and asks the user to enter it. The user runs the Authenticator app, which independently computes and displays the same password, which the user types in, authenticating their identity.[citation needed]
With this kind of two-factor authentication, knowledge of username and password is insufficient to get into a user's account - the attacker would need knowledge of the shared secret key or physical access to the device running the Authenticator app. A man-in-the-middle attack is another risk for users if their device used for the login process is compromised by malware, the credentials and one-time password can be intercepted by the malware, which then can initiate its login session to the site, or monitor and modify the communication between the user and the site.
During setup, the service provider generates an 80-bit secret key for each user (whereas RFC 4226 §4 requires 128 bits and recommends 160 bits). This is transferred to the Authenticator app as a 16, 24, or 32-character base32 string, or as a QR code.
Subsequently, when the user opens the Authenticator app, it calculates an HMAC-SHA1 hash value using this secret key. The message can be:
A portion of the HMAC is extracted and displayed to the user as a six- to eight-digit code; The last nibble (4 bits) of the result is used as a pointer, to a 32-bit integer, in the result byte array, and masks out the 31st bit.[citation needed]
The Google Authenticator app for Android was open source upon launch in 2010 before becoming proprietary in 2013. Google made earlier source code for their Authenticator app available on its GitHub repository where the latest open-source release was in 2020.