With 2-Step Verification, or two-factor authentication, you can add an extra layer of security to your account in case your password is stolen.
After you set up 2-Step Verification, you can sign in to your account with:
When you sign in, you may encounter different authentication challenges. The challenge you'll get is what Google thinks is best to help you sign in easily and keep out hijackers.
Tips:
Tip: If you use an account through your work, school, or other group, these steps might not work. If you can’t set up 2-Step Verification, contact your administrator for help.
Verify it’s you with a second stepImportant:
After you turn on 2-Step Verification, you need to complete a second step to verify it’s you if you choose to sign in with a password. To help protect your account, Google will ask you to complete a specific second step.
Use Google promptsIf you choose not to sign in with a passkey, we recommend you use Google prompts as your second step. It's easier to tap a prompt than enter a verification code. Prompts can also help protect against SIM swap and other phone number-based hacks.
You’ll receive Google prompts as push notifications on:
Based on the device and location info in the notification, you can:
For added security, Google may ask you for your PIN or other confirmation.
Use other verification methodsYou can set up other verification methods in case you:
Passkeys are a simple and secure alternative to passwords. With a passkey, you can sign in to your Google Account with your fingerprint, face scan, or device screen lock, like a PIN. You can create a passkey on a phone, computer, or hardware security key. Learn how to create a passkey.
A hardware security key is a small device that you can buy to help verify it’s you when you sign in. When we need to make sure it’s you, you can simply connect the key to your phone, tablet, or computer. Learn how to order your hardware security keys.
Tip: When a hacker tries to get your password or other personal information, passkeys and hardware security keys protect your Google Account from phishing attacks. Learn more about phishing attacks.
Use Google Authenticator or other verification code appsImportant: Never share your verification codes with anyone, as scammers may try to take over your account. You won't receive a call from Google to verify a code.
When you don't have an internet connection or mobile service, you can set up Google Authenticator or another app that creates one-time verification codes.
To help verify it's you, enter the verification code on the sign-in screen.
Use a verification code from a text message or callImportant: Never share your verification codes with anyone, as scammers may try to take over your account. You won't receive a call from Google to verify a code.
A 6-digit code is sent to a number you’ve previously provided. Codes can be sent in a text message or a voice call, which depends on the setting you chose. To verify it’s you, enter the code on the sign-in screen.
Tip: Although any form of 2-Step Verification adds account security, verification codes sent by texts or calls can be vulnerable to phone number-based hacks.
Use a QR codeIn certain cases, Google will require that you scan a QR code with your mobile device to verify. This method is less vulnerable to phone number-based attacks and abuse.
To verify your phone number:
Important: Do not give out your backup codes to anyone.
If you lose your phone, you can use a backup code for the second step. You can print or download a set of 8-digit backup codes to keep in a safe place.
Learn more about backup codes.
Skip a second step on trusted devicesIf you don't want to provide a second verification step each time you sign in on your computer or phone, check the box next to "Don't ask again on this computer" or "Don't ask again on this device."
Important: Only check this box on devices you regularly use and don't share with anyone else.
Related resourcesRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3