schedule 13-min read

How to Add a DMARC Record at 123-reg

DMARC AI editorial team · Last updated

Add a DMARC record at 123-reg as a TXT record named _dmarc, check the domain uses 123-reg nameservers, then verify it and move from p=none to p=reject.

01

How do you add a DMARC record at 123-reg?

To add a DMARC record at 123-reg, log in to the Control Panel, select Manage All next to Domains, pick the domain, open DNS and choose Add New Record. Set Type to TXT, Name to _dmarc and Value to a record such as v=DMARC1; p=none; rua=mailto:reports@example.net, then select Save.

This only works when the domain uses 123-reg's nameservers. 123-reg's own help pages say that otherwise, changes made in the Control Panel will not take effect. This guide covers the nameserver check, the exact fields, the hostname pitfalls, SPF and DKIM notes for 123 Reg Mail and Microsoft 365, the UK public sector context and verification. DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). For the protocol itself, start with the DMARC guide.

Interface note: the steps follow 123-reg's current help articles, which use a DNS tab with Add New Record and fields called Type, Name, Value and TTL. Older guides, including Microsoft's 123-reg page, describe a Manage DNS screen with an Advanced DNS tab and columns called Hostname, Type and Destination TXT/SPF. The values you enter are the same in both layouts.

02

Key takeaways

  • The DMARC record is a TXT record named _dmarc. 123-reg's guides use relative names (@ for the domain itself), so enter _dmarc, not the full domain.
  • 123-reg DNS changes only go live when the domain points at 123-reg's nameservers. Run dig NS first.
  • Keep one DMARC record per name. Under RFC 9989, receivers discard all of them when more than one is returned.
  • Leave out pct, ri and rf. RFC 9989 removed them; move from p=none to p=quarantine to p=reject instead.
  • UK public sector domains follow GOV.UK's email guidance, and the NCSC's end state for everyone is a reject policy.
03

Is the domain's DNS actually hosted at 123-reg?

Check this before you add anything. 123-reg's Manage DNS records page says the add, edit and delete options are for domains using 123 Reg nameservers. If a domain registered at 123-reg points to other nameservers, its DNS is managed by that other provider, and a record added in the 123-reg Control Panel is never served.

$ dig +short NS example.co.uk

If the answer names 123-reg's nameservers, carry on here. If it names Cloudflare, a web host or a client's own DNS provider, add the record there. On Windows, run Resolve-DnsName -Name example.co.uk -Type NS, or use our DNS lookup tool without a terminal.

Nameservers point to Where to add _dmarc
123-reg 123-reg Control Panel, DNS tab
Cloudflare Cloudflare dashboard: see how to add a DMARC record in Cloudflare DNS
A cPanel hosting server cPanel Zone Editor: see how to add a DMARC record in cPanel
Azure DNS Azure portal: see adding a DMARC record in Azure DNS

This split is common with .co.uk domains bought at 123-reg years ago: the registration stays at 123-reg while DNS moved to a host or Cloudflare. The registrar and the DNS host are often different companies.

04

What are the exact steps in the 123-reg Control Panel?

Open the domain's DNS tab, select Add New Record, choose TXT, enter _dmarc as the Name, paste the DMARC string as the Value, leave TTL on Default and select Save. These steps follow 123-reg's TXT record guide, with the DMARC values filled in.

  1. Log in to the 123-reg Control Panel.
  2. Under All Products and Services, select Manage All next to Domains.
  3. Select the domain, for example example.co.uk.
  4. Select DNS in the navigation bar.
  5. Check the existing records for a TXT record named _dmarc. If one exists, edit it instead of adding a second.
  6. Select Add New Record.
  7. Type: TXT.
  8. Name: _dmarc.
  9. Value: the full DMARC string on one line.
  10. TTL: 123-reg's guide recommends leaving it on Default.
  11. Select Save.

A first record in monitoring mode:

v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net

If you are unsure of the syntax, build the value with the DMARC record generator, or follow how to create a DMARC record step by step, which explains each tag.

Do you enter _dmarc or _dmarc.example.co.uk in the Name field?

