How to Block a Domain or Email Address in Google Workspace

The short answer
A Google Workspace admin blocks a domain in the Admin console: Apps, Google Workspace, Gmail, Spam, Phishing and Malware, then Blocked senders and Configure. Add the domain or email address, optionally set a rejection notice or an approved-senders exception, and save. Changes can take up to 24 hours, though they usually apply sooner.
Admin console path to block a domain or email address org-wide (Gmail > Spam, Phishing and Malware > Blocked senders), plus exceptions and how to undo it.
On this page
- 01How to block a domain in Google Workspace: step by step
- 02Block a single email address in Google Workspace
- 03Block many domains at once with an address list
- 04Allow one sender from a blocked domain
- 05Reject or quarantine: what Blocked senders does
- 06Before you block a whole domain
- 07What to do when the block is not working
- 08Blocking in personal Gmail is a different setting
- 09A per-inbox layer next to the admin block
To block a domain or a single email address for your whole organisation, use the Google Admin console: Menu, Apps, Google Workspace, Gmail, Spam, Phishing and Malware, then the Blocked senders setting. You enter the domain or the full address, save, and Gmail rejects mail from it for the users the setting covers. You need the Gmail Settings administrator privilege.
This guide gives the exact path first, then the single-address and bulk-list variants, how to allow one sender back through, and what to check when the block seems not to work. Last verified against Google's Admin help in November 2026. Menus change, so treat the button names below as the current wording, not a promise.
How to block a domain in Google Workspace: step by step#
Sign in to admin.google.com with an account that has the Gmail Settings administrator privilege (a super admin has it). Then follow these steps.
- 1
Open the Gmail spam settings
In the Admin console, go to Menu, then Apps, then Google Workspace, then Gmail, then Spam, Phishing and Malware.
- 2
Find Blocked senders and click Configure
Under Blocked senders, click Configure the first time. If a setting already exists, click Edit to change it, or Add another rule to create a new one.
- 3
Name the rule and add the domain
Enter a name or description, then add the domain you want to block, for example spamsite.example. Add several entries one at a time, or use a saved address list (covered below).
- 4
Optionally set a rejection notice
You can edit the text that blocked senders receive when their message is rejected. Keep it short and neutral.
- 5
Optionally add an exception
To let specific people or domains through, tick the bypass option and pick an approved senders list. More on this below.
- 6
Save and test
Click Save. Send a test from the blocked domain, or check the message in Email Log Search under the Admin console's reporting tools, to confirm the setting is applied.
Propagation can take up to 24 hours
Block a single email address in Google Workspace#
Blocking one sender uses the same Blocked senders setting, so the steps above apply unchanged. In step 3, enter the full address, for example [email protected], instead of the domain. Everything else, including the optional rejection notice and exception, works the same way.
Use an address block when one person is the problem and the rest of the domain is legitimate. Use a domain block when every sender on it is unwanted. Gmail's own per-user Block sender is a separate, personal setting, covered in how to block a sender in Gmail.
Block many domains at once with an address list#
For more than a handful of entries, build an address list instead of typing each one into the rule. Go to Menu, Apps, Google Workspace, Gmail, Routing, click Manage address lists, then Add address list. Name it, then enter entries one at a time with Add address, or several at once with Bulk add addresses, separated by commas. Save.
Back in Blocked senders, choose Use existing list, or Create or edit list, and select it. Enter domains as domain.com or @domain.com. Google notes that wildcard entries such as *@domain.com are accepted by the form but have no effect, so do not rely on them to cover subdomains.
Allow one sender from a blocked domain#
If one vendor or customer shares a domain you have blocked, add an exception rather than removing the block. In the Blocked senders rule, tick the option to bypass the setting for messages from addresses or domains in an approved senders list, and choose that list. Approved senders still get the regular virus and spam protection. The full flow, including how approved lists are built, is in how to allow a sender in Google Workspace.
Reject or quarantine: what Blocked senders does#
Many guides say Blocked senders offers a choice between reject and quarantine. Google's own page for the setting describes automatic rejection only: the sender gets the rejection notice you set, and the mail never reaches your users. It names no quarantine option for this setting.
If you want to hold mail for review before deciding, use a content compliance rule, which lets you choose Reject, Quarantine or Modify based on conditions you set. The table compares the options.

