Guide

Can someone send email in your name?

SPF, DKIM and DMARC are three records in your domain settings that tell receivers which servers may send email for you. Without them, anyone can send a message that looks like it comes from your CEO.

What to do

  • SPF lists the servers that may send for your domain.
  • DKIM signs each message so it can be verified.
  • DMARC says what receivers do with mail that fails.
  • Start DMARC in monitor mode, read the reports, then tighten it.

Why it matters

Fake invoices and payment requests are among the most common frauds against small companies. The message looks like it comes from your managing director or your bookkeeper and asks for a quick transfer. If your domain has no SPF, DKIM and DMARC, the receiving mail server has no way to tell the fake from the real thing.

The same records protect your customers. Without them, someone can mail your customers in your name, and your domain's reputation suffers when receivers start treating it as spam.

How to check it yourself

The records live in DNS, at whoever hosts your domain. You can read them with any public DNS lookup tool, or in the domains area of the Microsoft 365 admin center, which also flags missing records.

  • SPF is a TXT record on the domain itself that starts with v=spf1. If you send only through Microsoft 365, it usually includes spf.protection.outlook.com.
  • DKIM uses two CNAME records, selector1._domainkey and selector2._domainkey. Signing is switched on in the email authentication settings in the Microsoft Defender portal.
  • DMARC is a TXT record at _dmarc.yourdomain that starts with v=DMARC1. The p= value is the policy: none, quarantine or reject.

How to fix it

Start by listing everything that sends mail as you: Microsoft 365, the newsletter tool, the accounting system that mails invoices, the web shop. Each one must be in SPF or sign with DKIM, or its mail will fail once DMARC is tightened.

Keep a single SPF record and end it with -all or ~all. Switch on DKIM for every domain you send from. Then publish DMARC with p=none and a rua address to receive reports. Read the reports for a few weeks, fix any real sender that fails, move to p=quarantine and finally to p=reject.

Domains you own but never send from need protection too. Give them an SPF record of v=spf1 -all and a DMARC policy of p=reject.

What to tell your insurer

Name the domains and the current DMARC policy. A DMARC record at p=none is a good start, but it only monitors; it does not stop anything. If you are still at p=none, say so and say when you plan to move on.

How Ciras checks it

Ciras reads your domain setup and the Microsoft email settings that apply to your licences, and the report says in plain language whether someone can send mail in your name. If you choose the AI fix service, each proposed change is written out in plain words and waits for a person to approve it. The next scan shows whether the change held.

Questions

Will p=reject stop our own mail?

Only mail from senders that fail both SPF and DKIM alignment. That is why you read the reports at p=none first and fix every real sender before you tighten.

Who can change the DNS records?

Whoever manages your domain, often a web agency or the company you bought the domain from. Find out who it is before you need them in a hurry.

Do these records stop all phishing?

No. They stop people from using your exact domain. A look-alike domain with one letter changed is not covered, so staff still need to read sender addresses with care.

What do the DMARC reports look like?

They arrive as zipped XML files, one per receiver per day, and are hard to read by hand. A free or paid DMARC report service turns them into a list of senders that pass and fail. Use a separate mailbox for them so they do not fill anyone's inbox.

Updated 2026-11-11

Next

See where you stand.

Make an account, sign in read-only, and read your own report half a minute later. 499 kr. for one scan.