HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wesbos
burner-email-providers
JavaScript2018–2022
wesbos / burner-email-providers

burner-email-providers

A list of temporary email providers

4Distinct people
7Mentions
0Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A list of temporary email providers

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2018-05-02 22:29:41 UTC to 2022-04-11 08:20:55 UTC.

012342018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404

What Hacker News says

7 sources
Hi, can you please not block Firefox Relay for sign-ups, which I use to protect my email address? I don't trust your company with my real email address (I don't trust any company) and I think that's fair. EDIT: for why you should reconsider blacklisting Relay, one of Relay's developers gives a good answer at https://github.com/wesbos/burner-email-providers/pull/339#is... Another request: if you used a blocklist found on GitHub I'd really appreciate a link to it so I can make my argument for why Relay deserves to be spared.
In Ask HN: Why aren't devs making desktop apps any more?
> Setting limits (...) makes it harder to abuse services with those identities. Almost no legitimate users actually need truly unlimited email addresses (...). Even generous limits would help to avoid many problems. Note that Relay already rate-limits customers: > we limit our free users to 5 total aliases, and we rate-limit our premium customers so they cannot create large-scale throw-away aliases for abusive sign-ups and behaviors. https://github.com/wesbos/burner-email-providers/pull/339
In Mozilla's Firefox Relay to be added to disposable-email-domains blacklist
We're actively reaching out to maintainers of such lists (see e.g. [1]) to get us removed, and take a number of measures to make that more palatable (see also [1]). And of course Relay is a bit different from services like Mailinator, where email addresses are usually actually single-use: Relay addresses remain active until their owner actively disables them. Possibly in the future it might also be possible to bring your own domain, but I don't think we have any concrete plans for that that we can share. That said, no solution is perfect, and I expect that there will likely always be situations where you will be forced to fall back to a regular email address. [1] https://github.com/wesbos/burner-email-providers/pull/339
In Firefox Relay
https://github.com/wesbos/burner-email-providers/pull/226 more informations there. In case anyone wasn't aware, @tuptuptuu is a throwaway account seemingly created solely for the purpose of adding the hey.com domain to disposable email lists. See similar pull requests this person has filed: andreis/disposable#50 martenson/disposable-email-domains#244 wesbos/burner-email-providers#226 micke/valid_email2#153 so you are a liar.
In Ask HN: Startup CTO using big Twitter following to harass me, what should I do?
There was a ShowHN (can't find it) about an API that pre-qualifies email addresses. I think it just checked if the email syntax is valid (see related discussion https://news.ycombinator.com/item?id=16799976), if the domain really exists and if the domain is a known burner domain (I use this list https://github.com/wesbos/burner-email-providers/). Personally I can't use such an external service (in Europe) because with GDPR regulation sending a third-party a list of email addresses without user consent is better avoided.
In Ask HN: Help me choose a REST API to build

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.