Methodology & disclosure
Independence
MailboxWatch is an independent publication. We do not sell mailboxes, domains, warmup or sending software, and we are not owned by or affiliated with any provider on this site. Providers cannot pay to change their price, position in the default sort, or what we write about them.
How we make money
Some "Pricing" buttons may be affiliate links: if you buy after clicking, the provider may pay us a commission at no extra cost to you. Those links are marked rel="sponsored". We may also sell clearly labelled sponsorships in the newsletter. Neither affects the data. The default table sort is purely by total monthly cost.
Where prices come from
- Each price is read from the provider's own public pricing page on the date shown.
- If the provider's page does not show a price (e.g. it is behind a calculator or login), we may use a reputable third-party comparison and mark it with †. We never estimate a price; if we can't find it, it is left blank.
- Prices are list prices in the provider's currency, before tax, on monthly billing unless noted.
The "30 mailboxes" comparison
Per-mailbox prices are hard to compare because of minimums, bundles and flat plans. So we also price one common setup: 30 mailboxes on 10 domains (3 per domain). We take the cheapest listed plan that covers 30 mailboxes and add 10 domains at the provider's own yearly domain price ÷ 12. If the provider doesn't sell domains or doesn't publish the price, we use a reference .com price of $10.46/yr (Cloudflare Registrar at-cost) and mark it with *. Daily sending caps differ widely, so cost per mailbox is not the same as cost per email sent.
How changes are detected
A script re-downloads every tracked pricing page, extracts the price-related text and compares it with the last snapshot. Any difference is queued for a human to confirm before it appears in the change log and the weekly email.
Corrections
Spotted a wrong price? Providers and readers can send corrections with a link to the source; we fix confirmed errors and note them in the change log.