# We run our own email through iBlockSpam

URL: https://iblockspam.com/we-use-it
Last updated: 2026-10-10

> We run iblockspam.com through iBlockSpam. See what we'll publish about our own setup, quarantine trends, false positives and incidents once we have enough data.

iblockspam.com is protected by iBlockSpam, set up the same way we ask you to set up yours. Here is our real setup and our real numbers, including the parts that are small or unfinished.

## Why we do this

It's easy to sell an email filter you've never had to live with. We'd rather feel the same friction you will: the setup steps, the digest emails, the occasional wanted message in quarantine.

So iblockspam.com, including the support@ and security@ addresses you'd write to, routes inbound mail through iBlockSpam. If something in our setup guides is confusing or wrong, we find out first.

## What our setup looks like

We use the same steps as any customer:

1. **Check.** We ran our domain through the [Email Health Check](https://iblockspam.com/tools/email-health-check) and recorded our MX, SPF and DMARC records before changing anything.
2. **Configure.** We followed our own guided setup, including the platform steps for our mail server.
3. **Verify.** We sent test messages and confirmed they passed through filtering and arrived, using the [Email Header Analyzer](https://iblockspam.com/tools/email-header-analyzer) to read the route.
4. **Monitor.** Domain monitoring watches our MX, SPF and DMARC for drift.

### Our public DNS (checked 10 October 2026)

| Record | What it is | Status |
|---|---|---|
| MX | Four MX records (priorities 10 to 40), all pointing to our filtering service | Live since 9 October 2026 |
| SPF | One record that authorizes our outbound relay and ends in `-all` | Live |
| DKIM | Outgoing mail is DKIM-signed by our outbound relay for iblockspam.com | Live |
| DMARC | `p=none` with aggregate reports to dmarc@iblockspam.com | Collecting reports first; we'll move to `quarantine`, then `reject`, once two to four weeks of reports show every legitimate sender passing |

You can always check our records yourself with the [MX Lookup](https://iblockspam.com/tools/mx-lookup), [SPF Checker](https://iblockspam.com/tools/spf-checker) and [DMARC Checker](https://iblockspam.com/tools/dmarc-checker). That's the point: you shouldn't have to take our word for it.

## Our numbers so far

### Quarantine trends

**10 September to 9 October 2026** (the filtering service's own counts for iblockspam.com): **25** inbound messages, **24** delivered and **1** held. Most of that traffic is our own setup and delivery tests from the days around our launch, so it says very little about spam volumes yet. We'll update this section monthly with the date range shown.

### False positives

In the same period the filtering service recorded **1** message as a false positive. Our sample is too small, and too full of test traffic, to draw conclusions from. From here on, we'll list each wanted message that was held: why we think it was held, what we did (release it, allow the sender or change a rule) and what we'd advise a customer to do.

### Incidents

**None so far.** Since 10 October 2026 a probe message goes through our outbound relay and our inbound filtering every two hours, and the result is public on our status page at iblockspam.com/status. Anything that affects mail flow to our own domain will be summarized here: what happened, how long it lasted, whether mail was delayed or lost, and what we changed.

### Configuration changes

- **9 October 2026:** MX records switched to the filtering service; outbound relay with DKIM signing enabled.
- **10 October 2026:** Domain Watch and Lookalike Domain Watch turned on for our domain. Lookalike Domain Watch found one registered look-alike name with no mail server, which we're keeping an eye on.
- **10 October 2026:** the mail-flow probe behind our status page started.

## What this page won't do

- **It won't claim a catch rate.** One domain's traffic is not a benchmark.
- **It won't compare us with other filters** using our own small sample.
- **It won't hide bad months.** If a month is noisy or something breaks, it stays on the page.

## How to use this page

If you're evaluating iBlockSpam, use this page alongside:

- [How it works](https://iblockspam.com/how-it-works), for the mail route and setup steps
- [Security](https://iblockspam.com/security), for what we store and who can see quarantine
- [Pricing](https://iblockspam.com/pricing), for the exact limits per domain
- The [migration guide](https://iblockspam.com/migrate), for how to switch, and switch back

Then run your own domain through the [Email Health Check](https://iblockspam.com/tools/email-health-check) and see where you stand today.

## Frequently asked questions

### Are these real results?

Yes. Every figure on this page comes from our own domain, with the date range shown. Our sample is still small and includes our own setup test messages, so read it as a record of how we run the service, not as a catch rate. We don't fill gaps with estimates or borrowed numbers.

### Will one small domain tell me how well filtering works for me?

Not on its own. Every domain receives different mail, so our numbers aren't a prediction for yours. What this page shows is how we configure the service, how we review quarantine and what we do when something goes wrong. That's the part you can copy.

### Will you publish false positives and incidents?

Yes. A filter that never admits a mistake isn't credible. We'll list wanted messages that were held on our domain, why we think they were held and what we changed, and summarize any incident that affected our own mail flow.

---

Source: iBlockSpam, https://iblockspam.com/we-use-it (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt