Rent Gmail for GitHub: Machine Users and CI

Updated October 13, 2026 · 7 min read

GitHub confirms every new account with an 8-digit launch code sent by email, and it emails a second code whenever you log in from a device it does not recognize. If you don't want that tied to a personal inbox — a machine user for CI, a client handover, a sandbox for testing GitHub Actions — you need a working address that GitHub is willing to email in the first place, which rules out most short-lived, throwaway mail domains.

This guide is about renting the inbox for those jobs. If a sign-up is already failing before any email arrives, start with GitHub verification email not received: 5 causes and fixes, which diagnoses captcha errors, blocked networks and rate limits.

Three GitHub jobs that need their own inbox

GitHub's terms allow one free personal account per person, so extra accounts should have a clear purpose:

A machine user. The exception for automation: a separate account you manage for CI, bots or repository access. For many jobs a GitHub App or a deploy key fits better and needs no extra account, so reach for a machine user only when the job genuinely needs an account identity.
A client hand-over. Create the account on the client's behalf with their details, then switch the account email to the client's own address and add them as an owner of an Organization where you can, so nothing depends on your personal login.
A CI or Actions sandbox. Keep test accounts to the number your tests need, script the inbox step through the API (below), and space the sign-ups out.

How GitHub verifies a new account by email

When you sign up with an email address instead of continuing with Google, GitHub asks for a username and password, runs a puzzle to confirm you're not a bot, then sends "Your GitHub launch code" with an 8-digit number. Type it in and the account is live. Later, signing in from an unfamiliar browser or network without two-factor authentication triggers "[GitHub] Please verify your device," a 6-digit code sent to the same address. Both codes are single-use and expire fast, so it helps to have the inbox open before you submit the form.

Why a rented Gmail (or iCloud) inbox works here

GitHub blocks a large share of throwaway mail domains outright, which is why short-lived, throwaway-looking addresses often fail before any code is even sent. A rented inbox on OTPGmail is a real @gmail.com or @icloud.com mailbox, so it passes GitHub's domain check the same way your own address would. Pick GitHub from the service list, choose Gmail or iCloud as the inbox type, and rent — the launch code then shows up directly on your order page, typically within about 1 minute, with no mailbox login required. iCloud is usually cheaper and works exactly the same way for GitHub, so it's worth choosing when Gmail stock is thin.

If nothing arrives, you're not out any money: an order with no code after 25 minutes cancels itself and refunds automatically. Once a code does land, 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. If you expect a device-verification email, trigger it right after sign-up, because some sources close the inbox about 25 minutes after the latest code.

Renting a Gmail for GitHub: step by step

Open GitHub's sign-up page and get as far as the password and username fields.
On the GitHub inbox page, choose Gmail or iCloud and rent an address.
Paste that address into GitHub's email field, finish the password and captcha.
Watch your OTPGmail order page — the launch code usually appears within about 1 minute, and 96% of GitHub orders receive one inside the 25-minute window.
Enter the 8 digits on GitHub's page. A device-verification email lands on the same order at no extra charge within the order period, if the service sends more than one code (the limit is shown on the rental page).
Turn on two-factor authentication under Settings → Password and authentication right away, and save the recovery codes — a rented inbox only receives codes during the order period (extra codes cost nothing within it when the service sends more than one; the limit and time window are shown before you rent), so you don't want to depend on it for future logins.

Developers automating this — for CI test accounts or a signup-flow check — can skip the browser step entirely: POST /v1/orders with { "service": "git", "domain": "icloud.com" }, then poll GET /v1/orders/{orderId} every few seconds until otp is populated. Full request and response shapes are in the API docs.

When the code does not arrive

A failed attempt costs nothing, because an order with no code refunds itself after 25 minutes. If it keeps happening, the sign-up was almost certainly stopped before the email step: a captcha that would not verify, a VPN or data-center network, or too many recent sign-ups from one IP address. GitHub verification email not received walks through each cause and its fix, and the 7-point checklist applies to any service.

One rental-specific case: if GitHub says "Email is invalid or already taken" and you are sure the address is unused, cancel the order before a code lands (that refunds you) and rent a fresh address. For test suites, renting Gmail inboxes for sign-up flow testing covers the QA angle in more depth.

Choosing Gmail or iCloud, and what to do afterward

Both inbox types pass GitHub's checks equally well, so the choice usually comes down to stock and price — iCloud tends to run cheaper. Our Gmail rental pillar page covers how the rental mechanics work across every service if this is your first order; rent an inbox now to see live stock for GitHub in either format.

Once the account exists, treat the rented address as short-lived by design. Add an email you actually control under Settings → Emails if the account is meant to last, and keep the recovery codes somewhere safe. GitHub doesn't distinguish a rented inbox from any other real address — accounts get suspended for what happens after sign-up, such as unwanted bulk messages or malware, not for how the launch code was received. OTPGmail is not responsible for accounts that break GitHub's terms.

Frequently asked questions

Should CI use a machine user or a GitHub App?

Where you can, prefer a GitHub App or a deploy key: they need no extra account and can be scoped tightly. Use a machine user when the job needs an account identity, and keep it to one per purpose.

Can a client take over an account you created for them?

Create it on their behalf with their details, switch the account email to their own address and hand over ownership through an Organization where possible. Read GitHub's terms on account ownership first, since they govern what is allowed.

Will GitHub suspend an account created with a rented inbox?

Not because of the inbox itself. A rented address is a real mailbox, indistinguishable from any other. Suspensions come from what the account does afterward — mass sign-ups, malware, or other Terms of Service violations.

Can I automate GitHub sign-ups for testing?

Yes, within GitHub's own limits. Use the API to create an order with service: "git" and poll for the code, but keep GitHub's one-account-per-person rule in mind; use machine users for bots and CI rather than a pile of personal accounts.

What if I need the code for a device-verification email, not sign-up?

Same order, same inbox, while the order can still receive codes. 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, and some sources close the inbox about 25 minutes after the latest code, so trigger the device check right after sign-up.

Need GitHub email verification right now? Rent an inbox, check live prices and stock, or read the API docs to wire it into a script.