Beget DMARC record setup

You want a DMARC record on Beget, and what that comes down to is one TXT record at the host _dmarc under your domain, holding a short policy string that begins v=DMARC1.

Beget is the DNS host for domains registered or hosted there, so this is where the record gets published. It does not read the policy or decide what happens to any message; that is left to the receiving mail provider.

The record comes first on this page, with what each part of it means, and the exact Beget fields it goes into come after, because the record is the same wherever your DNS lives and only the form around it changes.

The record before the console

DMARC is the instruction a receiver reads after it has checked SPF and DKIM on a message claiming to come from your domain. Those two checks each return a pass or a fail. DMARC tells the receiver what you want done with a fail, and where to send a summary of what it saw. The instruction lives in DNS because that’s the one place a receiver anywhere in the world can look up something only the domain’s owner can write.

The host is _dmarc, with the _ character at the front, and the type is TXT. The value to start with is:

v=DMARC1; p=none; rua=mailto:[email protected]

Three tags carry the meaning. v=DMARC1 names the version of the standard and has to come first. p= is the policy: none asks receivers to deliver failing mail as they would have anyway and report on it, quarantine asks them to put failing mail in spam or junk, and reject asks them to refuse it during delivery. rua=mailto: names the mailbox that receives the aggregate reports, which arrive as XML attachments listing which servers sent mail as your domain and whether each one passed.

A message passes DMARC when SPF or DKIM passes and the domain that passed matches the domain in the From header. That matching is called alignment, and it’s why a mail provider’s own SPF record isn’t enough on its own: the check has to succeed for your domain, since that’s the one the reader sees.

Other tags turn up in records elsewhere. sp= sets a separate policy for subdomains and defaults to whatever p= says; the subdomain policy piece covers when it’s worth setting. pct= applies the policy to a share of failing mail. adkim= and aspf= switch alignment from relaxed to strict, and ruf= asks for per-message forensic reports, which most large receivers don’t send. Leave all of these out at the start; the three-tag record above is complete and valid.

Start at p=none. Publish p=reject before you know your SPF and DKIM pass on your own mail and you’ll bounce your own invoices along with the forgeries. The reports are how you find that out, so the rua= address has to be a mailbox somebody opens.

Check that Beget answers DNS for the domain

The record only works if Beget is answering DNS for the domain, which means the domain’s nameservers point at Beget’s nameservers. That is the default for domains registered or hosted at Beget, but it is worth checking rather than assuming. If the nameservers point somewhere else, the record has to go at whichever provider runs the DNS instead, because Beget’s editor will save it and still publish nothing useful.

Beget publishes the TXT record on the _dmarc subzone exactly as entered once it is saved. It does not generate the policy value, check SPF or DKIM results, or act on any message that fails the checks; the reader supplies the value and the receiving mail provider does the rest.

Publish SPF and DKIM before DMARC. The policy tells receivers what to do when those checks fail, so a domain with neither has nothing for DMARC to work from, and a p=reject on such a domain refuses everything that carries its name.

Add the record in the Beget console

Sign in to the Beget control panel and open the DNS section.
Select the domain in the list at the top of the DNS section.
Click «Добавить подзону» (Add subzone) and create a subzone named exactly _dmarc.
Select the new _dmarc subzone in the list once it has been created.
Click «Открыть режим редактирования» (Open editing mode) on that subzone.
In the «Быстрое добавление» (Quick add) block, set the record type to TXT.
Paste the record value into the data field without adding quote marks of your own.
Save the record so it publishes.

The subzone name field takes _dmarc and nothing else. Beget appends the domain automatically, so typing _dmarc.yourdomain.com in full breaks the record, and dropping the leading _ character breaks it too. The record type in the Quick add block is set to TXT, and the data field takes the record value beginning v=DMARC1;, pasted plain with the mailbox address replaced by one that gets read.

Look for an existing TXT record at _dmarc before you add one. A domain gets one DMARC record, and a receiver that finds two treats the domain as having none, so if one is already there you edit it. Paste the value without surrounding quotation marks and without a trailing space or line break, then compare the last few characters against the record above once it’s saved.

Traps in the Beget form

Beget gives no free-form host field for the main zone, so _dmarc has to exist as its own subzone before any TXT record can sit on it. A policy saved into the main zone publishes nothing.
Manual quote marks around the value can corrupt it, since the field expects the plain text beginning v=DMARC1;.
If a TXT record already exists on the _dmarc subzone, edit it rather than adding a second one, the same rule that applies to SPF.
The console will happily save the record even when the domain’s nameservers point elsewhere, so checking the nameservers first avoids a record that never publishes anywhere Beget’s own DNS is read.

A record that’s present and malformed is worse than an absent one in a single respect: it looks done. v=DMARC1 missing from the front, p= misspelt or left out, a rua= without mailto: in front of the address, or curly quotes pasted in from a document all produce a record receivers can’t parse and so ignore. The DMARC typos piece lists the ones that show up most often in the census.

With those checked and the record saved, run the free scan below. It looks up _dmarc on your domain the way a receiving mail server does and tells you whether the record is present, whether it parses, and which policy it carries.

Wait, then read the result

DNS changes at Beget can take a few minutes up to a couple of hours to take effect. The saved record appears under the _dmarc subzone in the DNS section once editing mode is closed.

A scan run in the first minutes after saving can read as absent while nothing is wrong, because a resolver somewhere is still handing out its cached answer from before the record existed. If the scan still reports no DMARC after a couple of hours, go back to the nameserver check at the top of this page first and the host name second.

A record saved into a console that isn’t answering DNS for the domain is the most common reason a scan comes back unchanged, and the fix is to add the same record at the company the nameservers point to.

When the scan shows the record and its policy, you’re in the monitoring stage. Nothing about delivery has changed yet, and the first reports take a day or so to arrive.

Tightening from none to reject

p=none leaves delivery as it was and starts the reports arriving. Those reports are the only evidence you’ll get about what sends as your domain: your mail provider, a newsletter tool, an invoicing system, and whatever else somebody connected two years ago. Each report names the sending server, how many messages it sent, and whether SPF and DKIM passed for them. The DMARC piece explains how to read one and what a failing row means.

Without a record, a receiver that sees a message fail both checks has no instruction from you, so most deliver it anyway and nobody tells you. Of the 316,600,902 domains carrying a grade in the September 2026 census, 238,156,049 (75.2%) have no DMARC record at all. The monitoring stage has its own trap: of the domains whose DMARC record carries p=none, 33,651,068 (80.33%) have no rua= address, so they sit at none collecting nothing that would let them move.

Read the reports until every sender you recognise is passing and the failing rows are ones you don’t. Then change p=none to p=quarantine in the same field you saved it in, wait for a further round of reports to confirm your own mail still lands, and change it to p=reject. That last edit is the one that turns a monitoring record into an instruction receivers act on, and it takes the same minute in the Beget console as the first one did.

Figures as of 5 September 2026, from the September 2026 edition of the defaults.exposed census. Census numbers move every month; the current values are on the census data page.