SPF · DKIM · DMARC · Gmail reporting

Email that arrives —
and proof it did.

Most hosts sell you a mailbox and stop there. We set up the authentication that stops your mail being treated as forgery, then show you what the big providers actually do with it — so “did they get my email?” becomes a question you can answer.

01 / The problem

Mail does not bounce any more. It just vanishes.

Gmail, Outlook and the rest no longer reject suspicious mail with an error you would notice. They accept it and file it in spam, or drop it silently. The sender sees a successful send and hears nothing back.

What goes wrong

ForgerySomeone sends as your domainInvoice fraud aimed at your customersrisk
SpamYour invoices land in junkYou are chasing payment for mail nobody sawcost
SilenceNo bounce, no warningNothing tells you it is happeningblind

What fixes it

SPFWhich servers may send as youPublished in your DNS, kept correctset
DKIMA signature proving mail is yoursKey generated and published for youset
DMARCWhat to do with mail that failsAnd reports on everyone sending as youset
02 / What we do

Set up properly, then kept right.

These three records are easy to publish and easy to get subtly wrong. A misconfigured one is worse than none at all — so we do not just set them and walk away.

  1. Step 01
    We publish the records
    SPF, a DKIM key, and a DMARC policy, in your DNS, correct for the way you actually send — including any newsletter tool or accounts system that sends on your behalf.
  2. Step 02
    We check the signature can be verified
    Signing a domain whose key is not published is worse than not signing it: unsigned mail is treated as neutral, but a signature that cannot be checked counts against you. Our systems confirm what is really in DNS before signing anything.
  3. Step 03
    We confirm the domain really points at us
    A domain can publish perfect records on our servers while the registry sends the world somewhere else entirely — and then every change made is quietly ignored. We check the registry itself, so that cannot happen unnoticed.
  4. Step 04
    We watch the sending reputation
    How Microsoft rates the servers your mail leaves from, and how Google rates your domain. A reputation problem gets found and dealt with here, before it turns into mail that does not arrive.
03 / What you see

The figures, in your control panel.

Google publishes delivery data about your domain, but only to whoever has set up and verified a Postmaster Tools account for it. We have done that for every domain we host, and put the results where you can read them.

D / 01Gmail

Delivery reporting

How much of your mail Gmail files as spam, how much passes authentication, how much is rejected, and your domain and IP reputation — day by day across the last month.

D / 02DMARC

Who sends as you

The reports mailbox providers send back, read for you: every source using your domain, how much of it authenticates, and whether your policy is protecting you yet.

D / 03DNS

Records you control

Every record editable yourself, with a full history of what changed and when — and if you use Cloudflare, the two stay in step automatically.

04 / Also worth knowing

If you send from elsewhere.

Deliverability is not only about mailboxes. If your mail leaves from your own server or an application, the same authentication still has to be right.

E / 01Relay

SMTP gateway

Keep your own mail server and route outbound mail through ours, with the filtering, queueing and reputation handled at our end.

E / 02Mailboxes

Email hosting

IMAP, POP and SMTP mailboxes on our UK platform, with the authentication above set up as a matter of course.

E / 03Help

Something not arriving?

If mail to one particular recipient keeps disappearing, that is usually diagnosable. Tell us who and when.

Not sure whether your mail is arriving? We can check.

We can look at what your domain publishes today and tell you what it means — whether or not you host with us.