How to Block a Domain Using Google Workspace, Block Sender in Gmail Easily 2026
By Impran M NLast checked against official docs
Unwanted emails from a spam domain or a persistent sender can clutter an inbox and, worse, carry a real phishing risk if left unchecked. Gmail gives individual users a quick way to block one sender, but that only protects their own inbox.
Stopping a domain for an entire organization means going into the Google Workspace Admin Console instead. This guide covers both paths: the personal block any user can do in seconds, and the admin-level route where domain-wide filtering rules actually live.
Before you start
- Super admin, or delegated Gmail-admin, access to the Google Workspace Admin Console; only needed for the org-wide block, not the personal one
01Decide whether you need a personal block or an admin-level block
Before touching any settings, work out the scope of the problem. If it's one annoying sender emailing just you, Gmail's own block-and-filter tools handle it without any admin involvement. If it's a spam or phishing domain hitting multiple people across the company, that needs to be handled centrally by a super admin through the Workspace Admin Console, since a personal block in one inbox does nothing to protect anyone else's.
02Block a sender directly in Gmail
Open the message from the unwanted sender, click More (the three-dot menu) next to Reply, and choose "Block [sender]." Gmail moves future messages from that address straight to spam. This is the fastest fix for a one-off nuisance sender, but it's scoped to your account only. It won't stop the same sender from reaching a colleague, and it won't catch that sender if they simply switch to a different address at the same domain.
03Set up a filter for more control
For anything beyond a simple block, Gmail's filter system is more flexible: from the search bar, use the dropdown arrow to create a filter matching the sender's address or entire domain, then choose to skip the inbox, delete automatically, or apply a label. Filtering by domain with a wildcard, such as *@spamdomain.com, catches senders who rotate addresses within the same domain, which a simple one-off block won't.
04Open the Admin Console's Gmail settings for org-wide control
For a domain that's targeting the whole organization, a super admin needs to go into the Admin Console, then Apps > Google Workspace > Gmail, which opens a settings page broken into sections: Setup, End-user access, Spam, phishing and malware, Compliance, and Routing. The "Spam, phishing and malware" section is where domain-level blocking and allow/block lists are configured for everyone in the domain at once, instead of one inbox at a time.

05Add the domain under Blocked senders
Inside "Spam, phishing and malware," scroll to Blocked senders and click Configure (or Add another rule if a blocklist already exists). Name the rule, add the domain or specific addresses you want to reject, and click Save. Google's own documentation is explicit that this can take up to 24 hours to fully apply, even though it typically happens faster, so a rule that hasn't caught a test email within the first few minutes hasn't necessarily failed.
06Review and confirm the block is working
Whichever route you used, check back afterward: personal users should look at Settings > Filters and Blocked Addresses in Gmail to confirm the rule is active, and admins should spot-check with a colleague or a test account, and the Admin console's audit log, to make sure mail from the blocked domain is landing in spam or being rejected rather than slipping through. If phishing was the original concern, it's also worth reporting the domain so Google's spam filters improve for other Workspace customers too.
When it doesn't work
The blocked domain still delivers mail a few minutes after saving the rule
Why: Google's own Workspace documentation states blocked-senders changes can take up to 24 hours to fully apply across the organization, even though they usually land sooner.
Fix: Wait up to a day before treating the rule as broken. Check the Admin console's audit log to confirm the change saved correctly.
A sender is blocked for you, but a colleague still gets their email
Why: A personal block or filter only applies to the Gmail account that created it; it has no effect on anyone else's inbox.
Fix: If the sender is a problem for more than one person, escalate to a super admin for an org-wide block under Spam, phishing and malware.
Blocking one domain doesn't stop the phishing attempts
Why: The sender is likely rotating across several look-alike domains rather than reusing the same one.
Fix: Report the messages to Google as phishing so its filters can catch the pattern, and add each new domain to the blocked senders list as it appears rather than assuming one entry covers all of them.
Frequently asked questions
Can I block an entire domain in Gmail without admin access?
As an individual user you can filter out a domain using a wildcard filter, but a true organization-wide block needs admin-level access through the Workspace Admin Console.
Will blocking a sender delete their previous emails too?
No. Blocking only affects future emails; messages already in your inbox stay unless you delete them separately.
Can a blocked sender still email other people in my organization?
Yes, unless the block is applied organization-wide by an admin through Spam, phishing and malware settings. A personal block only affects your own inbox.
How long does an org-wide block take to apply?
Google's documentation says up to 24 hours, though it typically happens faster. A test email still arriving a few minutes after saving the rule doesn't mean it failed.
How do I unblock a domain or sender later?
Remove the filter or blocked-address entry from Gmail's Filters and Blocked Addresses settings, or have an admin edit the Blocked senders rule in the Admin Console.
Sources and last check
Personal Gmail block and filter steps, and the Admin Console path (Apps > Google Workspace > Gmail > Spam, phishing and malware > Blocked senders), were checked in September 2026 against Google's official Workspace and Gmail help documentation. That check corrected the propagation guidance: Google's own docs say a blocked-senders change can take up to 24 hours to fully apply, not the couple of minutes the original draft implied.
About the author

Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.



