Defaults.Exposed

Defaults.Exposed › Setup walkthroughs › SPF › REG.RU

How to set up SPF on Reg.ru

Read the domain’s nameservers before you open a panel, because Reg.ru has two of them and only one holds the live zone for any given domain. Save the record in the wrong one and the console will show you a normal-looking row that no receiver will ever read.

Which nameservers, which panel, for SPF

Reg.ru’s help splits the domain into two cases by nameserver. If the domain uses ns1.reg.ru and ns2.reg.ru, the registrar’s own DNS (Domain Name System) holds the live zone, and the personal account (личный кабинет) zone editor described below is the right place. If the domain uses ns1.hosting.reg.ru and ns2.hosting.reg.ru, the live zone sits in the hosting control panel instead, and a record saved in the personal account changes nothing there. If the nameservers point at a different company entirely, such as Cloudflare, another host or the mail provider, the record has to be added at that provider instead.

Reg.ru’s nameservers answer for 1,910,203 domains in the October 2026 census, 0.59% of the domains that have nameservers. The nameserver names tell you which of the two panels holds your zone.

Where the value comes from

Reg.ru is the registrar and, on its own nameservers, the DNS host for the domain. It stores whatever TXT value you type into the text field and publishes nothing for this record on its own. You supply the SPF (Sender Policy Framework) string, including the include value your mail provider generates.

Add the record in the personal account

  1. Sign in to the Reg.ru personal account, called the личный кабинет.
  2. Open the Домены (Domains) section and click the row that lists the domain.
  3. In the DNS-серверы и управление зоной (DNS servers and zone management) block, click Изменить (Edit).
  4. Check the existing rows for a TXT record already starting v=spf1, and edit that one if it is there.
  5. Click Добавить запись (Add record) and select TXT from the record type list.
  6. In the subdomain field, enter @ to place the record on the domain apex.
  7. In the text field, enter the SPF value starting v=spf1, with no surrounding quote marks.
  8. Click Готово (Done) to save the record.

The subdomain field takes @, which Reg.ru applies to the domain apex rather than a named host, so typing the full domain name here creates the record on the wrong host. The text field takes the full SPF string starting v=spf1, with the include value replaced by whatever the domain’s actual mail provider publishes, and no TTL (Time to Live) field appears in this add-record step.

Traps on this console

How the line ends

-all lets a receiver reject mail from an unlisted server on SPF alone, which can bounce forwarded mail before DKIM (DomainKeys Identified Mail) is checked. ~all marks that mail as a soft fail and leaves the decision to your DMARC (Domain-based Message Authentication, Reporting and Conformance) policy. Both endings are defensible; whichever you choose, list every sender first. Of the 332,492,319 domains the census graded or found dead, 87,173,390 (26.2%) end on softfail and 175,426,748 (52.8%) publish no SPF record at all.

Mixed senders, and the record that has to hold all of them

The common state for a domain here is more than one sender: Reg.ru’s own mail or hosting on one side, and Google Workspace, Microsoft 365 or a mailing tool on the other. All of them have to be named inside the one line, because a second record starting v=spf1 fails the check.

Each sender contributes one term. include: pulls in a service’s own published list of servers and keeps up to date automatically when that service changes its infrastructure. a authorises the address the domain’s A record points at, which is the website. mx brings in whatever is listed as receiving mail for the domain. ip4: names a specific address or range, which is the right choice for a server you run yourself and the wrong choice for a large provider whose addresses change.

Two operational notes follow from that. First, if the website sends anything at all, a contact form or an order confirmation, that mail leaves from the web server rather than from the mailbox platform, so it needs a or an explicit ip4: in the line. Second, when you move mail away from a provider, remove its include at the same time, so the record no longer authorises a service you stopped using.

There is also a ceiling. A receiver allows ten DNS lookups when evaluating the record and fails the whole check on the eleventh, and every include:, a and mx spends from that budget, including the lookups hidden inside an include.

Wait, then check it

Reg.ru’s own DNS changes take from a few minutes up to a couple of hours to spread once the record is saved in the personal account zone editor, where the new TXT row appears in the DNS-серверы и управление зоной block after saving.

Once it is listed there, run the free scan against your domain. Because it resolves the record from the public internet rather than reading your console, it is also the fastest way to confirm you edited the panel that holds the live zone.

How the scan grades this record: the SPF record check, with its pass and fail rules and how many domains pass it.

SPF authorises sending servers and is checked against the envelope sender, so on its own it says nothing about the From address a reader sees. DMARC is what turns a failure into an instruction, and the SPF guide covers the check itself.

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