Enter _dmarc. 123-reg's guides treat the Name field as relative to the domain: for a record on the domain itself, its Google verification guide says to enter the @ symbol rather than your domain name, and its DKIM guide uses a bare hostname as the example.

123-reg does not document what happens if you type the full name instead, so do not rely on it. After saving, query the record with dig as shown below. If the answer only appears at a doubled name such as _dmarc.example.co.uk.example.co.uk, delete that record and add it again with _dmarc.

For a subdomain such as shop.example.co.uk, the relative name is _dmarc.shop. More patterns are in DMARC record examples for common setups.

What about quotation marks and spaces?

Leave them out. 123-reg's SPF guide warns against special characters such as quotation marks and spaces after the record string, because they can cause DNS problems. The same applies to a DMARC value. Paste it from a plain text editor, never from a word processor that inserts curly quotes.

How long does a 123-reg DNS change take?

123-reg's help pages give different windows. The TXT record guide says changes take 24 to 48 hours to become active, while the Google verification guide says 4 to 8 hours, or 24 to 48 hours if nameservers also changed. Check with dig against the domain's own nameservers rather than waiting a fixed time.

05

What SPF and DKIM does 123-reg document?

123-reg documents an SPF record for its own mail service and a general way to add DKIM records you are given. DMARC passes when SPF or DKIM passes and aligns with the From domain, so set these up before you think about enforcement. For SPF syntax in general, see how to create an SPF record.

Mail service SPF at Name @ DKIM Source
123 Reg Mail v=spf1 include:secureserver.net -all Not covered in that guide 123-reg SPF guide
Microsoft 365 v=spf1 include:spf.protection.outlook.com -all Not covered on the 123-reg page Microsoft Learn
Other providers Use the provider's include TXT record with the hostname and value the provider gives 123-reg DKIM guide

The 123-reg SPF guide warns against adding more than one SPF record to a domain and advises combining them into one. Microsoft's 123-reg DNS guide gives the same warning: if an SPF record already exists, add Microsoft's include to it rather than creating a second. If both services send, merge them as shown in multiple SPF records: how to merge them.

For DKIM, 123-reg's DKIM guide adds a TXT record with the hostname and value your email provider supplies. Microsoft 365 DKIM is enabled in Microsoft's own admin tools and published as the records Microsoft shows you; the DMARC and Microsoft 365 setup guide covers that end.

06

How do you verify the DMARC record after publishing?

Query _dmarc for the domain and confirm exactly one record starting with v=DMARC1 comes back with the value you saved. Ask one of 123-reg's nameservers directly as well, so a cached answer from a public resolver does not mislead you.

$ dig +short TXT _dmarc.example.co.uk
"v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net"

To bypass caches, take a nameserver from the dig NS output and ask it directly:

$ dig @<nameserver-from-dig-NS> +short TXT _dmarc.example.co.uk

On Windows:

Resolve-DnsName -Name _dmarc.example.co.uk -Type TXT
nslookup -type=TXT _dmarc.example.co.uk

The DMARC checker validates the syntax and flags duplicates. How to check your DMARC policy explains how to read the result. If the checker finds nothing, work through how to fix "no DMARC record found".

07

Should the 123-reg DMARC record include pct?

No. RFC 9989 replaced RFC 7489 in 2026 and removed pct, ri and rf. Older tutorials still show a percentage ramp, but receivers following the current standard ignore it. Publish each policy in full, and use t=y if you want a cautious step, which asks receivers to apply the next lower policy.

v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc-reports@example.net

Remove t=y once the level is confirmed. RFC 9989 also adds np for non-existent subdomains, explained in non-existent subdomains and the DMARC np tag.

08

What does UK guidance say about DMARC on 123-reg domains?

UK guidance applies whatever the registrar. The NCSC's recommended implementation plan ends with a DMARC policy of reject on all of your domains, reached in phases: monitor, send spoofs to spam, then reject. Public sector bodies also follow GOV.UK's email security guidance.

A public sector record in the GOV.UK pattern, entered in 123-reg as a TXT record named _dmarc:

v=DMARC1; p=none; rua=mailto:dmarc-rua@dmarc.service.gov.uk,mailto:dmarc@example.gov.uk

09

When do you move from p=none to quarantine and reject?

