Defaults.Exposed › Setup › DKIM

How to set up DKIM on Reg.ru

Publish the DKIM key from your email provider in your Reg.ru DNS zone so your emails carry a tamper-proof signature.

Why this matters to your business

DKIM (DomainKeys Identified Mail) adds an invisible digital signature to every email you send. The receiving mail provider uses a public key you’ve published in your DNS to confirm two things: the message really came from your domain, and nobody altered it on the way.

In plain terms: DKIM is a seal of authenticity on your email. It makes impersonation harder and improves the chance your genuine mail reaches the inbox rather than spam. It’s free and it’s a one-time setup.

Important: DKIM has two halves

• Your email provider generates the key. Whoever runs your mailboxes — Google Workspace, Microsoft 365, Reg.ru’s own mail, VK WorkSpace, Yandex 360, or another service — creates the DKIM key for your domain, along with a selector name (the label that identifies the key). You cannot make this value up.
• Reg.ru publishes it. You then add that key to your domain’s DNS zone at Reg.ru.

If you use Reg.ru’s own mail service, Reg.ru’s help has a dedicated article on enabling DKIM and DMARC for it — the key is generated on their side. For third-party mail services, follow the steps below.

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, add the DKIM record at that provider instead.

Get the records from your email provider

Before touching DNS, collect the DKIM details from whoever runs your email:

• Google Workspace: in the Admin console go to Apps → Google Workspace → Gmail → Authenticate email, generate the key, and copy the selector (usually google._domainkey) and the long TXT value beginning v=DKIM1; k=rsa; p=.
• Microsoft 365: Microsoft uses two CNAME records named selector1._domainkey and selector2._domainkey, each pointing at a long ...onmicrosoft.com target.
• Another provider: look in its email or DNS setup area for the DKIM record and copy the host and value exactly.

Note whether you were given TXT or CNAME records — you’ll choose the matching type below.

Step-by-step on Reg.ru

1. Sign in to your Reg.ru personal account (личный кабинет).
2. Open the «Домены» (Domains) section and click the row with your domain.
3. In the «DNS-серверы и управление зоной» (DNS servers and zone management) block, click «Изменить» (Edit).
4. Click «Добавить запись» (Add record) and select the type your provider gave you — TXT for most providers, or CNAME for Microsoft 365.
5. In the subdomain field, enter only the selector part — for example google._domainkey or selector1._domainkey. Reg.ru’s help shows DKIM hosts entered this way (e.g. dkim._domainkey), without the domain on the end.
6. In the value field, paste what your provider gave you:
   • For a TXT record, the long key beginning v=DKIM1;.
   • For a CNAME record, the target host (the ...onmicrosoft.com address).
7. Click «Готово» (Done) to save. For Microsoft 365, repeat for the second selector.

Reg.ru quirks people get wrong

• Right record type. Google Workspace gives you a TXT record; Microsoft 365 gives you two CNAME records. Adding the wrong type means DKIM never validates.
• Don’t put the full domain in the subdomain field. If the provider shows google._domainkey.yourdomain.com, enter only google._domainkey — the domain is appended for you.
• 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.
• Paste the whole key — it’s long. DKIM public keys are hundreds of characters. Make sure nothing is cut off and no stray spaces or line breaks crept in.
• Finish at the provider too. Some providers (Google included) require you to come back and click a button to start signing after the record is live.
• Give it time. DNS changes can take minutes up to a couple of hours before DKIM starts validating.

Verify it worked

After publishing the record (and switching DKIM on at your provider, if required), run the free check on this site. It will confirm in plain language whether your DKIM record is published and readable.

See the full fix guide →

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