Defaults.Exposed › Setup › DMARC
How to set up DMARC on Reg.ru
Add a DMARC record in your Reg.ru DNS zone to tell mail providers what to do with email that fails your checks.
Why this matters to your business
DMARC ties SPF and DKIM together and adds the missing instruction: what should a receiving mail provider do when an email claiming to be from you fails the checks? Without DMARC, each provider guesses. With it, you decide — and you can ask them to send you reports showing who is sending mail in your name.
In plain terms: DMARC is what actually stops criminals from spoofing your domain to scam your customers or staff. It’s the policy on top of the locks SPF and DKIM provide — free, and well worth the few minutes.
Set up SPF and DKIM first
DMARC works by checking the results of SPF and DKIM. If you haven’t added those yet, do them first — a DMARC policy with nothing underneath it has nothing to enforce.
Confirm where your DNS actually lives
Reg.ru’s help distinguishes two nameserver setups:
ns1.reg.ru/ns2.reg.ru— edit records in the Reg.ru personal account (личный кабинет), as below.ns1.hosting.reg.ru/ns2.hosting.reg.ru— records are managed in the hosting control panel instead.
If the nameservers point at a different company entirely (Cloudflare, another host, your email provider), add the DMARC record there instead.
Step-by-step on Reg.ru
- Sign in to your Reg.ru personal account (личный кабинет).
- Open the «Домены» (Domains) section and click the row with your domain.
- In the «DNS-серверы и управление зоной» (DNS servers and zone management) block, click «Изменить» (Edit).
- Click «Добавить запись» (Add record) and select TXT.
- In the subdomain field, enter exactly:
_dmarcDo not type your domain name after it — it is appended for you. - In the text field, start gently with a monitoring-only policy:
v=DMARC1; p=none; rua=mailto:[email protected]Replace the address with a mailbox you actually read. This asks providers to email you summary reports without changing how any mail is treated yet. - Click «Готово» (Done) to save.
Choosing your policy (the p= part)
p=none— monitor only. Nothing is blocked; you just receive reports. Start here.p=quarantine— send failing mail to spam/junk.p=reject— refuse failing mail outright (the strongest protection).
Run p=none for a few weeks, read the reports to confirm all your legitimate mail passes, then move up to quarantine and finally reject. Jumping straight to reject before you’ve checked the reports risks blocking your own genuine email.
Reg.ru quirks people get wrong
- Subdomain is
_dmarc, with the underscore. A common mistake is leaving the underscore off, or typing_dmarc.yourdomain.comin full — enter just_dmarc. - One DMARC record only. Like SPF, there must be a single DMARC TXT record. If one exists, edit it rather than adding a second.
- Wrong panel for hosting nameservers. On
ns1.hosting.reg.ru/ns2.hosting.reg.ru, the personal-account zone editor isn’t where your live records live — use the hosting panel. - Don’t add your own quotes. Paste the plain value beginning
v=DMARC1;— manual"marks can break the record. - Use a real reporting mailbox. The address after
rua=mailto:should be one you genuinely check, or the reports are wasted. - Give it time. DNS changes can take a few minutes up to a couple of hours to take effect.
Verify it worked
Once saved and propagated, run the free check on this site. It will tell you in plain language whether your DMARC record is in place and what policy you’ve set.
Done? Check your domain free to confirm it worked — and see your full grade across all 34 checks.