Skip to content
iBlockSpam
New: per-domain pricing, 30-day money-back guarantee

Business spam filter for Microsoft 365, Google Workspace & cPanel

Spam stops at your domain. Business mail gets through.

iBlockSpam filters every message for your whole domain before it reaches Microsoft 365, Google Workspace or your own server. Each person reviews their own quarantine. You pay per domain, not per mailbox.

The idea in 15 seconds.

One filter in front of your whole domain: junk is held back, real mail goes straight through.

All videos
Less noise. More of what matters. A wall of red spam envelopes dissolves, three clean messages remain, and the iBlockSpam mark appears: spam is held back before it reaches your team.
How a domain-wide filter works, in 15 seconds Animated junk envelopes march towards a mailbox and bounce off a protective shield, while a legitimate message passes straight through.
A doorman for your email A hotel doorman checks every arriving envelope, turns away junk and waves trusted mail inside, like a filter in front of your mail server.

See the portal.

This is what you get after the switch: every domain's status, mail delivered and held, Domain Watch, lookalike domains, DMARC monitoring and a setup checklist. Click through it with sample data, no sign-up needed.

Open the portal demo
iBlockSpam portal dashboard with sample data: three domains with their status (protected and verified, mail routed, next step), and an overview table of messages delivered and held as spam over 30 days, quarantine counts, daily trend lines and lookalike domains found.
Your domains at a glance: status, 30-day delivered and held counts, quarantine and lookalikes. Sample data. Open it in the demo

What gets checked before a message reaches anyone.

A phishing email looks ordinary in an inbox. In its headers, it gives itself away. Scroll through the checks.

Message headers
Return-Path: <bounce@mailer-xq7.example>Received: from mailer-xq7.example ([203.0.113.77])From: "Microsoft 365 Billing" <billing@micros0ft-billing.example>Reply-To: payments-desk@freemail.exampleSubject: Payment failed — update your card todayAuthentication-Results: spf=fail; dkim=none; dmarc=failLink: https://micros0ft-billing.example/loginAttachment: invoice_0921.html

Illustrative message using reserved example domains.

  1. 1

    Look-alike sender

    The display name says Microsoft. The domain is micros0ft-billing — a zero where the o should be. Impersonation checks compare senders against the names people trust.

  2. 2

    Replies go somewhere else

    Reply-To points at a free mailbox, not the sender. Answering would hand your reply straight to the attacker.

  3. 3

    It fails authentication

    SPF fails, there is no DKIM signature and DMARC fails for the From domain. A real Microsoft message passes all three.

  4. 4

    The link leads to a fake login page

    The link uses the same look-alike domain as the sender. Link and sender reputation are checked before delivery, not after a click.

  5. 5

    An HTML attachment

    An .html "invoice" is a common way to open a fake sign-in form offline. Attachment-type filters can hold these on arrival.

  6. Held in quarantine

    The message never reaches the inbox. It waits in quarantine, where the right person can review it — and release it if it was legitimate after all.

We checked the world's 1,000 busiest websites.

Even the biggest names leave gaps that let attackers send mail in their name. We ran our Email Health Check engine against the Tranco top 1,000 domains on October 9, 2026.

38.3%

don't enforce DMARC — so receivers aren't told to reject mail that spoofs them.

DMARC policy of the top 1,000

Only quarantine and reject actually stop spoofed mail.

No valid record
26.6%
Monitoring only (p=none)
11.7%
Quarantine
17.2%
Reject
44.5%

Enforcement by popularity

Share with DMARC at quarantine or reject.

How many DNS lookups their SPF needs

Limit: 10 — above it, SPF breaks
0 50 100 150 0 2 4 6 8 10 11+

22 sites exceed the limit, so receivers treat their SPF as failed.

Newer protections are still rare

Share of sites that publish each record.

Source: iBlockSpam analysis of the Tranco list PY35J (2026-10-08), 1,000 domains, public DNS. Full methodology and data

What 30 days of filtering looks like.

Real, anonymized traffic from business domains on our filtering service. Every column is one day — and roughly one message in six never needed to reach an inbox.

Messages filtered
74,147
Held as spam or threats
18%

Anonymized daily totals across 6 business domains filtered by the iBlockSpam service, 2026-09-19 to 2026-10-18. "Held" includes spam, phishing and malware. Full methodology and data

0 1k 2k 3k 4k 5k 19 Sep 24 Sep 29 Sep 4 Oct 9 Oct 14 Oct 18 Oct
Held Delivered

Switching without losing a message.

Every step is checked before the next one starts, and every screen shows how to undo it.

How the setup works
  1. 1

    Check

    Run a free check on your domain. We read your MX, SPF and DMARC records, show where your mail goes today, and flag problems worth fixing before you change anything.

  2. 2

    Configure

    The setup wizard walks you through your platform's steps, such as a Microsoft 365 inbound connector or a Google Workspace inbound gateway, then the MX change. You see your DNS before and after, plus the rollback steps.

  3. 3

    Verify

    Send a test message and confirm it passed through filtering and arrived in the right mailbox. We don't call a domain protected until mail is actually flowing through it.

  4. 4

    Monitor

    We keep watching your MX, SPF and DMARC records and alert you if they change unexpectedly: weekly on Protect, daily on Protect Plus.

