What Is g.co/sc? How to Get a Google Security Code & Fix g.co/sc Login Problems

If Google is telling you to “visit g.co/sc in a new browser window” to obtain a security code, you are seeing part of a Google identity-verification and 2-Step Verification process.

The message can be extremely confusing—especially when you are already locked out of Gmail or your Google Account.

The most important thing to understand is:

g.co/sc is not a website that simply gives anyone a recovery code. In Google's documented security-key procedure, you visit g.co/sc from a device that is already signed into the Google Account you are trying to access.

If you are completely signed out everywhere, g.co/sc may therefore not solve the problem by itself. You may need another verification method or Google's official account-recovery process.

This guide explains exactly what to do.

Quick Answer: What Should I Do When Google Says “Visit g.co/sc”?

If another device is still signed into your Google Account

For example, Gmail or another Google service still works on your old phone, tablet, laptop, desktop, Chromebook, or another browser profile:

1. Do not sign out of that device.
2. Open a browser on that signed-in device.
3. Make sure the correct Google Account is active.
4. Go to g.co/sc.
5. Follow Google's on-screen instructions.
6. If Google provides the requested security-code process, complete it.
7. Return to the device where you were trying to sign in.
8. Enter the requested code and continue.

If you are signed out everywhere

Look for:

Try another way
or
More ways to verify

Google may offer another verification method.

If you cannot complete any method Google offers, use Google's official Google Account Recovery process.

What Is g.co/sc?

g.co is Google's short domain.

Google officially documents g.co/sc as part of a security-code procedure for 2-Step Verification when a user cannot use their security key.

Google's documented instructions are essentially:

1. Use a device signed into your account.
2. Go to g.co/sc.
3. Follow the on-screen instructions.

This explains something that confuses many users:

g.co/sc is not a general-purpose Gmail password reset or account-recovery-code generator.

It is part of a specific Google verification process.

Is g.co/sc Really Google?

Yes. g.co is a Google-controlled short domain.

The address discussed in this guide is:

g.co/sc

However, always inspect URLs carefully.

A malicious website can use an address that visually resembles a legitimate Google address.

For example, do not assume a site is Google merely because:

• “Google” appears somewhere in the URL;
• it uses Google's logo;
• the page looks like Google;
• the browser displays HTTPS or a padlock.

Always check the actual domain.

What Does “Visit g.co/sc in a New Browser Window” Mean?

This is one of the most confusing parts of Google's instruction.

Think of the process as involving two environments.

Device A — The Device Where You Are Trying to Sign In

For example:

• your new iPhone;
• a new Android phone;
• a new computer;
• a browser where you are currently signed out;
• a phone after a factory reset.

Google is asking Device A for additional verification.

Device B — A Device Where Your Account Is Already Signed In

For example:

• your old phone;
• a tablet;
• laptop;
• desktop;
• Chromebook;
• another authenticated browser profile.

On Device B:

1. Confirm that the correct Google Account is signed in.
2. Open a browser.
3. Go to g.co/sc.
4. Follow Google's instructions.

Then return to Device A and continue the verification process.

New Browser Window vs New Tab — Does It Matter?

If your browser does not provide an obvious “New Window” option, don't focus too heavily on the words window versus tab.

The critical issue is not simply creating another blank browser window.

The important requirement in Google's documented g.co/sc security-key procedure is that you use a device signed into the affected Google Account.

Opening ten new tabs on a completely signed-out device does not create an authenticated Google session.

So first ask:

Do I have another device or browser session where this Google Account is already signed in?

That is the more important question.

Important: Do Not Sign Out of a Working Google Device

Before troubleshooting further, check every device you use.

Look at:

• Android phones;
• iPhones;
• iPads;
• Windows computers;
• Macs;
• Chromebooks;
• tablets;
• Chrome browser profiles.

Check whether Gmail, YouTube, Google Drive, Google Photos, or another Google service still works with the affected account.

If it does:

Do not unnecessarily sign out.

That existing authenticated session may be valuable for verification or account recovery.

How to Use g.co/sc Step by Step

Step 1: Find a Signed-In Device

Find a phone, tablet, computer, Chromebook, or browser profile where the affected Google Account is still signed in.