Move up when aggregate reports show every legitimate source passing SPF or DKIM with alignment: the mailbox provider, the website and each third-party sender. Then edit the existing _dmarc record in the 123-reg DNS tab, change p=none to p=quarantine, watch the reports again, and finally publish p=reject.

v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.net
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.net

Always edit the one record. Adding the new policy as a second record leaves two DMARC records, which receivers discard.

10

What should you check when the 123-reg DMARC record does not work?

Start with the nameservers, then the record count, then the name. Most problems come from editing DNS at 123-reg while the domain is delegated elsewhere, leaving an old record in place, or typing the full domain into the Name field.

Symptom Likely cause Fix
Record shows in the 123-reg DNS tab, but dig returns nothing Domain uses another provider's nameservers Check dig NS and add the record at the live DNS host
Record found only at a doubled name Full domain typed into Name Delete it and re-add with _dmarc
Checker reports no valid policy Two TXT records at _dmarc Merge into one record
Value starts with a quote or has odd characters Quotes or curly quotes pasted in Re-enter the value without quotes
Record ignored First tag is not v=DMARC1, or the record sits at @ Put v=DMARC1 first and use the Name _dmarc
No aggregate reports arrive No rua tag, or an external address without authorisation Add rua; publish the receiver's _report._dmarc record
Mail fails DMARC after enforcement A sender not covered by SPF or DKIM Check reports and fix that sender before tightening further

When reports go to a mailbox on another domain, that domain must publish an authorisation record as defined in RFC 9990. Authorising external DMARC report destinations shows the format.

11

How should MSPs handle DMARC across many 123-reg client domains?

Map every client domain by registrar and by DNS host, because they often differ. For domains whose DNS lives at 123-reg, keep a list of who holds each Control Panel login, publish DMARC at p=none with a shared report address, and move each domain to enforcement only when its own reports are clean.

  • Run dig NS across the portfolio. UK client estates often include a .co.uk at 123-reg, a .com elsewhere and DNS at a web host. Our DNS lookup fundamentals for MSPs covers batch checks.
  • Record access. Note which client owns each 123-reg account and how your team gets access, so a policy change does not wait on a forgotten password.
  • Parked names. Spare domains that send no mail can go straight to v=spf1 -all and p=reject, in line with GOV.UK and NCSC guidance.
  • Change control. Track each domain's policy level and the date of each change, as in a DMARC change-management policy.

DMARC AI collects aggregate reports for every client domain in one multi-tenant view, so you can see whether each client's mailbox provider, website and third-party senders align before you move them to enforcement. More on running DMARC as a managed service is on DMARC for MSPs.

12

Frequently asked questions

Does 123-reg add a DMARC record automatically?

123-reg's help pages do not say that it does. Its guides describe adding TXT, SPF and DKIM records yourself through the DNS tab. Check the domain with dig +short TXT _dmarc.example.co.uk or a DMARC checker rather than assuming a record exists, and add one with a rua address if the answer is empty.

Why does my 123-reg DMARC record not show up in lookups?

Usually because the domain uses another provider's nameservers, so the 123-reg DNS settings are not the live zone. Run dig NS example.co.uk. If the answer is Cloudflare, a web host or another DNS provider, add the _dmarc record there. Otherwise check for a doubled name or wait for the change to propagate.

Can I add the DMARC record as an SPF record type at 123-reg?

No. DMARC is a plain TXT record at _dmarc. 123-reg's current guides add SPF as a TXT record too, and older layouts showed a combined TXT/SPF type. Choose TXT, enter _dmarc as the Name and keep the DMARC value separate from the SPF value at @.

What DMARC policy should a UK organisation start with?

Start with p=none and an aggregate report address, as both NCSC and GOV.UK guidance describe. Use the reports to find and fix every legitimate sender, then move to p=quarantine and finally p=reject, which is the NCSC's end state. Domains that send no email can go straight to p=reject.

13

Next steps

Adding a DMARC record at 123-reg takes a couple of minutes in the DNS tab. The checks around it matter more: confirm the domain uses 123-reg's nameservers, enter _dmarc as a relative name, keep one record, and verify with dig. Then let aggregate reports decide when each domain moves from p=none to p=reject.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.