Surftec customers will be recognised automatically when they use these tools from their office network.
Customer sign-in is coming soon.
DMARC checker and builder
Check what happens to forged mail for a domain and where the reports go, then build and test the next record on the way from monitoring to reject.
The limits DMARC sets
Limit
Used now
Allowed
Status
Where it is set
DMARC records at the name Two or more and receivers act as if there were none.
–
1
Note
RFC 9989 (policy discovery)
DNS queries to find the policy Receivers ask at the domain, then each parent in turn, and stop after 8 queries.
–
8
Note
RFC 9989 (DNS tree walk)
Parts in the domain name Over 8 parts, the walk jumps from the full name to its last 7 parts, so records in between are never seen.
–
No fixed limit
Note
RFC 9989 (DNS tree walk)
Aggregate report addresses (rua) Report senders need only use the first 2. Send to one mailbox or service and forward from there.
–
2
Note
RFC 7489 §6.2; RFC 9990
Failure report addresses (ruf) Few mailbox providers send failure reports at all.
–
2
Note
RFC 7489 §6.2; RFC 9991
Report addresses at another domain without its permission 0 of the report addresses are at another domain. Each such domain must publish a record agreeing to receive the reports.
–
0
Note
RFC 9990 (external destinations)
Characters in one TXT string Fits in one string.
–
255
Note
RFC 1035
Percentage (pct) Newer receivers ignore pct and apply the policy to all mail.
–
0 to 100
Note
RFC 7489 §6.3; historic in RFC 9989
Used now is counted from live DNS at the time of this check. A record over a limit is treated as broken by receiving mail systems, not as partly working.
Test with a real emailNothing is uploaded
Send an email from the domain to a mailbox you can open elsewhere (Gmail or Outlook.com work well), view the message source or headers there, and paste them here. The headers are read in your browser and are not sent to Surftec.
About this tool
DMARC tells other mail systems what to do with email that claims to be from your domain but passes neither SPF nor DKIM for it: deliver it anyway (none), send it to junk (quarantine) or refuse it (reject). It also asks them to send reports, so you can see every system sending in your name. It is one TXT record at _dmarc under your domain.
The standard was reissued in May 2026 as RFC 9989, with reporting in RFC 9990 and RFC 9991, replacing RFC 7489. Records still start v=DMARC1. The limits are: exactly one record at the name; at most 8 DNS queries to find the policy, walking up from the domain to its parents; and report senders need only use the first 2 report addresses. An address at another domain receives nothing until that domain publishes a record agreeing to it. pct, ri and rf are now historic, and t=y (test mode) replaces pct. The checker tests each of these and shows the figure beside the limit.
The roll-out plan gives the three records, monitor, quarantine and reject, with your report address already in them, and marks where the domain is now. The builder starts from the published record; Test this record validates the draft and checks each report address before you publish.
Common questions
Which DMARC policy should I use?
Start with p=none and a report address to see who sends as you. Move to quarantine, then reject, once the reports show every genuine sender passing SPF or DKIM for your domain. Reject is the goal: it is the only policy that stops forged mail being delivered.
What changed in the 2026 DMARC update?
RFC 9989 replaced RFC 7489. Records are still v=DMARC1. The pct, ri and rf tags are historic and ignored by newer receivers; t=y is the new test mode; np sets a policy for subdomains that do not exist; and the organisational domain is found by walking up the DNS tree (at most 8 queries) in place of the Public Suffix List.
Where should DMARC reports go?
To a mailbox kept for the purpose or to a DMARC reporting service. They arrive daily as compressed XML files, one from each mail provider, and are hard to read by hand.
Why are my DMARC reports not arriving at another domain?
A report address outside your own domain must be authorised: the receiving domain publishes a TXT record v=DMARC1 at yourdomain._report._dmarc.theirdomain. Without it, report senders skip the address. The checker tests this and shows the record that is needed.
Can I have two DMARC records?
No. With more than one record at _dmarc, receivers act as if there were none.
Do I need DMARC for Microsoft 365 or Google Workspace?
Yes. Google, Yahoo and Microsoft require it of anyone sending in bulk, and it is the main protection against someone sending email in your name.