Step 2: Confirm the Correct Google Account

This is particularly important if you use several Gmail/Google accounts.

The account already authenticated on the working device must be the same account you are trying to access.

Step 3: Open g.co/sc

On the signed-in device, open your browser and go to:

g.co/sc

Step 4: Follow Google's Instructions

Follow the instructions Google displays for your account.

Do not use third-party websites claiming they can generate Google verification codes.

Step 5: Return to the Original Login

Return to the new phone, computer, or browser where Google originally requested verification.

Complete the verification using the method Google requested.

Example: Signing Into Google on a New Phone

Suppose you purchased a new phone.

You enter:

Google email → Password

Google then asks for additional verification and tells you to visit g.co/sc.

Meanwhile, your laptop is still signed into the same Google Account.

On the old laptop

Confirm correct Google Account → Open browser → Visit g.co/sc → Follow Google's instructions

On the new phone

Return to Google verification → Enter/complete the requested verification → Continue sign-in

The important advantage in this example is that another authenticated Google session still exists.

What If I Have an iPhone Instead of Android?

This question deserves special attention because many users assume g.co/sc requires them to own an Android phone.

Google's documented g.co/sc security-key instructions say to use a device signed into your account.

Therefore, if you have an iPhone, iPad, Mac, Windows computer, Chromebook, or another device where the affected Google Account is already authenticated, follow the specific instructions Google presents there.

However, Google's separate 10-digit Android Security Code feature is Android-specific.

These are related Google verification concepts, but they should not be confused.

If Google specifically asks you to:

“Get a security code on your Android phone”

then that particular method requires an appropriate Android device.

If you do not have Android, select Try another way or another verification option Google makes available.

How to Get the 10-Digit Google Security Code on Android

If Google's verification screen specifically offers:

Get a security code on your Android phone

you can use Google's Android security-code feature.

On a supported Android phone or tablet:

1. Open Settings.
2. Tap Google.
3. Tap Manage your Google Account.
4. Open Security or Security & sign-in.
5. Look for Security code.
6. Authenticate using your device PIN, pattern, password, fingerprint, or screen lock if requested.
7. Select the correct Google Account.
8. Use the security code Google displays.

Google documents that this Android security-code process can work without internet access or mobile service.

Important

The Android security code is different from:

• SMS OTP;
• Google Authenticator code;
• Google Prompt;
• backup code;
• passkey;
• hardware security key.

Use the exact verification method Google is requesting.

g.co/sc After a Factory Reset

Factory-reset scenarios are a common source of g.co/sc confusion.

Suppose your phone previously contained your Google Account.

You factory-reset the phone.

After the reset, you attempt to sign into the same account again.

The previous authenticated Google session on that phone may no longer exist.

Google may now see a new or reinitialized device and require additional verification.

What should you do?

Check whether the same Google Account remains signed in on another:

• phone;
• tablet;
• laptop;
• desktop;
• Chromebook;
• browser profile.

If another authenticated device exists, preserve that session and follow Google's verification instructions.

If no signed-in device remains, select Try another way and review the alternatives Google offers.

g.co/sc Keeps Asking Me to Sign In — Verification Loop

Some users experience this:

1. Google asks for a security code.
2. Google tells them to visit g.co/sc.
3. They visit g.co/sc.
4. Google asks them to sign in.
5. Signing in requires the same verification.
6. They appear to return to the original problem.

This feels like an endless loop.

Why does this happen?

You may be attempting to use g.co/sc from a device that is not already authenticated with the affected Google Account.

Remember:

g.co/sc is not a universal account-recovery-code generator.

What should you do?

First, search for another device where the Google Account is still signed in.

If none exists:

1. Return to the Google sign-in screen.
2. Select Try another way or More ways to verify, if available.
3. Review the alternative verification methods Google offers.
4. If you cannot use any offered method, use Google's official account-recovery process.

My Phone Number Is Linked, but Google Does Not Show SMS

Another common situation is:

“My phone number is registered with Google, but Google isn't giving me the option to receive an OTP by SMS.”

A telephone number being associated with your Google Account does not guarantee that SMS will be offered for every security challenge.