Free tools that show their work.

Each result shows the record we read and when. Checks that couldn't run say so — they never count as failures.

All free tools

SPF Checker

Count real DNS lookups, find PermErrors, loops and risky "all" settings.

DMARC Checker

Check your policy, reporting and the safe path from p=none to reject.

MX Lookup

See where your mail is delivered, spot unfiltered backup MX and broken hosts.

DKIM Checker

Validate DKIM keys by selector, including key type and strength.

One price per domain.

Ten people or two hundred, the price stays the same. Every user gets a personal quarantine, and outbound relay is included.

$12 per domain / month

Protect plan, billed annually. $15 month to month. Beta pricing in USD. 30-day money-back guarantee on your first annual plan.

  • Unlimited mailboxes
  • Personal quarantine for everyone
  • 100,000 inbound messages a month
  • 500 outbound relay messages
  • Mail held up to 5 days if your server is down
  • 30-day message history

The honest answers to the usual worries.

What people ask before they put a filter in front of their business mail.

Will real email get blocked?

Suspicious messages are held in quarantine, not deleted. Each person has a personal quarantine and gets a digest email on the schedule they choose (hourly, daily, on a set weekday or custom), and they can release a message that was held by mistake. Admins also get a domain-wide shared quarantine, approved-sender lists keep known contacts flowing, and 30 days of message history let you trace what happened to any message. How quarantine works.

Isn't Microsoft 365 or Google Workspace filtering enough?

For some organizations it is, and iBlockSpam works alongside it rather than replacing it. A gateway adds an independent layer in front of the mailbox: personal quarantines with digests, sender verification on approved lists, geographic, attachment-type and Office macro filters, and up to 5 days of outage spooling. Our comparisons set out what each option does: Microsoft 365 built-in vs a gateway and Google Workspace built-in vs a gateway.

Where is our email processed?

Mail is processed in the United States, and message history is kept for 30 days. Our security page explains what passes through filtering, what we store and who can see a quarantine. The subprocessor list shows who helps us run the service.

What if your service goes down?

Email is built to ride out short outages: a sending server that can't connect keeps retrying, usually for several days, before it gives up, so an interruption delays mail rather than losing it. On your side, if your own mail server is unreachable, we hold incoming mail for up to 5 days and deliver it when the server is back. See outage spooling.

Who do I talk to when something's wrong?

A person. Email support@iblockspam.com or use the support page, and someone reads every message. If mail has stopped arriving, say so in the subject line so it's seen straight away. Protect Plus also includes a human setup session for your cutover.

Still deciding?

A domain's first annual subscription has a 30-day money-back guarantee, and you can start with a free check of your current setup.

Learn how email security really works.

Plain-English guides with primary sources: RFCs, Microsoft Learn and Google's own documentation.

All guides

Questions before you switch.

More on the FAQ page, or ask a person.

Will iBlockSpam work with our email provider?

Yes, if your mail server can receive mail from a filtering gateway. We have guided setups for Microsoft 365, Google Workspace and cPanel/WHM, and we also deliver to Exchange and other standard SMTP servers. Each platform needs its own steps, such as an inbound connector in Microsoft 365 or an inbound gateway in Google Workspace. Run the free health check first to see where your mail goes today.

What happens if mail stops arriving?

First, nothing is lost just because your own server is down: we hold mail for up to 5 days and deliver it when the server is back. If mail stops for another reason, contact support with your domain and the time it started. Your setup record keeps your previous MX values, so rolling back is a DNS change you can make straight away.

Can we leave safely if it isn't right for us?

Yes. Leaving is a DNS change. Before your service ends, we help you point your MX records back to your previous provider (or a new one) so mail keeps arriving, and you undo the platform settings we helped you add. Your setup record lists your original DNS values to make the switch straightforward.

Does changing our MX records affect mail we already have?

No. MX records only control where new incoming mail is delivered. Mail already in your mailboxes, your folders, calendars and contacts stay exactly where they are. During DNS propagation some senders will use the old route and some the new one for a while, which is why we ask you to keep both working until the change has settled.

What's the difference between the mailbox and message limits?

Pricing is per domain, so you can protect as many mailboxes and domain aliases as you need. That covers how many mailboxes, not how much mail. Each domain includes 100,000 inbound messages per month, and individual messages can be up to 400 MB. If you expect more than that, talk to us before you sign up so we can plan for it.

Do you filter outgoing email too?

You can send through our outbound relay (smart host). It signs messages with DKIM and filters outbound mail, which helps catch a compromised account sending spam in your name. Both plans include 500 outbound relay messages per domain per month. Using the relay is optional; inbound filtering works without it.

How is pricing calculated?

You pay per protected domain, not per user. Protect is $12 per domain per month billed annually ($144 a year) or $15 month to month. Protect Plus is $19 billed annually ($228 a year) or $24 month to month. These are beta prices in USD, excluding tax. For MSPs and hosting providers, partner terms, including pricing, are agreed individually.

See what your domain lets through.

Ready to protect it? Protect your domain