Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google Workspace thinks my domain is an email provider

An error that persists as of August 2026 prevents users from creating a Google Workspace account for their company, leading them to believe their domain has previously been used as an email provider. Despite extensive research, no official documentation by Google addresses the issue, nor does it provide a solution. The problem is not isolated, as community threads suggest it is a widespread issue.

One such thread was submitted by the Ukrainian Ministry of Economy, who encountered the same error for their domain, me.gov.ua. Community "experts" offer minimal guidance, advising users to try creating the account on different browsers or devices, and even directing them to high-level support specialists and product engineers for review.

After multiple attempts, users are left frustrated and desperate for a resolution. The error is triggered by a local input validation function in Google's sign-up page, which checks the domain against a regex list of email providers. However, the list contains numerous odd entries, including entries like web\\..*, which incorrectly flag certain domains as email providers, preventing their acceptance.

One example is the web.[tld] domains, which erroneously triggers the error, even for legitimate domains like the one used by the Ukrainian Ministry of Economy. A single entry, me\\..*, is identified as the culprit preventing me.gov.ua from being accepted. In essence, Google engineers have mistakenly categorized all web.[tld] domains as email providers, leading to this frustrating validation issue.

Disabling this function allows users to successfully complete the sign-up process. The Ukrainian Ministry of Economy, left with no other options, opted to use Microsoft 365 instead of Google Workspace.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at blog.elis.cc →

More in Tech

A Windows Service is Down. Now What?

It doesn't matter if it's SQL Server, IIS, a background agent, or a custom app — when a Windows service goes down, the investigation is always the same five moves.

  • Confirm service status and start type before taking action
  • Map service transitions using Event ID 7036 in Windows logs
  • Read application's own logs for reason service stopped

More from Sunday 23 August →