Google determines which verification options are available for a particular sign-in.

Depending on the circumstances, you may instead see:

• Google Prompt;
• passkey;
• security key;
• backup code;
• another signed-in device;
• Android security code;
• another verification method;
• account recovery.

Select:

Try another way

or:

More ways to verify

when Google provides the option.

Important

BISON cannot send Google's OTP or verification code to your telephone number.

Google controls its authentication systems.

Never post your telephone number, password, OTP, security code, Authenticator code, backup code, or recovery information in public comments.

What If I Lost My Phone?

Losing your primary phone does not automatically mean losing your Google Account.

Depending on what you configured previously, you may still have:

• another signed-in device;
• backup phone;
• Google Prompt;
• backup codes;
• hardware security key;
• another registered security key;
• passkey;
• trusted computer;
• another verification option.

At the Google sign-in screen, select:

Try another way

and review the options available to your account.

Once you regain access, review and remove authentication credentials associated with a lost or stolen device where appropriate.

What If My Old Phone Number Is No Longer Active?

If the registered number has been disconnected, changed, or lost, do not assume SMS is your only recovery method.

Select:

Try another way

Google may provide another configured authentication method.

After recovering the account:

1. Update your recovery phone.
2. Confirm your recovery email.
3. Review 2-Step Verification.
4. Remove obsolete numbers where appropriate.
5. Review passkeys and security keys.
6. Generate appropriate backup methods.

g.co/sc Security Code vs SMS OTP

These are different.

SMS OTP

Google sends a code through the mobile telephone network.

This depends on the telephone number and SMS availability.

g.co/sc / Google Security Verification

This uses a Google verification process associated with your authenticated account/device.

Do not assume a g.co/sc code and an SMS OTP are interchangeable.

g.co/sc vs Google Authenticator

Google Authenticator generates time-based one-time codes for accounts configured with it.

A g.co/sc security-code process is different.

If Google requests a specific type of code, provide that type rather than substituting an Authenticator code.

g.co/sc Security Code vs Google Backup Code

These are also different.

Google backup codes are emergency codes generated in advance for 2-Step Verification.

Google currently allows users to generate a set of 10 backup codes, and each backup code can be used once.

Generating a new set makes the previous set inactive.

If you previously downloaded your Google backup codes, the file may have a name similar to:

Backup-codes-username.txt

Store backup codes securely.

Never send them to another person.

g.co/sc vs Google Prompt

Google Prompt may display a notification on another signed-in device asking whether you are trying to sign in.

You approve or reject the login from that device.

A g.co/sc verification flow is different because Google may ask you to obtain a security code through a separate verification procedure.

g.co/sc vs Passkey

Passkeys provide cryptographic authentication and may use:

• fingerprint;
• face recognition;
• device PIN;
• screen lock;
• supported security hardware.

If a usable passkey is available, Google may offer it as another sign-in method.

g.co/sc vs Hardware Security Key

A hardware security key is a physical authentication device.

It may use technologies such as:

• USB;
• NFC;
• other supported authentication methods.

Google specifically documents g.co/sc as a way to generate a security code for 2-Step Verification when a user cannot use their security key.

Why Is My g.co/sc Security Code Invalid?

If Google rejects the code:

1. Check the Google Account

Make sure the code belongs to the exact account you are attempting to access.

This is especially important if several Google Accounts are configured on your device.

2. Check Every Digit

Carefully enter the code exactly as displayed.

3. Use the Correct Type of Code

Do not confuse:

• Google security code;
• SMS OTP;
• Authenticator code;
• backup code.

4. Follow the Current Verification Screen

If you have started multiple verification attempts, follow the newest active Google verification screen rather than an old tab or previous request.

5. Try Another Verification Method

Select Try another way if Google offers it.

What If “Try Another Way” Does Not Work?

The options Google provides vary according to your account and the circumstances of the sign-in.

You cannot force Google to display a specific verification method.

If none of the available options works, proceed to Google's official Google Account Recovery process.

Completely Locked Out of Google — What Should I Do?

If:

