Category: DMARC

  • How to Set Up SPF, DKIM and DMARC for Any Email Platform

    How to Set Up SPF, DKIM and DMARC for Any Email Platform

    Every email platform has its own screens and its own names for things, but the job underneath is always the same. You’re proving to Gmail, Outlook and Yahoo that the email really comes from you, using three DNS records: SPF, DKIM and DMARC.

    This guide walks through that job step by step. It works whether you send from Mailchimp, Brevo, HubSpot, Klaviyo, Google Workspace, Microsoft 365 or something else entirely. Where a platform does things differently, I’ll point it out.

    Before you start: list everything that sends as you

    This is the step most people skip, and it’s why so many setups fail later. Make a list of every service that sends email from your domain, not just your marketing platform. Typically that’s:

    • Your mailbox provider (Google Workspace or Microsoft 365)
    • Your marketing platform
    • Your CRM or sales tools
    • Your help desk or support system
    • Invoicing, booking or ecommerce systems
    • Your website’s contact forms

    Every one of these needs to pass authentication. Miss one, and when you turn DMARC up later, its emails will start going to spam or bouncing.

    You’ll also need access to your DNS. That’s usually wherever you bought your domain, or Cloudflare if you use it.

    Step 1: Authenticate your domain in each platform

    Every decent email platform has a setting for this, though the name varies: domain authentication, sending domain, branded domain or verified domain. Find it, add your domain, and the platform will give you a set of DNS records to publish. Usually these are CNAME or TXT records.

    Do this for every platform on your list. It’s what lets the platform sign your email with your own domain instead of its own.

    Step 2: Publish the DKIM records

    Most of the records your platform gives you are for DKIM. Copy them into your DNS exactly as shown. A few things to watch:

    • Some DNS panels add your domain to the end of the name automatically, so you end up with selector._domainkey.yourdomain.co.uk.yourdomain.co.uk. Check what your panel expects.
    • Long DKIM keys sometimes get split or cut off when pasted. If your platform offers a 2048-bit key, use it, and check the whole value went in.
    • Some platforms, like Microsoft 365, need you to switch DKIM on after the records are published. Publishing them isn’t enough.

    Then go back to the platform and click verify. DNS changes can take a few minutes to a few hours to show up.

    Step 3: Sort out SPF, but only where it’s needed

    This is where most people go wrong. Not every platform needs adding to your SPF record. SPF checks the bounce (Return-Path) domain, and many marketing platforms use their own bounce domain unless you set up a custom one. If yours does, adding it to your SPF record does nothing.

    Add a platform to SPF when it tells you to, or when you’ve set up a custom bounce domain on your own domain. Your mailbox provider (Google Workspace or Microsoft 365) always needs to be in there.

    Two rules matter more than anything else:

    Step 4: Check alignment

    DMARC doesn’t just want SPF or DKIM to pass. It wants them to pass for the same domain your subscribers see in the From address. That’s called alignment.

    In practice, DKIM alignment is the one that matters most. If step 2 is done properly, DKIM will be signed with your domain and will align. SPF only aligns if the platform uses a custom bounce domain on your domain. If you’re seeing SPF pass but DMARC fail, DMARC alignment explained covers why.

    Step 5: Add a DMARC record

    Once your senders are authenticating, publish a DMARC record. Start in monitoring mode:

    v=DMARC1; p=none; rua=mailto:[email protected]

    It goes in a TXT record at _dmarc.yourdomain.co.uk. The p=none part means nothing gets blocked yet. The rua part asks mailbox providers to send you daily reports showing every service sending as your domain and whether it passed. Those reports are how you find the senders you missed. Here’s how to read a DMARC aggregate report.

    Step 6: Test it

    Send a test email from each platform and check it passes. The quickest way is our free email spam test, which checks SPF, DKIM and DMARC along with your spam score. You can also open the email in Gmail, choose “Show original” and look for SPF, DKIM and DMARC all showing PASS.

    Step 7: Move to enforcement

    p=none is a starting point, not a finish line. Once your reports show all your real email passing, move to p=quarantine and then p=reject. That’s what actually stops someone sending email pretending to be you, and it’s needed for BIMI. A few weeks is typical to get there. DMARC p=none: what it means and how to move to enforcement safely walks through it.

    Notes for the most common platforms

    • Google Workspace: DKIM is generated in the Admin console and has to be switched on after you publish it. Full walkthrough: DMARC for Google Workspace.
    • Microsoft 365: your own domain isn’t DKIM-signed until you switch it on. Full walkthrough: How to set up DKIM in Microsoft 365.
    • Mailchimp, Brevo, HubSpot and Klaviyo: each has a domain authentication setting that gives you the records to publish. Step-by-step guides: Mailchimp, Brevo, HubSpot and Klaviyo.
    • Anything else: look for “domain authentication” or “sending domain” in the settings. If you can’t find it, or the platform can’t sign with your domain at all, that’s worth knowing before you move DMARC to enforcement.

    Common mistakes

    • Adding a second SPF record instead of merging into the first
    • Publishing DKIM records but never clicking verify or switching DKIM on
    • Forgetting the services outside marketing, like invoicing or your help desk
    • Adding a DMARC record with no rua address, so you never get the reports
    • Staying on p=none forever, which leaves your domain open to spoofing

    Want it done for you?

    I’ve set up SPF, DKIM and DMARC on most email platforms over 16 years, and it can often be done within an hour. See SPF, DKIM & DMARC setup, or run the free email spam test first to see where you stand.

  • DMARC for Google Workspace: A Small-Business Setup Guide

    DMARC for Google Workspace: A Small-Business Setup Guide

    If your business email runs on Google Workspace, setting up DMARC properly takes three records: SPF, DKIM and DMARC itself, in that order. Get the first two right and DMARC is straightforward to add. This guide is written for small and medium-sized UK and Irish businesses doing it themselves.

    Why bother?

    Gmail, Yahoo and Microsoft all now expect SPF, DKIM and DMARC from anyone sending at volume, and since late 2025 Gmail has been rejecting more mail that doesn’t comply. DMARC also stops criminals sending fake invoices that look like they came from your domain.

    Step 1: SPF

    Your domain should have one TXT record starting v=spf1 that includes Google:

    v=spf1 include:_spf.google.com ~all

    If other services send email as your domain (a newsletter platform, CRM or website form), their entries go into the same record. Never add a second SPF record. Our guide to merging SPF records explains why. And keep an eye on the 10-lookup limit.

    Step 2: DKIM in the Google Admin console

    Google Workspace doesn’t sign mail with your own domain until you set it up:

    1. In the Google Admin console, go to Apps → Google Workspace → Gmail → Authenticate email.
    2. Choose your domain and click Generate new record.
    3. Choose a 2048-bit key (use 1024 only if your DNS host can’t handle long records) and keep the default selector, google.
    4. Copy the host name (google._domainkey) and the TXT value, and add them as a TXT record at your DNS host.
    5. Back in the Admin console, click Start authentication.

    It can take up to 48 hours to start working, and the console may show a warning about DNS during that time. If you’ve added the record correctly, you can ignore it.

    Step 3: check both are working

    Send an email from your Workspace account to a Gmail address other than your own (you can’t test by emailing yourself). Open it, choose Show original, and check SPF and DKIM both say PASS, with DKIM showing your domain.

    Step 4: add your DMARC record

    Add a TXT record at _dmarc.yourdomain.co.uk:

    v=DMARC1; p=none; rua=mailto:[email protected]
    • p=none starts in monitoring mode, so nothing is blocked while you check everything is set up.
    • rua= is where daily reports are sent. Use a dedicated mailbox or a DMARC reporting service, because the volume adds up.

    Step 5: read the reports for a few weeks

    Your DMARC reports will show every service sending as your domain. Google Workspace should pass straight away. Anything else that fails needs SPF and DKIM set up in that service, signed with your domain so it aligns.

    Step 6: move to enforcement

    Once your reports show all your legitimate email passing, move to p=quarantine and then p=reject. That’s when DMARC actually protects your domain from spoofing, and it’s also a requirement for showing your logo with BIMI. Our guide to moving from p=none covers it step by step.

    Check your Google Workspace setup

    Send a test email from Google Workspace to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, in seconds. When you’re ready to move to enforcement, our DMARC service handles the reports and gets you to p=reject safely.

    5.0 from 12 Google reviews

  • BIMI in the UK: VMC vs CMC, Trademarks and What You Need

    BIMI in the UK: VMC vs CMC, Trademarks and What You Need

    BIMI puts your logo next to your emails in the inbox, so they’re instantly recognisable and harder to fake. But the rules on what you need are confusing: certificates, trademarks, logo formats and DMARC policies. Here’s what a UK or Irish business needs in practice, and how to choose between the two certificate types, VMC and CMC.

    What is BIMI and how does it work?

    BIMI stands for Brand Indicators for Message Identification. It’s a DNS record that tells mailbox providers where to find your logo, so they can show it next to your emails in the inbox.

    When your email arrives, the receiving server checks that it passes DMARC. If it does, it looks up your BIMI record, fetches your logo and, at most providers, checks the certificate that proves the logo is yours. Only then does the logo appear.

    That’s why BIMI is more than branding. It only works for domains that have locked down their authentication, so the logo is a visible sign to your subscribers that the email really came from you. It also helps your emails stand out in a busy inbox.

    Gmail, Yahoo and Apple Mail all support BIMI, and more providers are adding it. Here’s what you need to get it working.

    Step 1: DMARC at enforcement

    This is the requirement that stops most businesses. Your DMARC policy must be p=quarantine or p=reject, applied to all of your mail. A p=none policy doesn’t qualify, and neither does a pct value below 100. Gmail also expects your subdomain policy (sp=) not to be set to none.

    If you’re still on p=none, start with our guide to moving to enforcement safely. Most of the work in a BIMI project is here, not in the logo.

    Step 2: your logo in SVG Tiny PS format

    BIMI needs your logo as a square SVG file in a specific profile called SVG Tiny Portable/Secure (SVG Tiny PS). A normal SVG exported from a design tool usually won’t pass validation, so expect to convert it. Keep the logo simple and centred, with a solid background, because inboxes show it small and often cropped to a circle.

    Step 3: choose a certificate, VMC or CMC

    Gmail and Apple Mail only show your logo if it’s backed by a mark certificate, which proves you have the right to use it.

    VMC (Verified Mark Certificate)CMC (Common Mark Certificate)
    Needs a registered trademark?YesNo
    Other requirementTrademark registered with an accepted office (UK IPO and EUIPO are accepted)Logo in continuous public use on your domain for at least 12 months
    GmailLogo plus blue verified tickLogo only, no tick
    Apple MailSupportedNot supported

    Which should you choose?

    • Already have a registered trademark for your logo? Choose a VMC. You get the tick in Gmail and support in Apple Mail.
    • No trademark, but you’ve used the logo for at least a year? A CMC gets your logo into Gmail without the time and cost of registering a trademark.
    • Neither? Get your DMARC to enforcement now, and revisit BIMI once your logo qualifies. Yahoo can show BIMI logos without a certificate for some senders, but don’t rely on that alone.

    Certificates are issued by a small number of approved certificate authorities and renewed every year. Expect a cost in the hundreds of pounds a year, and allow a few weeks for verification.

    Step 4: publish your BIMI record

    Once you have your SVG and certificate hosted on your website, add a TXT record at default._bimi.yourdomain.co.uk:

    v=BIMI1; l=https://yourdomain.co.uk/bimi/logo.svg; a=https://yourdomain.co.uk/bimi/certificate.pem

    The l= tag points to your logo and a= to your certificate.

    Step 5: be patient

    Mailbox providers decide when to show your logo, and they also look at your sending reputation. It can take days or weeks to appear, and good authentication and engagement remain a prerequisite.

    A note for Outlook users

    Microsoft’s Outlook doesn’t currently display BIMI logos, so recipients on Outlook and Microsoft 365 won’t see the logo even when everything is set up correctly.

    Is your domain BIMI-ready?

    BIMI starts with authentication. Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass before you spend money on a certificate. We can also take you from p=none to a working BIMI logo.

    5.0 from 12 Google reviews

  • SPF Passes but DMARC Fails? DMARC Alignment Explained

    SPF Passes but DMARC Fails? DMARC Alignment Explained

    Your email headers show spf=pass. Maybe dkim=pass as well. And yet dmarc=fail. It looks contradictory, but it’s one of the most common results we see, and it comes down to one idea: alignment.

    Passing isn’t the same as aligning

    SPF and DKIM each check a domain, but not necessarily the domain your recipient sees.

    • SPF checks the Return-Path (also called the envelope sender or bounce address), a hidden address used for bounces.
    • DKIM checks the domain in the signature’s d= tag, which is whoever signed the email.
    • DMARC cares about the From address, the one people actually see.

    DMARC passes only when SPF or DKIM passes and the domain it passed for matches the From domain. That match is alignment.

    A typical example

    You send a newsletter from [email protected] using an email marketing platform. The headers show:

    Return-Path: [email protected]
    DKIM-Signature: d=platform-example.com; s=k1
    From: [email protected]
    
    spf=pass (mail.platform-example.com)
    dkim=pass (platform-example.com)
    dmarc=fail (yourdomain.co.uk)

    Both checks passed, but for the platform’s domains, not yours. Neither aligns with yourdomain.co.uk, so DMARC fails. In your DMARC reports this shows up as SPF and DKIM passing under auth_results but failing under policy_evaluated.

    Relaxed vs strict alignment

    Your DMARC record controls how closely the domains must match, with aspf for SPF and adkim for DKIM:

    • Relaxed (r, the default): subdomains count. DKIM signed by mail.yourdomain.co.uk aligns with a From address at yourdomain.co.uk.
    • Strict (s): the domains must match exactly.

    Most businesses should stay on relaxed. Strict alignment breaks easily and adds little protection for most senders.

    How to fix it

    Fix DKIM first

    Set up custom DKIM in every platform that sends as your domain: it’s usually called “domain authentication” or “branded sending domain”. Once the signature reads d=yourdomain.co.uk, DKIM aligns. This is the most reliable fix, because DKIM survives forwarding and SPF doesn’t. See why DKIM fails if it doesn’t verify.

    Add a custom Return-Path if you can

    Many platforms let you set a custom bounce domain, such as bounce.yourdomain.co.uk. With relaxed alignment, SPF then aligns too, which gives you a second route to DMARC passing.

    Watch for forwarding

    When email is forwarded, SPF usually fails because the forwarding server isn’t in your SPF record. Aligned DKIM is what keeps forwarded mail passing DMARC.

    A note on the 2026 DMARC update

    The updated DMARC standard published in 2026 (RFC 9989) changes how receivers work out your organisational domain, replacing a published list of domain suffixes with a lookup of DMARC records up your domain tree. For a typical business with a DMARC record at _dmarc.yourdomain.co.uk, alignment works exactly as before. Keep a DMARC record on your main domain and you’re covered.

    Why it matters

    Until every legitimate sender aligns, you can’t safely move your DMARC policy beyond p=none. Once you do, Gmail and Microsoft will start rejecting or junking the senders that don’t.

    Get every sender aligned

    Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass for your domain, or let our DMARC service find every platform sending as your domain and get each one aligned before you move to enforcement.

    5.0 from 12 Google reviews

  • How to Read a DMARC Aggregate Report (Without Losing Your Mind)

    How to Read a DMARC Aggregate Report (Without Losing Your Mind)

    You’ve set up DMARC with a rua= address, and now your inbox is filling with emails from Google, Microsoft, Yahoo and others, each with a zipped file attached. Inside is a wall of XML. This guide explains what those reports are, how to read one, and, most importantly, what to do with what you find.

    What a DMARC aggregate report is

    When you publish a DMARC record with a rua=mailto: address, mailbox providers send you a summary of all the email they received claiming to be from your domain. Each report usually covers one day from one provider and tells you:

    • which servers (IP addresses) sent email as your domain
    • how many messages each one sent
    • whether those messages passed SPF and DKIM, and whether they aligned with your domain
    • what the provider did with them under your policy

    Reports contain no message content and no recipient addresses, just counts and authentication results. They usually arrive as .xml.gz or .zip attachments with names like google.com!yourdomain.co.uk!1759276800!1759363199.xml.gz: the reporter, your domain, then the start and end of the reporting period as Unix timestamps.

    The anatomy of a report

    Here’s a trimmed-down example of what you’ll see once you unzip one:

    <feedback>
      <report_metadata>
        <org_name>google.com</org_name>
        <report_id>1234567890</report_id>
        <date_range><begin>1759276800</begin><end>1759363199</end></date_range>
      </report_metadata>
      <policy_published>
        <domain>yourdomain.co.uk</domain>
        <adkim>r</adkim><aspf>r</aspf>
        <p>none</p>
      </policy_published>
      <record>
        <row>
          <source_ip>203.0.113.25</source_ip>
          <count>412</count>
          <policy_evaluated>
            <disposition>none</disposition>
            <dkim>pass</dkim>
            <spf>fail</spf>
          </policy_evaluated>
        </row>
        <identifiers><header_from>yourdomain.co.uk</header_from></identifiers>
        <auth_results>
          <dkim><domain>yourdomain.co.uk</domain><selector>s1</selector><result>pass</result></dkim>
          <spf><domain>bounces.platform-example.com</domain><result>pass</result></spf>
        </auth_results>
      </record>
    </feedback>

    It looks intimidating, but there are only four parts that matter.

    1. report_metadata: who sent the report

    The provider’s name (org_name), a report ID and the time period covered. Useful for knowing which mailbox provider’s view you’re looking at, and nothing more.

    2. policy_published: what your DMARC record said

    This shows the policy the provider found in your DNS: your domain, your policy (p) and the alignment modes (adkim and aspf, where r means relaxed and s strict). If this doesn’t match what you think you published, check your DNS.

    3. row: the headline result for each sender

    Each record represents one sending IP (and one combination of results). The row gives you:

    • source_ip: the server that sent the email
    • count: how many messages it sent in the period
    • policy_evaluated: the DMARC verdict for DKIM and SPF, which means “passed and aligned with your From domain”, plus the disposition (what the provider did: none, quarantine or reject)

    4. auth_results: the raw SPF and DKIM results

    This is the part people misread. auth_results shows whether SPF and DKIM passed for whichever domain they checked. It doesn’t care whether that domain matches yours. That’s why you can see SPF “pass” here but “fail” in policy_evaluated.

    In the example above, SPF passed, but for bounces.platform-example.com, the platform’s own bounce domain. It doesn’t align with yourdomain.co.uk, so DMARC counts SPF as a fail. DKIM, though, was signed by yourdomain.co.uk and passed, so the email passes DMARC overall. That’s a perfectly healthy result.

    The four patterns you’ll see most often

    Both pass: all good

    DKIM and SPF both pass in policy_evaluated. These are typically your main mailbox provider (Microsoft 365 or Google Workspace) and properly configured platforms. Nothing to do.

    DKIM passes, SPF fails: usually fine

    Common for marketing platforms that use their own bounce domain, and for forwarded email (forwarding breaks SPF but not DKIM). DMARC still passes, as in the example above.

    A sender you recognise fails both: fix this before enforcing

    Your CRM, helpdesk, invoicing tool or website form is sending as your domain but isn’t authenticated. Set up DKIM for your domain in that platform, and add it to SPF if it uses your bounce domain. These are exactly the senders that would be blocked if you moved to p=quarantine or p=reject too early.

    An IP you don’t recognise fails both: likely spoofing

    Look up the IP’s owner (any IP “whois” tool will tell you the network). If it’s not a service you use, someone is sending email pretending to be you. That’s the threat DMARC enforcement stops, and a good reason not to sit on p=none for ever.

    A note on the 2026 DMARC update

    In May 2026 the IETF published updated DMARC standards (RFC 9989, 9990 and 9991), replacing the original 2015 specification. The aggregate report format changes slightly. For example, the DKIM selector becomes required and the pct field is dropped. Most providers still send the older format for now, so you may see both. What the reports tell you, and how you act on them, stays the same.

    Why reading XML by hand doesn’t scale

    One report is manageable. But a busy domain receives reports from dozens of providers every day, each listing many IP addresses, and the picture only becomes clear when you combine them over weeks. That’s why most businesses use a DMARC reporting tool that collects the files, groups IPs by sending service and flags new failures automatically.

    Turn your DMARC reports into action

    Our DMARC monitoring service collects your reports, identifies every service sending as your domain, flags spoofing and new failures, and guides you safely to p=reject. Not sure where you stand? Send a test email to The Inbox Wizard Test and see whether SPF, DKIM and DMARC pass.

    5.0 from 12 Google reviews

  • DMARC p=none: What It Means and How to Move to Enforcement Safely

    DMARC p=none: What It Means and How to Move to Enforcement Safely

    If your DMARC record looks like this, your domain is in “monitoring mode”:

    v=DMARC1; p=none; rua=mailto:[email protected]

    That’s a perfectly good place to start. It’s also where a huge number of businesses stop, often for years, without realising what it leaves open.

    What is DMARC?

    DMARC stands for Domain-based Message Authentication, Reporting and Conformance. It sits on top of SPF and DKIM and does two jobs.

    First, it tells mailbox providers what to do with email that claims to be from your domain but fails authentication: let it through, send it to spam, or reject it. That’s your policy, the p= part of the record.

    Second, it asks providers to send you reports. Aggregate reports (rua=) arrive daily and show every server sending email as your domain, and whether it passed. Forensic reports (ruf=) give details on individual failures, though most big providers no longer send them. The aggregate reports are the useful ones, and our guide to reading a DMARC aggregate report explains how to make sense of them.

    Without DMARC, anyone can send email pretending to be you, and you’d never know. With it, you can see who’s using your domain and, once you’re ready, stop the ones who shouldn’t be.

    What p=none actually does

    DMARC has three policies. Each tells receiving mailbox providers what to do with email that claims to be from your domain but fails authentication:

    PolicyWhat happens to failing emailProtects against spoofing?
    p=noneDelivered as normal; you just get reportsNo
    p=quarantineSent to spam/junkMostly
    p=rejectRefused outrightYes

    So with p=none, someone can send a fake invoice “from” your domain to your customers and it will still be delivered. What you get in return is visibility: the reports sent to your rua address show every server sending as your domain and whether it passes SPF and DKIM.

    Is p=none enough?

    For delivery, mostly yes. Google, Yahoo and Microsoft all require bulk senders to have a DMARC record, and p=none meets that minimum. If you were seeing errors like Microsoft’s 550 5.7.515, a p=none record (plus passing, aligned SPF or DKIM) is what clears them.

    For protection, no. Your domain can still be used in phishing and invoice fraud, which damages your reputation with customers and with mailbox providers.

    For BIMI, no. If you want your logo to appear next to your emails in Gmail and other inboxes, BIMI requires an enforcement policy: p=quarantine or p=reject.

    Why businesses get stuck on p=none

    The fear is reasonable: “If I switch to reject and I’ve missed something, my own emails will stop arriving.” That’s exactly what happens when a business moves too fast. A payroll system, a website contact form, a CRM or an old marketing platform is still sending as the domain without being authenticated, and those emails disappear.

    The way out is not to stay on p=none for ever. It’s to use the reports to find every sender first.

    A safe path from p=none to p=reject

    1. Make sure reports are arriving, and actually read them

    DMARC aggregate reports arrive as zipped XML files, usually daily from each provider. They’re not meant to be read by humans in their raw form. Use a DMARC reporting service (or ours) to turn them into a readable list of sending sources.

    2. List every legitimate sender

    Go through each source in the reports and label it: Microsoft 365 or Google Workspace, your email marketing platform, CRM, helpdesk, accounting software, website, and so on. Anything you don’t recognise is either a forgotten tool or someone spoofing you.

    3. Fix authentication and alignment for each one

    For every legitimate sender, set up DKIM signed with your domain, and add it to SPF where the platform supports it. DMARC passes when SPF or DKIM passes and matches the domain in your From address. DKIM is the more reliable of the two, because it survives forwarding.

    4. Move to p=quarantine

    Once your reports show your legitimate mail passing consistently (we suggest at least two to four weeks of clean data), update the record:

    v=DMARC1; p=quarantine; rua=mailto:[email protected]

    Keep watching the reports. If a legitimate source starts failing, it goes to spam rather than vanishing, so you can catch it and fix it.

    5. Move to p=reject

    After another few weeks with no surprises, go to full protection:

    v=DMARC1; p=reject; rua=mailto:[email protected]

    6. Don’t forget subdomains and parked domains

    Your subdomains inherit your policy unless you set sp=. Domains you own but never send from (old brand names, .ie or .com variants of your .co.uk) should be locked down with v=spf1 -all and p=reject straight away, because they’re easy targets for spoofing.

    How long should the whole process take?

    For most small and medium-sized businesses, six to twelve weeks from p=none to p=reject is realistic. The time goes mainly on tracking down the senders nobody remembered.

    Where does your domain stand?

    Send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass for your domain before you move to enforcement. Want it done for you? Our DMARC service handles the reports, finds every sender and takes your domain to p=reject safely.

    5.0 from 12 Google reviews