How-to · Intermediate · 15 minutes plus a monitoring month

How to Publish a DMARC Policy

Everything you need to tell receiving servers what to do with mail that fails your authentication — the steps in order, the snag to watch, and the tip our support desk gives everybody.

See the plans Ask us a question

Straight answer first

In a line: tell receiving servers what to do with mail that fails your authentication — a intermediate-level task that takes 15 minutes plus a monitoring month.

The walkthrough below covers every step, the mistake most people make, and the shortcut worth keeping. On Hosting Seller plans several of these steps are already done for you, and we say where.

Written by the Hosting Seller staff · Checked 1 August 2026

Intermediate

Difficulty level

Quick

Time to allow

Stages

24/7

Help at any hour

This guide assumes no expertise at all — just a hosting account, a browser and 15 minutes plus a monitoring month of attention. Every instruction works on our platform exactly as written, and carries over to any standard cPanel host.

One promise before you start: nothing in this guide is irreversible. Where a step could bite, we say so and give you the undo.

The route, start to finish

The job breaks into a few clear stages: get the groundwork done, publish in monitor mode, read the reports carefully first, move up to quarantine, and then reject and keep on reading the feedback loop.

Each stage is a few minutes of steady clicking — the time it takes depends mostly on how familiar the control panel already feels. The detailed steps sit further down this page; skim the whole route once before you begin.

The classic snag

Going straight to p=reject without the monitoring month. The legitimate-but-forgotten sender — the invoicing tool somebody set up two years ago — starts bouncing, and you find out about it through customer complaints.

It is worth learning because it is not some rare edge case — it is the single most common reason this task turns into a support ticket. Knowing it up front turns the whole job from risky into routine.

One habit that makes this easy for good

Inbox providers now expect DMARC from anyone sending in volume, so what used to be good advice has become a condition of entry. Even publishing p=none puts you on the right side of that door while you sort the rest out.

It costs a minute now and pays that back every time the job comes round again — which, like most hosting jobs, it certainly will.

The parts we have already done for you

We have automated the steps that do not deserve your time: certificates issue and reissue themselves, the installer handles application setup, the daily backup covers the what-if, and per-site settings live in a panel instead of a config file. The guide above covers what remains — the part that is actually about your site.

And when a step misbehaves anyway, support answers at any hour with the actual fix, not a knowledge-base link and a shrug. Half our best guides began life as a pattern in the ticket queue.

A good platform makes every guide shorter

Every walkthrough on our how-to shelf is tested on the platform we actually run — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen instead of gesturing vaguely at it.

Backups run every day on every plan, and putting a file or a database back takes one click from the panel.

Step by step, tested exactly as printed
The snag flagged before you reach it
The dull steps are already automated
People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

Written from real tickets

Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.

Automation where it belongs

SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.

5 steps, no filler

Each stage is a few minutes of steady clicking, with the fiddly parts marked as fiddly.

The undo is always named

Where a step could bite, the guide says so and tells you how to put it back again.

No jargon toll

Terms are explained where they appear or linked to the glossary — nothing assumes you already know.

Works exactly as written

Every step tested on the platform we run — no 'your host may differ' hand-waving anywhere.

First Steps

From choosing to live

1
Get the groundwork done
DMARC judges whether SPF and DKIM line up with your domain. Both should already be passing for every legitimate stream of mail before enforcing anything makes the slightest sense.
2
Publish in monitor mode
A TXT record at _dmarc.yourdomain reading v=DMARC1; p=none; rua=mailto:you@yourdomain. Policy none changes nothing about delivery, but it starts the reports arriving in your inbox.
3
Read the reports carefully first
Aggregate reports name every source sending as your domain — the forgotten CRM, the invoicing tool, and the outright spoofers. A report-parsing service turns the raw XML into something readable.
4
Move up to quarantine, and then reject
Once everything legitimate aligns, set p=quarantine so failures go to spam. Later move to p=reject, the point at which mail forged as your domain simply stops being delivered anywhere.
5
Keep on reading the feedback loop
Leave the reporting address live and check it. New services and misconfigurations announce themselves in the reports weeks before they announce themselves as an incident.

In the Box

Packed with every plan

The renewal price printed on the tag matches the order price
Spam and virus filtering fitted to every mailbox
NVMe SSD storage on every shelf, not just the top one
A 99.9% uptime commitment, watched by monitoring day and night
One-click installs for WordPress and 400+ other applications
A domain free for year one when you order annually
cPanel, the panel the rest of the trade already knows
A backup taken daily, with restores you run yourself
Site migration done for you by our staff, at no charge
WebP image optimisation built in and costing nothing

Across the Counter

The questions we get asked most

What is actually inside one of these DMARC reports?

Counts grouped by sending source, with the SPF, DKIM and alignment result for each. No message content ever appears. What you get is a map of who sends as you and how their authentication fares, which is precisely what enforcement requires.

How long is the p=none monitoring phase meant to run?

Somewhere between a few weeks and a month. Long enough to catch the senders that only run weekly or monthly, such as invoicing batches and newsletters. Move up when the reports show clean alignment from everything you recognise.

Who actually runs the company?

Hosting Seller is a trading name of Bohzo Ltd, a company registered in England and Wales — a real business with a public record and terms published under English law. Looking that up is worth doing about any host before you hand over your domain.

Can one plan hold more than a single website?

From the Pro tier upward, yes — several sites, each with its own domain, mailboxes and certificate, all under one account. If those extra sites belong to clients rather than to you, reseller hosting is the better fit: it gives each one proper separation.

Are backups included, and can I put one back myself?

A backup is taken daily on every plan, and the restore is yours to run from the panel in minutes — files, databases or both, at three in the morning without waiting on a ticket. Keeping your own copy offsite as well is never a bad habit, and nothing here stops you.

What happens to my files if I leave?

The site and the files stay yours. Pull a full backup from the panel whenever you like, before or during cancellation. Domains remain registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.

How quickly can I be up and running?

Minutes, not days. The account opens the moment the order clears, the domain — free for year one on annual plans — attaches straight away, and the one-click installer puts WordPress or any of 400+ applications on the page before you leave your chair. Already have a site elsewhere? Hand it over and we move it free, usually inside a day.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

Get online, with no games at checkout.

From a first website to a rack of servers, moving up is a change to your account rather than a migration.

See the plans