Google Workspace thinks my domain is an email provider (2025)
Google Workspace is blocking certain custom domains from signup because its frontend-only validation treats them as if they were public email providers, with the offending logic apparently based on an overbroad regex list. Commenters highlight how this exposes poor internal processes, opaque and unhelpful support responses that may be AI-generated, and a willingness to lose paying customers rather than fix low-priority edge cases. The incident feeds into broader worries about automated, unaccountable decision-making in large SaaS platforms and prompts many to advocate for alternatives such as self-hosting, smaller providers, or more conventional TLD choices.
Frontend-Only “Security” Check and Regex List
- Many are surprised the block was implemented entirely client-side while being described as “important security.”
- Several infer it’s really a crude anti-abuse / anti-fraud filter to stop users registering Workspace for domains that look like existing email providers.
- The regex seems to match provider-style labels (e.g., “web”, “gmx”, “alice”) across many TLDs; commenters note these ISPs/mail providers historically used multiple country TLDs.
- Some think the regex is very old or written by an inexperienced developer; others see it as quick “product engineering” that got shipped and never revisited.
Risk of Bypassing the Check
- Some applaud disabling the JS to proceed, noting this proves it’s only cosmetic.
- Others warn it’s risky: Google could later enforce the same rule server-side and lock the domain or account with little recourse.
Google’s Support, Priorities, and Power Imbalance
- Many recount similar experiences of opaque suspensions and useless support flows, even for paying Workspace / Google Cloud customers.
- There’s a strong sense that Google only meaningfully supports very large customers; smaller firms and individuals feel disposable.
- This episode reinforces fears about entrusting core business infrastructure (email, identity) to a provider that can cut access unilaterally.
Domain/TLD Peculiarities and “Unconventional” Choices
- Multiple users describe their own domains being rejected (short domains, numeric starts, unusual TLDs like .one, .email).
- Some argue this is the predictable cost of using “weird” TLDs; others counter that Google itself sells such domains and should handle them properly.
- There is side discussion on premium-priced new gTLDs, lack of price protection, and advice to prefer traditional TLDs (.com, .org, .net, ccTLDs).
Alternatives and Self-Hosting
- Commenters mention moving to other hosted providers (e.g., smaller email platforms) or self-hosting email as a way to escape Google’s ecosystem and policies.
AI-Generated Support and Automation Dystopia
- The odd support explanation (about “.web” and “fictitious domains”) is widely suspected to be LLM-generated; others caution against over-attributing to AI.
- Broader concerns emerge about automated decision-making, Kafkaesque appeal processes, and SaaS vendors using AI and scripts to gatekeep access without accountability.