[58x14]

It's funny that I can think of a few legitimate use cases for this type of service:

- Deploying a new brand identity. I've worked with larger marketing agencies that may create many dozens of brands in a given month, and the process tends to be fairly manual and subject to various operational issues. There may be 20+ usernames/handles to "claim" as accounts across a broad spectrum of platforms, plus updating bios, profile pictures, 2FA/MFA, and, of course, the basic sign up and email confirmation process. I once scoped out how much of this could be automated, which was unsurprisingly cost infeasible relative to the current human method, and one of the components involved verification links, especially in scenarios with multi-tenant brands (such as a client wanting their new socials to be established under their own email, but wanting the agency to create those socials).

- User software provisioning. For all services that don't support some type of OAuth provisioning (through Okta, Atlassian, Google, etc) it would be helpful to create a new user, use scripts to post sign-up requests to non-OAuth services, use a function to verify the user's email, archive the email and present the user with their credentials.

- Tracking marketing/sales/promotion/update/announcement emails. Imagine if I could pay per user record for a Regex/SQL query; what if I want to estimate the amount of traction or activity of a competitor's email list? Rather than facilitating any interaction with the source users' email, it could simply give me a count of records, and perhaps a boolean for read/unread. Already that sounds like valuable data.

[paultopia]

Or just getting rid of marketing/sales/promotion/update/announcement emails. I regret not having used disposable emails (and phone numbers) for essentially everything ever touching anything involving politics, for example, as that would have kept tens of thousands of bullshit solicitations away from me over the years.

[tlavoie]

While I tend not to use disposable email addresses, I am a huge fan of having unique ones for many services or web site accounts. Not only does it tell me which ones have had a data breach or sold my info, but it also helps differentiate the spam that purports to come from that site, but isn't addressed to the specific one I _did_ use there.

[adql]

You could just have a *@wildcard e-mail addresses, you don't need to have one in specific established e-mail domain for any of those use cases.

[58x14]

Exactly what we were doing.

[charcircuit]

No way. No legitimate business wants to give the owner of [e-mail] the ability to hijack all of their brand accounts by hitting the reset password button. Even if you can change the email aftwards why take the risk of setting it up with a random person's account?

[willcipriano]

Especially since you can setup a catch-all on some domain you own so "creation" of the email address is as simple as typing it into the registration form on the site you want to use it on.

[NoZebra120vClip]

Surely this sort of sharing and access techniques violate most Terms of Service for any email I can conceive. It would be difficult to pull off a 100% legit service in this vein.