GitHub Verification Email Not Received: 5 Fixes
GitHub is usually quick to send verification email: on rented inboxes the code typically shows up after about 1 minute. So when a GitHub sign-up stalls, the mailbox is rarely the culprit. The cause is almost always one of the five below. Work through them in order and you will find yours.
This guide is for diagnosis, whatever inbox you use. If you already know you want a separate address for a machine user, a client hand-over or CI, see Rent a Gmail for GitHub: machine users, hand-overs and CI; for live stock and prices, the GitHub inbox page. For other services, the 7-point checklist for a verification code that has not arrived applies.
Start here: match your symptom
| What you see | Most likely cause |
|---|---|
| The form is submitted and no email ever comes | Captcha unfinished, wrong address, or GitHub stopped the sign-up early (causes 1, 2, 4) |
| "Unable to verify your captcha" | An extension, an outdated browser or a VPN (cause 2) |
| "Email is invalid or already taken" | Address already in use, blocked domain or plus-address (cause 3) |
| The captcha keeps failing and pages load slowly | A data-center IP or a free VPN (cause 4) |
| The first account worked, the next ones fail | Per-IP rate limit (cause 5) |
| A code arrived but GitHub rejects it | An older code replaced by a newer one (three emails below, and the FAQ) |
What GitHub checks when you sign up
A GitHub sign-up passes four gates: a valid email address that is not already in use, a strong enough password, a captcha puzzle, and finally an 8-digit code sent by email, the launch code. In parallel, GitHub scores the risk of the request from your IP address and browser. A failure can happen at any gate, and the error message does not always say which one.
GitHub sends three different emails
Part of the confusion is that GitHub has more than one verification email, and each fails for different reasons:
| When GitHub sends it | What it contains | |
|---|---|---|
| Launch code | At sign-up, after the captcha | An 8-digit code, subject "Your GitHub launch code" |
| Device verification | A login from a new device or network on an account without two-factor authentication | A 6-digit code, subject "[GitHub] Please verify your device" |
| Email verification link | You add or change an address under Settings → Emails | A button that confirms the address |
If you are waiting for the wrong one, nothing looks broken on your side: a launch code never arrives during a login, and a device code never arrives at sign-up. For an address that is still unverified, Settings → Emails offers a resend for the verification link.
1. The launch code never arrives
This is the most common complaint. Check these in order:
- Is the address exactly right? One stray space or missing character sends the code elsewhere. Paste it; do not type it.
- Did you finish the captcha? GitHub only sends the code after the puzzle is solved. If the page still shows the puzzle, no email has been sent yet.
- Have you waited long enough? The code usually arrives after about 1 minute, but allow two or three minutes before doing anything else.
- Go easy on "Resend". Each new code can invalidate the previous one. Resend once, then wait.
- On your own mailbox, check the junk folder and any filters.
If you are using a rented inbox and the code still does not show, GitHub most likely stopped the sign-up before the email step (see causes 2, 4 and 5). In the last 30 days, 96% of GitHub orders on Почта received a code; most of the rest were blocked at the captcha or by IP reputation, so no email was ever sent. Those orders are cancelled after 25 minutes and refunded in full.
2. "Unable to verify your captcha"
This message means the puzzle did not load or its result was not accepted. The usual suspects:
- An ad blocker or script blocker interfering with the puzzle.
- An outdated browser, or JavaScript or third-party cookies switched off.
- A VPN or proxy whose IP address has a poor reputation.
Fixes that work:
- Retry in a private window, where extensions are usually disabled.
- Switch to another, fully updated browser.
- Turn the VPN off, or change server, and reload the page.
- Wait 5–10 minutes. GitHub sometimes locks the captcha briefly after several attempts in a row.
3. The email domain is rejected
GitHub may say "Email is invalid or already taken", or refuse without much explanation. Three typical reasons:
- The address already belongs to an account. Every GitHub account needs its own address.
- The domain is blocked. GitHub blocks many 10-minute mail and temp-mail domains because of abuse. A real @gmail.com or @icloud.com address avoids the problem entirely; our comparison of real inboxes and 10-minute mail explains the difference.
- Plus-addressing. Addresses such as name+github@… are sometimes treated as aliases and refused. Use the plain address.
4. VPNs, proxies and network reputation
GitHub restricts sign-ups from IP ranges with a history of abuse — typically data centers, free VPNs and public proxies. The symptoms are an unusually hard captcha, very slow page loads, or a rejection right after you click "Create account".
The quickest test is to switch to mobile data and sign up again. If that works, your previous network was the problem. If company policy requires a VPN, pick a stable server and stay on it for the whole sign-up.
5. Too many sign-ups from one IP address
After a few accounts created back to back from the same IP address or browser, GitHub starts failing the captcha or withholding the code. That is not a bug. It is a rate limit, and it exists by design.
It also reflects GitHub's rules. The Terms of Service allow one free personal account per person. For automation, GitHub permits a separate machine account (a machine user) that you manage for CI or bots, and teams should share work through an Organization rather than a pile of personal accounts. Read the terms first, create only the test accounts you need and space the sign-ups out. Почта is not responsible for misuse.
Using a rented inbox for the launch code
If the account should not be tied to your personal address (a machine user, a client hand-over, a sandbox for GitHub Actions), a rented real inbox covers the email step. Choose GitHub on the rent page, pick Gmail or iCloud under "Inbox type", paste the address into github.com/signup and read the 8-digit launch code on your order page; no code within 25 minutes means an automatic, full refund. The full walkthrough, including the API, is in Rent a Gmail for GitHub, and live prices are on the GitHub inbox page. GitHub accepts iCloud addresses as readily as Gmail, and iCloud is usually the cheaper of the two.
After sign-up: what to do right away
Extra codes cost nothing within the order period when the service sends more than one; the limit and time window are shown before you rent. That can cover the device verification code from a new machine, but do any step that needs another code (a second device, an extra confirmation) right after sign-up, because some sources close the inbox about 25 minutes after the latest code. Then:
- Turn on two-factor authentication with an authenticator app or a passkey, so later logins do not depend on email.
- If the account will live on, go to Settings → Emails, add an address you own and make it primary.
- Save the recovery codes GitHub gives you.
If GitHub sign-ups are part of an automated pipeline, the email OTP API guide shows how to create an order and read the code in Python or Node.js.
Frequently asked questions
The launch code arrived, but GitHub says it is wrong or expired. Why?
Each new code can invalidate the previous one, so a code from an earlier attempt stops working as soon as a newer one is sent. Use the most recent email, type all eight digits promptly, and resend only once before waiting.
Does "Email is invalid or already taken" mean the address is blocked?
Not necessarily. The message appears when the address is already attached to an account, when its domain is on a blocklist, and sometimes for plus-addresses such as name+github@…. Try the plain address first; if it belongs to an old account, use a different one.
Why do I get a 6-digit code when I log in but an 8-digit code at sign-up?
They are different emails. The 8-digit launch code confirms a new account; the 6-digit device verification code appears when you log in from a new device or network on an account without two-factor authentication. App-based two-factor authentication removes the second one.
How long should I wait before trying again?
The code usually arrives after about 1 minute. Allow up to five minutes before you resend, and ten if you suspect a captcha lock. A rented order that shows nothing after 25 minutes refunds itself, and GitHub almost certainly stopped an earlier step, so change network or browser before renting again.
Can I fix a stuck sign-up without a new address?
Sometimes. If the account already exists and only the email is unverified, log in and use the resend option under Settings → Emails. If the sign-up never completed, a clean retry usually works before a new address is needed: wait ten minutes, use a private window, turn the VPN off and submit once.
Need an address for GitHub right now? Rent an inbox, check live prices and stock, or read the API docs to automate it. More troubleshooting lives in the guides, including ChatGPT verification email not received.
