Knowledge base
Mail has two separate halves - receiving and sending - and they fail for different reasons. Work out which half is broken first.
Email problems split cleanly in two, and the fix is different for each. Work out which one you have before changing anything.
Almost always DNS. Receiving mail requires an MX record pointing at the right mail servers.
The most common cause is a nameserver change: when a domain moves, its DNS records are recreated at the new provider, and if the MX records were not carried across, mail stops arriving from that moment. It does not bounce loudly, either - it usually just goes somewhere else quietly.
Check the domain's DNS in your dashboard for an MX record. If there is none, that is your answer.
Two likely causes, in order:
SPF and DKIM. These are DNS records that tell the receiving server your mail is genuine. Without them a lot of providers will refuse the message or file it as spam. Neither is optional in practice any more.
Sending from the wrong place. A contact form that sends from you@yourdomain.com while the server is not authorised to send for that domain will fail authentication every time, even though the address is really yours.
Send a message to an address on a different provider - a Gmail address if your problem is with Outlook, or the reverse. If that arrives, the problem is specific to one recipient's provider rather than to your domain, and the fix is usually SPF or DKIM.
The exact bounce message, if you have one. Bounce text is precise and names the real reason; "my email is not working" does not. Also tell us whether the address you are sending to is inside or outside your own domain - internal-only failures point somewhere quite different.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →