How to set up DMARC on Timeweb

Add a DMARC record in Timeweb 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 Timeweb runs your DNS

This record only works if Timeweb is answering DNS for your domain — the panel’s DNS editor only affects domains delegated to Timeweb’s nameservers. If the nameservers point to another company (a different host, Cloudflare, your email provider), add the DMARC record at whichever provider runs your DNS instead.

Using Timeweb Mail? Timeweb’s docs say a DMARC record is applied automatically for delegated domains that use Timeweb Mail — check the DNS editor for an existing _dmarc record first, and edit it rather than adding a second.

Step-by-step on Timeweb

Panel labels below are the Russian originals with English equivalents.

Sign in and go to «Домены и SSL» (Domains and SSL) → «Мои домены» (My domains); in the Timeweb Cloud panel, open «Домены и SSL» and your domain’s DNS tab.
Click the row with your domain and open the «Редактор DNS» (DNS editor) tab.
Click «Добавить запись» (Add record).
Set the type to TXT.
In the «Хост» (Host) field, enter exactly: _dmarc Do not type your domain name after it — it is appended for you.
In the «Значение» (Value) 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.
Leave TTL at the default and 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.

Timeweb quirks people get wrong

Check for an auto-created record first. With Timeweb Mail on a delegated domain, a _dmarc record may already exist. Edit it — two DMARC records is treated as broken.
Name is _dmarc, with the underscore. A common mistake is leaving the underscore off, or typing _dmarc.yourdomain.com in full — enter just _dmarc.
Don’t add your own quotes. Paste the plain value beginning v=DMARC1; — manual " marks can break the record.
Check you’re on Timeweb nameservers. The editor will happily save the record, but it does nothing if your domain’s nameservers point elsewhere.
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.

See the full fix guide →

Done? Check your domain free to confirm it worked — and see your full grade across all 34 checks.