A real phone number
for GitHub.

How GitHub verification works

GitHub can send two-factor authentication codes by text message, but only to countries on its supported list. It strongly recommends a TOTP app as the main method.

Because SMSCreation numbers are real mobile numbers, GitHub treats them like any other phone: the code is delivered to your number and shows up in your dashboard inbox straight away.

Why it works with WhatsApp, Facebook, Telegram & Google

Apps check more than the digits: they look up the line type, the country format and whether the number can actually receive their code. Every SMSCreation number is a real mobile number in its country's official format — not a VoIP line — so it passes those checks the same way a SIM in your pocket does.

And we stand behind it with a 7-day replacement guarantee: if your number doesn't work with WhatsApp, Facebook, Telegram, Google or any app you need, we replace it free with a new number in the same country — or refund 100% if you prefer.

• Non-VoIP, real mobile line type — line-type checks see an ordinary SIM number, not a VoIP line
• Official country format with the right country code, prefix and digit count
• Unlimited incoming SMS and calls — codes arrive by text or through the “call me” option
• Private to you — never listed on public SMS sites, so it isn't flagged or rate-limited
• Yours for as long as you want — re-verification and account recovery keep working

GitHub SMS two-factor details

GitHub accepts text messages as a two-factor authentication (2FA) method, and it matters because GitHub makes 2FA mandatory for accounts that contribute code. Selected users get a 45-day setup window. To set up SMS, click your profile picture → Settings → Password and authentication → Enable two-factor authentication. Complete the CAPTCHA, choose your country code, enter the mobile number and click Send authentication code. Type the code from the text, then download and save your recovery codes before 2FA switches on.

Be clear-eyed about GitHub's stance. It strongly recommends a TOTP app over SMS, and it only sends 2FA texts to the countries on its supported list, about 130 of them, because of delivery rates. Organizations and enterprises can block members who use SMS 2FA. After you configure 2FA, your account enters a 28-day check-up: complete 2FA once in that time, or GitHub prompts you on day 28. To swap numbers, go to Settings → Password and authentication → Two-factor methods and click Edit next to SMS.

Code

Authentication code by text message

Supported countries

About 130, on GitHub's official list

Check-up

28 days after setup you must successfully perform 2FA

Recovery

16 recovery codes; regenerate once used

Where to change the number

Settings → Password and authentication → Two-factor methods → Edit (SMS)

Common GitHub problems and fixes

• Your country isn't offered for SMS → GitHub only texts countries on its supported list → choose a number from a listed country, or use a TOTP app.
• An organization blocks you → some organizations disallow SMS 2FA → enable 2FA with a TOTP app and disable SMS to regain access to their content.
• Codes arrive late or not at all → GitHub itself calls SMS delivery unreliable → add a TOTP app or security key as a second method. Our guide "Verification code not received" covers the phone side.
• Lost the phone → sign in with one of your 16 recovery codes, then edit the SMS number under Two-factor methods.

Where a number fits in GitHub's mandatory 2FA rollout

GitHub's requirement is aimed at people who contribute code, and it arrives as a notice with a 45-day window to enrol. When you pick text messages, the flow is CAPTCHA, country code, number, Send authentication code, then the code itself. The step people skip is the last one: GitHub shows 16 recovery codes and wants them downloaded before 2FA goes live. Keep them somewhere that doesn't depend on the phone line.

The 28-day check-up is the second checkpoint. During those four weeks GitHub wants to see one successful 2FA sign-in; if it hasn't, it prompts you on day 28.

• SMS goes only to numbers in the roughly 130 countries GitHub lists as supported for text delivery.
• Organizations and enterprises can lock out members whose only second factor is a text message.
• Edit the number later under Password and authentication → Two-factor methods, using the Edit button beside SMS.

Picking the country of a GitHub 2FA number

Country matters more on GitHub than on most sites, because a number from an unlisted country simply isn't offered as an option. Check GitHub's supported-countries page before you choose, then pick a number from a country that appears there. If you belong to an organization that disallows SMS, set up a TOTP app as well and disable the text method so its repositories open for you again.

Verify GitHub with your number in 4 steps

1. 01Choose a country and pick a mobile number.
2. 02Pay in crypto or from your wallet — from $1.80 a month on the yearly plan.
3. 03Enter the number in GitHub with its country code and request the code.
4. 04Open your SMSCreation inbox, copy the code and you're verified.

Tips for GitHub

• Check GitHub's list of countries where SMS authentication is supported first.
• Save your 16 recovery codes when you enable 2FA.
• Add a TOTP app or security key, since some organizations block SMS 2FA.

Included with every number

• Unlimited incoming SMS — every verification code and message, no cap
• 500 outgoing SMS every month
• 1,000 outgoing call minutes every month
• Unlimited incoming calls
• Keep the number for as long as you want — auto-renew keeps it yours
• Works with WhatsApp, Facebook, Telegram, Google & Instagram — guaranteed: free replacement or 100% refund within 7 days
• 7-day replacement guarantee — if the number doesn't work with WhatsApp, Facebook, Telegram or Google, we replace it free or refund 100%; plus a no-questions-asked refund if you haven't used it for any call or SMS

Private by design — keep GitHub separate from your identity

A SMSCreation number keeps your personal SIM, name and bank card out of your GitHub account. No KYC, no ID, no card — crypto only.

• No KYC — no ID, passport, selfie or proof of address, ever
• No real name required — sign up with an email and a password
• No card, no bank account — crypto only, so no payment details are linked to you
• No phone number needed to sign up

Popular countries for GitHub numbers

USUnited States+1CACanada+1BRBrazil+55GBUnited Kingdom+44DEGermany+49FRFrance+33NLNetherlands+31ESSpain+34AEUnited Arab Emirates+971INIndia+91SGSingapore+65AUAustralia+61

Keep it as long as you want

GitHub may ask for your number again — on a new phone, after a reinstall or for account recovery. Keep your number renewed and it stays yours, so you can always receive the code.

Not what you needed? Our 7-day replacement guarantee — if the number doesn't work with WhatsApp, Facebook, Telegram or Google, we replace it free or refund 100%; plus a no-questions-asked refund if you haven't used it for any call or SMS.