What is DMARC? How it works and how to set it up
Published on July 3, 2026 9 min read
DMARC protects your domain against spoofing and phishing. Learn what DMARC is, how to set up a DMARC record and which policy to choose.
DMARC is a DNS setting that stops criminals from sending email that appears to come from your domain. It builds on SPF and DKIM and tells receiving mail servers what to do with messages that fail the checks: do nothing, move them to spam or reject them. This article explains what DMARC is, how it works together with SPF and DKIM, which DMARC record LJPc sets up for you by default, how to change that record and which policy (none, quarantine or reject) suits your situation.
What is DMARC?
DMARC stands for Domain-based Message Authentication, Reporting and Conformance. It is a TXT record in your DNS that does two things. First, it sets a policy: what should a receiving server do when a message that claims to be from your domain fails the checks? Second, it enables reporting: you receive summaries of who is sending email on behalf of your domain.
Where your MX record decides which server receives your incoming email, and SPF and DKIM state who may send on behalf of your domain, DMARC adds the final piece. Without DMARC, receivers check SPF and DKIM, but they never look at the From address the reader actually sees. That gap is exactly what fraudsters exploit in phishing and spoofing.
How does DMARC work with SPF and DKIM?
DMARC never works on its own. It relies on two existing techniques that you need to have in place first.
- An SPF record lists which servers may send on behalf of your domain. The receiver checks the envelope address (the Return-Path), not the visible From address.
- DKIM adds a digital signature to your outgoing email. The receiver verifies that signature using a public key in your DNS.
Neither of them looks at the From address your reader sees in their mail program. A spammer can pass SPF and DKIM for their own domain while putting your domain in the From field. DMARC closes that gap with alignment.
Alignment: the heart of DMARC
Alignment means that the domain in the visible From address has to match the domain that SPF or DKIM checked. DMARC passes as soon as at least one of the two passes and is aligned with your From domain. If both fail, or belong to a different domain, your DMARC policy takes over.
There are two modes. In relaxed mode (the default), a subdomain counts as a match with the parent domain, for example mail.yourdomain.com and yourdomain.com. In strict mode the domain has to be identical. You control this with the aspf tag (for SPF) and the adkim tag (for DKIM). DKIM is the stronger pillar, because a DKIM signature still checks out when your email is forwarded, whereas SPF breaks at that point.
DMARC at LJPc: set up by default
If you have a hosting package with LJPc and your domain uses our name servers, we set up SPF, DKIM and DMARC in your domain's DNS by default. You do not need to configure anything yourself. This is what is in place:
- SPF:
v=spf1 include:_spf.ljpc.network -all - DKIM: a public key at
default._domainkey - DMARC:
v=DMARC1; p=quarantineat_dmarc
So your domain is protected from the start with the quarantine policy: receivers treat email that fails the check as suspicious. The default record has no reporting address. If you want to receive reports or change the policy, edit this existing record. Do not create a second DMARC record: with two records, receivers do not apply DMARC at all.
Where you find the record depends on your package:
- Hosting package: you manage the DNS in Plesk, under the DNS Settings of your domain.
- DNS management only at LJPc: you manage the records in the customer portal. A DMARC record is not always there yet. If you see no record named
_dmarc, add one. - DNS with another provider: your DMARC record and your other records belong there.
How to view, add and change records in Plesk and in the portal is explained step by step in managing DNS records.
Setting up or changing your DMARC record
A DMARC record is a TXT record in your DNS. Work through it step by step.
- First, make sure SPF and DKIM work for every service that sends for you. For mail through LJPc, they are already in place. If you also send through another service, such as a newsletter tool, your accounting software or your CRM, set up DKIM for your own domain in that service (often called domain authentication). If the service asks for an entry in your SPF record, add it to your existing SPF record.
- Check your DNS records for an existing TXT record named
_dmarc. The full name is then _dmarc.yourdomain.com. - If a record is already there, edit that record. Do not delete it and create it again: that way your domain stays protected during the change. If there is none yet, create a TXT record named
_dmarc. - For the value, include at least the version and a policy, and add a rua address if you want to receive reports. Enter the value without quotation marks around it.
- Save the record. At LJPc, a change usually reaches our name servers within a minute. Servers that still have the old value in their cache only see the new one once the TTL expires, which at LJPc is usually after an hour. Read more in DNS propagation.
These are the values you will need most often:
| Situation | Value |
|---|---|
| Default at LJPc hosting | v=DMARC1; p=quarantine |
| Default, with reports | v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com |
| First DMARC record on a domain without DMARC | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com |
| Domain you never send email from | v=DMARC1; p=reject |
The address behind rua has to exist, otherwise the reports never arrive. Create a mailbox or a forwarding address for it. If you use a DMARC reporting service, that service gives you the address to enter at rua.
The policy options: none, quarantine and reject
The p tag decides what a receiver does with email that fails the DMARC check. There are three values, from loose to strict.
| Policy | What the receiver does | When to use it |
|---|---|---|
p=none | Delivers the email as usual and sends you reports. | As a starting point on a domain without DMARC, to see who sends on your behalf. |
p=quarantine | Treats failing email as suspicious and delivers it to the spam or junk folder. | Once you are sure your own mail is aligned. This is the default at LJPc hosting. |
p=reject | Refuses failing email completely, before it is delivered. | As the end state, for full protection against spoofing. |
Which policy suits you?
- You have hosting with LJPc: your domain is already on quarantine, and you keep it that way. If mail you send through another service lands in spam at the receiver, set up DKIM for your domain in that service. If that cannot be done right away, set the policy to none temporarily until it is sorted.
- You are setting up DMARC for the first time: start with none and a rua address, and read your reports for a few weeks. Move to quarantine once all your legitimate senders pass and are aligned.
- You want to move to reject: do so once your reports have shown for a while that all your own mail passes. Reject gives the best protection against spoofing.
Since the updated DMARC standard of May 2026 (RFC 9989), the old pct tag, which let you apply the policy to a percentage of your mail, no longer exists. So you tighten your policy step by step, from none through quarantine to reject, while keeping an eye on the reports.
Key DMARC tags
A DMARC record is made up of tags separated by semicolons. These are the ones you will meet most often.
| Tag | Meaning |
|---|---|
v | The version. Always v=DMARC1, and it must be the first tag. Required. |
p | The policy for your domain: none, quarantine or reject. |
rua | Address for the daily aggregate reports, for example mailto:dmarc@yourdomain.com. |
ruf | Address for detailed per-message failure reports. Far from universally supported. |
sp | A separate policy for subdomains. Without this tag, p also applies to your subdomains. |
adkim / aspf | The alignment mode for DKIM and SPF: r for relaxed (the default) or s for strict. |
t | Test mode (t=y), new in RFC 9989. Receivers then apply one step below your policy: quarantine instead of reject, or none instead of quarantine. Receivers that do not know the tag yet skip it and apply your policy in full. |
DMARC reports: how you know it works
Reports are the most useful part of DMARC. Receivers such as Google and Microsoft send a daily aggregate report to your rua address. It shows which servers sent email on behalf of your domain and whether SPF and DKIM passed and were aligned. The default LJPc record has no rua address: add one to the existing record if you want to receive reports.
These reports are XML files that are hard for humans to read. Use a DMARC reporting service or tool that turns the data into a clear overview. That is how you spot legitimate senders you still need to authenticate, and how you see straight away if someone is abusing your domain.
Solving common problems
| Problem | Cause and fix |
|---|---|
| No DMARC record is found | The name has to be exactly _dmarc and the value must start with v=DMARC1, without quotation marks in front. Check for typos and check that your domain uses the name servers of the provider where you created the record. |
| DMARC seems to be ignored | There is more than one DMARC record at _dmarc, for example the default record and one of your own. Only one is allowed: put everything in one record and remove the others. |
| Mail through a newsletter service or other tool lands in spam | That service is not aligned with your domain. At LJPc hosting your domain is on quarantine, so you notice this straight away. Set up DKIM for your domain in that service. If that cannot be done right away, set the policy to none temporarily. |
| Forwarded email fails SPF | Forwarding breaks SPF. Rely on DKIM alignment, which survives forwarding. |
| Legitimate mail blocked after reject | You moved to reject too soon. Go back to none or quarantine until every sender passes. |
With a well-configured DMARC record, you protect your domain against abuse and improve your own email deliverability. Keep an eye on your reports and tighten your policy step by step. How DMARC works together with spam filters and the other layers of protection is explained in email security. If your mail does not arrive or lands in spam, see fixing email problems. Still stuck? Create a support ticket and we will look into it with you.
Frequently asked questions
What is the difference between DMARC, SPF and DKIM?
SPF decides which servers may send on behalf of your domain, and DKIM adds a digital signature to your email. DMARC ties those two to the visible From address and adds a policy and reporting. SPF and DKIM are the checks; DMARC decides what happens when they fail.
Do I need SPF and DKIM before I set up DMARC?
Yes. DMARC depends entirely on SPF and DKIM. For a DMARC check to pass, at least one of the two has to pass and be aligned with your From domain. At LJPc hosting, SPF and DKIM are set up by default. If you also send through another service, set up DKIM for your domain in that service.
Do I need to create a DMARC record myself at LJPc?
No. A hosting package at LJPc comes with a DMARC record with p=quarantine by default. If you want reports or a different policy, change that existing record. With a second record, receivers do not apply DMARC at all. If you only have DNS management with us, check in the customer portal whether a record named _dmarc is already there.
Which DMARC policy should I choose?
If you have hosting with LJPc, your domain is already on p=quarantine and you keep it that way, unless mail you send through another service lands in spam. If you are setting up DMARC for the first time, start with p=none and a rua address, and move to p=quarantine once all your legitimate senders pass. Choose p=reject once your reports have shown for a while that everything passes: it gives the best protection against spoofing.
Where do I put the DMARC record?
In your DNS, as a TXT record named _dmarc, so that the full name becomes _dmarc.yourdomain.com. With a hosting package at LJPc you manage it in Plesk under the DNS Settings of your domain, and with DNS management only in the customer portal. Publish no more than one DMARC record per domain.
How long before DMARC works?
At LJPc, a new or changed record usually reaches our name servers within a minute. Servers that still have the old value in their cache only see the change once the TTL expires, which at LJPc is usually after an hour. Reports then arrive daily; collect a few weeks of them before you tighten your policy.
Is DMARC required?
For large senders, yes. Google and Yahoo (since 2024), and Microsoft (since May 2025), require SPF, DKIM and DMARC from anyone sending a lot of email to their users. For smaller domains DMARC is strongly recommended too, because it helps prevent your domain being spoofed.