| Method | Where to configure | Effect on the mail | Best for |
|---|---|---|---|
| Blocked senders | Gmail > Spam, Phishing and Malware | Rejects the message, with an optional custom rejection notice | Domains or addresses you never want mail from |
| Content compliance rule | Gmail > Compliance > Content compliance | Reject, quarantine or modify, based on the conditions you set | Domains where some mail is legitimate, or where you want to review first |
| Individual user block | Gmail settings, per user | Sends that sender's future mail to spam for that one user | One person blocking a sender without admin involvement |
Before you block a whole domain#
Blocking a domain is a blunt instrument, so check these before you save.
- Is the domain specific enough? Blocking a shared provider such as gmail.com, outlook.com or yahoo.com cuts off every customer, partner and job applicant who uses a personal account there.
- Does anyone on your team work with someone at that domain? A vendor or client sharing the sending domain is the most common cause of support tickets after a block.
- Would a narrower rule do? If only some messages are unwanted, a content compliance rule that matches on patterns is usually safer than a whole-domain block.
Blocking a shared domain cuts off everyone on it
What to do when the block is not working#
Several things can make it look as if mail from a blocked domain is still arriving.
| Symptom | Likely cause | Fix |
|---|---|---|
| Mail from the domain still arrives after saving | Propagation is not complete, since changes can take up to 24 hours | Wait and test again, and use Email Log Search to see whether the setting is evaluated on inbound messages. |
| Mail still arrives after 24 hours | The setting was saved for a different organizational unit than the affected users | Check which organizational unit the rule applies to and save it for the one that contains the affected users. |
| Blocked mail still reaches people through a Google Group | Google says blocked messages might still reach users in Google Groups when Groups for Business is on, depending on each member's group settings | Check the group's and the members' email delivery settings. Google lists this as a known gap in the setting. |
| Mail arrives from a similar domain or a subdomain | The sender is rotating across variants, and Google's help does not say whether a domain entry covers subdomains | Add each variant that sends mail as its own entry, then send a test from one to confirm. |
| The From address looks blocked but mail still arrives | The From header is spoofed while the actual sending domain is different | Check Email Log Search for the sending domain and the SPF and DKIM results, and block that domain. |
| Legitimate mail is also rejected | A vendor or customer uses the blocked domain | Add an approved senders exception, or replace the domain block with a narrower rule. |
Use the admin audit log to see who changed the rule
Blocking in personal Gmail is a different setting#
Everything above is the org-wide admin block. If you only use a personal Gmail account, or you want to block a domain for your own inbox without admin access, see block a domain in personal Gmail instead.
A per-inbox layer next to the admin block#
The admin block is a fixed list you maintain in the Admin console. It suits domains you are sure you never want mail from. For noise that changes from week to week, a second layer at the inbox level can help, because it does not need a list update each time.
We build AI Emaily. Its cold-email filter scores intent and offers a per-sender or per-domain Block in your own inbox. That is different from an org-wide admin rule: it works for the mailbox you connect, not for everyone in the organisation, and it does not replace the Admin console setting. On Google Workspace, your administrator needs to allow third-party app access before AI Emaily can connect. There is a 7-day free trial on Pro or Autopilot. See the pricing page for plans.
Frequently asked
See it in AI Emaily
Keep reading
Sources
- Google Workspace Admin Help: Block messages from an email address or domain
- Google Workspace Admin Help: Use address lists to apply settings to specific people or domains
- Google Workspace Admin Help: Control message delivery based on message content
- Google Workspace Admin Help: Manage spam, phishing, and malware

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.