• you are signed out everywhere;
• the old phone is gone or reset;
• the old number is unavailable;
• you have no usable backup code;
• you cannot use your security key;
• you cannot use your passkey;
• Google Prompt is unavailable;
• g.co/sc sends you back to sign-in;

then you are dealing with account recovery, not simply g.co/sc troubleshooting.

Use Google's official account-recovery process.

Improve Your Chances During Account Recovery

Where practical:

• use a device you previously used with the account;
• use the browser you normally used;
• attempt recovery from a familiar location;
• answer Google's questions as accurately as possible;
• provide the most recent password you remember if asked;
• avoid unnecessary guessing;
• follow Google's instructions exactly.

Do not pay anyone who claims they can bypass Google's account-ownership verification.

Google Account Recovery Scams — Important Warning

People locked out of Gmail are attractive targets for scammers.

Be suspicious of anyone saying:

“Pay me and I will recover your Gmail.”

“Send me the security code.”

“Give me your backup codes.”

“I work with Google and can unlock your account.”

“Install this remote-access program so I can recover Gmail.”

Do not comply.

Never provide another person with:

• Google password;
• OTP;
• security code;
• Authenticator code;
• backup code;
• recovery information.

Google Workspace and Business Accounts

If your account looks like:

yourname@yourcompany.com

rather than a consumer @gmail.com account, it may be managed through Google Workspace.

Contact your organization's:

• Google Workspace administrator;
• IT department;
• authorized IT support provider.

Administrators may have organizational account-management and recovery capabilities that do not exist for ordinary consumer Gmail accounts.

However, an administrator cannot simply bypass every Google security mechanism in every situation.

Before Replacing or Factory-Resetting Your Phone

Preventing a lockout is much easier than recovering from one.

Before resetting, selling, or replacing your phone:

1. Confirm that you know your Google Account password.
2. Verify your recovery phone number.
3. Verify your recovery email.
4. Review 2-Step Verification methods.
5. Check Google Authenticator access/migration where applicable.
6. Review your passkeys.
7. Review your security keys.
8. Generate and securely store backup codes where appropriate.
9. Confirm that another device can access the account.
10. Sign into the replacement device successfully.
11. Only then erase the old device.

This is particularly important for business owners and Google Workspace administrators.

Quick g.co/sc Troubleshooting Checklist

Problem	What to Check
Google says visit g.co/sc	Use a device already signed into the affected account when Google's procedure calls for it
Only “New Tab” is available	Focus on having an authenticated account session rather than the wording “window”
g.co/sc asks you to sign in	Look for another device where the account is already signed in
New phone	Preserve access on the old device until the new phone works
Factory-reset phone	Check another signed-in device
iPhone user	Use the verification options Google offers; the separate 10-digit Android Security Code requires Android
Phone number linked but no SMS	Select Try another way/More ways to verify
Code rejected	Check account, digits, code type, and current verification attempt
Lost phone	Check backup methods and other authenticated devices
Signed out everywhere	Use Google Account Recovery
Someone asks for your code	Do not provide it

Frequently Asked Questions (FAQ)

1. What is g.co/sc?

g.co/sc is a Google-controlled shortcut documented as part of a security-code procedure for 2-Step Verification when a security key cannot be used.

2. Is g.co/sc safe?

The correctly spelled g.co domain is controlled by Google. Always check the actual address because phishing sites may imitate Google.

3. Why is Google telling me to visit g.co/sc?

Google is requesting additional identity verification. In its documented security-key procedure, g.co/sc can be used from a device already signed into your account.

4. Do I need another device for g.co/sc?

The key requirement in Google's documented procedure is access to a device signed into the affected Google Account. This may be another physical device or an appropriate authenticated environment.

5. Can I use an Android phone?

Yes, if the relevant Google Account is appropriately signed in and Google's verification flow supports it. Android also has a separate 10-digit Security Code feature.

6. Can I use an iPhone or iPad?

Follow the verification methods Google offers on your signed-in devices. However, Google's separate “Get a security code on your Android phone” method specifically requires Android.

7. Can I use a Windows PC or Mac?

If the affected Google Account is already authenticated there and Google's g.co/sc procedure is available, follow Google's instructions.

8. Do I really need a new browser window instead of a new tab?

