Testing a sign-up flow, spinning up a throwaway account for a demo, or checking what a fresh GitHub account looks like from the inside? A disposable UseTemp address can receive GitHub's launch code — we verified it ourselves. Here is how developers use it, and the point where you should stop and use a real mailbox instead.
Yes. On 21 October 2026 we created a fresh @usetemp.org address and used it on GitHub's sign-up page. GitHub accepted the address and sent its launch code; the email arrived in the UseTemp inbox within about a minute. No domain error, no silent disappearance — the code was simply there, ready to copy into the sign-up form.
That result is not a given with disposable email. Some services quietly refuse to deliver to temporary addresses at all. GitHub, as of our test, delivers normally — which makes a temp address a practical tool for short-lived development work.
[email protected], [email protected].The honest warning. Never put a temporary address behind the GitHub account that holds your real work. Your main account is your developer identity: repositories, organisation access, and account recovery all hang off its email. UseTemp addresses expire after 10 days, and every message is deleted 24 hours after it arrives. A password-reset or security email sent to an expired address goes nowhere — and there is no support process that will hand the account back to you.
One more, out of respect for the platform: GitHub's terms restrict running multiple free personal accounts, so treat temp addresses as a testing tool — walk the flow, learn what you need, delete the test account — not as a way to maintain a stable of extra identities.
Yes. We tested it ourselves on 21 October 2026 with a fresh @usetemp.org address: GitHub sent its launch code and the email arrived in the UseTemp inbox within about a minute.
Testing: walking through a real sign-up flow end to end, creating short-lived test accounts for demos and QA, and checking what notification emails look like — without touching a real mailbox. It suits work that lasts hours or days, not accounts you need for years.
Please don't. Your main GitHub account is your developer identity — it holds your code, your organisation access, and your recovery path. UseTemp addresses expire after 10 days and emails are deleted after 24 hours, so a recovery or security email sent later would go nowhere. Use a permanent address you control for the account that matters.
While the address is alive — up to 10 days — yes, mail to it lands in the inbox, including GitHub notifications. But every message is deleted 24 hours after it arrives, so it is no good as a long-term notification or CI alert address. Use a real mailbox for anything that must keep working.
No. UseTemp is receive-only by design, which is why it works for code-based verification like GitHub's launch code but not for any flow that requires you to send a reply.