Earlier quoted context omitted.
And ban their entire Google account
And delete all their data.
*make it hidden, they will of course keep the data for themselves :)
Google Workspace thinks my domain is an email provider (2025)
21–30 of 163 posts
Re: Google Workspace thinks my domain is an email provider (2025)
#22I think ditching google would've been a better choice.
Re: Google Workspace thinks my domain is an email provider (2025)
#23I think ditching google would've been a better choice.
Well, if the alternative was going to be Microsoft 365... not so sure :)
Re: Google Workspace thinks my domain is an email provider (2025)
#24I wonder how this list ended up being created anyway. Was it a long standing issue, or just some ai slop? web.com, web.org, web.net don't look like an email provider.
The rationale probably was that end users primarily identify the email provider by the subdomain, not the TLD, and therefore to prevent spoofing they block all domains where the subdomain corresponds to an email provider, regardless of the TLD. Like, they don’t want to allow gmail., and the same for all other email providers they know of.
Re: Google Workspace thinks my domain is an email provider (2025)
#25> Just for context, this is a premium domain with a very high premium renewal fee, no history of abuse obviously.
The registry premium domains on the new TLDs have several issues. The biggest IMO is a lack of price protection. Non-premium domains at least get the cohort based protection from section 2.10c of the registry agreement.
So, in addition to being treated as a 2nd rate domain, there’s nothing stopping the registry from cranking up the price if a domain gets popular. I don’t think it’s ever happened, but have never found contractual terms that forbid it.
I made a website about it a while ago after a registry reclassified one of my domains from standard to premium.
Re: Google Workspace thinks my domain is an email provider (2025)
#26Re: Google Workspace thinks my domain is an email provider (2025)
#27the last paragraph was probably most important one here, and the lesson is If you truly want to enforce a validation then it has to be in the backend, the client side validation is just additional luxury if you can afford it.
On a different note, the validations were added for genuine reasons and most likely there would be some discussions/debate on the scope/cost/benefits. I would imagine if some one were to do it a a business seriously then they would have some way to override it on use case basis.
Re: Google Workspace thinks my domain is an email provider (2025)
#28I wonder how this list ended up being created anyway. Was it a long standing issue, or just some ai slop? web.com, web.org, web.net don't look like an email provider.
scroll through a list of known email providers and you will notice they registered tlds for the countries they operate in, very typical for the old ones like yahoo yandex Freemail Hotmail etcpp
web.de is an oldschool German provider, as is gmx.de (and .at, .fr, .com, ...)
the regex smells like an inexperienced developer trying to be clever
Re: Google Workspace thinks my domain is an email provider (2025)
#29Crazy that .one gets locked, but .arpa is fully okay.
Re: Google Workspace thinks my domain is an email provider (2025)
#30Earlier quoted context omitted.
web.net, at least, absolutely is an email provider.
web.de is also a big email provider in Germany.
Yes and gmx (listed next to it) as well, and I’m pretty sure that gmx offered/offers multiples TLDs (gmx.net, gmx.de, gmx.at, …)
I think the same goes for Alice (big ISP, offering mail addresses, in multiple countries)
It looks like some of these wildcards are for mail providers who use multiple TLDs.