The more important issue is whether the account is already authenticated in the environment you are using. Merely opening a new tab on a completely signed-out device does not create an authenticated session.

9. Why does g.co/sc keep asking me to sign in?

The device/browser may not already be authenticated with the affected account. Look for another signed-in device or use another verification/recovery option.

10. Why is my g.co/sc security code invalid?

Check that the code belongs to the correct account, was entered accurately, and is the type of code Google is requesting.

11. Is a g.co/sc code the same as an SMS OTP?

No. They are different verification mechanisms.

12. Is a g.co/sc code the same as Google Authenticator?

No. Google Authenticator generates time-based authentication codes and is a separate verification method.

13. Is a backup code the same as a g.co/sc security code?

No. Backup codes are generated in advance as emergency 2-Step Verification codes.

14. How many Google backup codes can I generate?

Google currently provides a set of 10 backup codes. Each can be used once. Generating a new set makes the previous set inactive.

15. Why is my phone number registered but SMS is not offered?

Google does not necessarily offer every verification method during every sign-in. Select Try another way or More ways to verify when available.

16. What should I do if I lost my phone?

Try another signed-in device, backup method, passkey, security key, backup code, or another verification option Google provides.

17. What if my old phone number is no longer active?

Use another verification method. After regaining access, update your recovery phone and security configuration.

18. What if my phone was factory reset?

The previous authenticated session may have been removed. Check whether another device remains signed into the account.

19. Can Google Support give me my security code?

Do not rely on anyone claiming they can manually bypass Google's authentication process or generate a secret code for your account.

20. Can BISON send the Google OTP to my phone?

No. BISON and other third-party support providers do not control Google's OTP and authentication systems.

21. Should I give a security code to an IT technician?

No technician needs your Google security code merely to “prove” your identity to Google. Authentication secrets should remain private.

22. Can I recover my account if I am signed out everywhere?

Potentially, but g.co/sc may not solve the problem by itself. Use the verification methods Google offers and, when necessary, Google's official account-recovery process.

23. What should I do if Google says “Try another way”?

Review each method Google offers and use one that you still control. Available methods vary by account.

24. Can I force Google to send an SMS?

No. The verification methods available for a particular sign-in are determined by Google.

25. What is the most important thing to remember about g.co/sc?

Use g.co/sc only when Google instructs you to, preserve any device where your account is still signed in, and never share Google authentication codes with another person.

Final Advice

If Google sends you to g.co/sc, first determine whether another device or authenticated browser session still has access to the affected Google Account.

If one does: preserve that session and follow Google's instructions.

If none does: select Try another way or More ways to verify and check the alternatives Google provides.

If no verification method is usable: proceed through Google's official account-recovery process.

Most importantly:

Never give your Google password, security code, Authenticator code, backup code, or OTP to anyone offering to recover your account.

 

What Is g.co/sc? Fix Google Security Code & Login Problems

Google says visit g.co/sc in a new browser window? Learn exactly what g.co/sc means, how to get the security code, fix login loops, missing SMS, factory-reset and lost-phone problems.

#gcosc #GoogleSecurityCode #GoogleVerification #GoogleLogin #GoogleAccountRecovery #GmailRecovery #GoogleLoginProblem #GmailLoginProblem #Google2StepVerification #Google2FA #GoogleSecurity #GoogleAccountSecurity #GmailSecurity #GoogleVerificationCode #Google10DigitCode #GoogleAccount #Gmail #GooglePrompt #GoogleAuthenticator #GoogleBackupCodes #GooglePasskey #GoogleSecurityKey #GoogleOTP #GoogleAccountLocked #RecoverGoogleAccount #RecoverGmail #GoogleAccountHelp #GoogleTroubleshooting #GmailTroubleshooting #GoogleWorkspace #GoogleWorkspaceSecurity #GoogleWorkspaceRecovery #AccountRecovery #AccountSecurity #TwoFactorAuthentication #IdentityVerification #AndroidSecurity #iPhone #FactoryReset #LostPhone #SMSVerification #PhoneVerification #Passkeys #SecurityKey #Phishing #PhishingProtection #CyberSecurity #OnlineSecurity #EmailSecurity #BISONKnowledgebase