Category: Deliverability

  • Microsoft 365 Outage: What Happened to Outlook and Email, and How Big Is It?

    Microsoft 365 Outage: What Happened to Outlook and Email, and How Big Is It?

    If Outlook or Teams has been playing up since Thursday, it was not just you. Microsoft dealt with a large outage affecting Exchange Online, the service behind email for businesses on Microsoft 365, and a lot of email was delayed. Here is what we know now, who was affected, and what it means for your email.

    Updated Monday 16 November. Microsoft has marked the incident as resolved and promised a full Post-Incident Report, so check the Microsoft links further down for the latest.

    What happened

    Microsoft opened an incident called EX1550543 at 16:17 UTC (the same as UK and Irish time at this time of year) on Thursday 12 November, covering people unable to connect to their mailboxes in Exchange Online. The first message only mentioned the Americas, but Microsoft later confirmed that users in any region could be affected.

    Microsoft’s explanation changed as the incident went on. It first pointed to servers that had become unexpectedly unavailable after failing automated health checks, which pushed extra load onto the remaining servers. It has since given a preliminary root cause: an issue during an earlier network capacity upgrade, which surfaced following a recent network change. Microsoft has confirmed it was a technical issue, not a cyberattack and not related to AI or agents. A full Post-Incident Report is due to confirm the details.

    Who is affected

    The affected ways of getting to a mailbox included Outlook on the web, desktop Outlook, phones and API based integrations. So if you tried rebuilding your Outlook profile, that was not going to help, the problem was on Microsoft’s side.

    Other services that depend on Exchange were hit too, with reports covering Teams, SharePoint, Copilot and Defender XDR. Teams chats and calls could carry on working while calendar and scheduling features failed, as those rely on Exchange. If you use AI or automation tools that read your Microsoft mailbox or calendar, those will have been struggling as well. Businesses running a hybrid setup with an on-premises mail server could also see mail flow affected.

    It reached well beyond small businesses. In Ireland, the HSE warned of delayed emails and intermittent problems with video conferencing, and Cork City and County Councils reported disruption. In the UK, GPs, pharmacies, councils and schools were hit, and several police forces asked people to report crimes by phone instead of online. There was also a separate Teams incident earlier on Thursday, and Microsoft has not said if the two are related.

    What it means for your email

    The main thing is that delayed mail is not the same as lost mail. Microsoft extended its email timeout window to 48 hours so delayed messages do not expire while it catches up. Nothing so far suggests messages were lost, so expect late delivery rather than missing mail.

    If you are on the sending side, our advice is to leave your DNS and MX records alone. Changing them will not fix a capacity problem at Microsoft and can add work later. A few things are worth doing instead:

    • Check your bounce and deferral logs over the next few days, in case anything to Microsoft recipients got stuck.
    • If you have a campaign due to go out, consider holding it until the delays clear.
    • Once things settle, run an inbox placement test to confirm your email is landing where it should.

    If mail to Outlook, Hotmail or Live addresses keeps going to junk after the outage is over, that is a separate problem. Our guide to emails going to junk in Outlook or Hotmail covers what to check.

    Where things stand now

    Microsoft has marked the incident as resolved, with service restored. Recovery was not smooth. At one point a fix it was rolling out did not work as expected, and servers it had brought back could become unresponsive again once traffic returned. Some customers and regions took longer than others to recover, so if you are still seeing delayed email, check your own service health in the admin centre.

    Microsoft has promised a preliminary Post-Incident Report within two business days of the incident being resolved and a final one within five business days. For the latest, including the Post-Incident Report once it is published, go to Microsoft directly:

    How big is this?

    It is a big one. Nearly 130,000 reports came in on Downdetector at the peak on Thursday, across 74 countries. For comparison, the Outlook outage in March 2025 had around 37,000 reports. Reuters described Thursday’s disruption as lasting roughly 10 hours, but it carried on into Friday, and Irish coverage had it stretching beyond 18 hours at one point. An Exchange Online outage in September 2025 was described as mostly restored about 14 hours after Microsoft’s first post.

    Microsoft said in January it had more than 450 million paid Microsoft 365 commercial subscriptions. That is the size of the user base, not the number affected, but it shows how many businesses rely on one provider for email.

    Have a plan B for email

    A cloud provider going down is out of your hands, but a plan B is not. Even something as simple as a phone number or a second way to reach your key customers makes a difference when email is out.

    Need a hand with your email?

    If you would like us to look at how your email is set up, or you need help with anything in email or AI & automation, give us a shout. You can also send a test email to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass.

    ★★★★★ 5.0 from 12 Google reviews

  • How to Set Up DKIM in Microsoft 365 (Step by Step)

    How to Set Up DKIM in Microsoft 365 (Step by Step)

    If your business email runs on Microsoft 365, there’s a good chance DKIM isn’t set up for your own domain. Microsoft signs mail from your yourcompany.onmicrosoft.com domain automatically, but not mail sent from your custom domain until you switch it on. Without it, DKIM can’t help your emails pass DMARC, which matters more every year as Gmail and Microsoft tighten their rules.

    Here’s how to set it up, step by step, in about 15 minutes plus waiting for DNS.

    Before you start

    • You need a Microsoft 365 admin account with access to the Microsoft Defender portal.
    • You need access to your domain’s DNS settings (your registrar or DNS host).
    • Your domain must already be added and verified in Microsoft 365.

    Step 1: open the DKIM settings

    In the Microsoft Defender portal, go to Email & collaboration → Policies & rules → Threat policies → Email authentication settings, then open the DKIM tab. You’ll see a list of your domains with their DKIM status.

    Step 2: get your two CNAME records

    Select your domain. If DKIM has never been set up, switch the toggle to Enabled. Microsoft will show an error explaining that the CNAME records are missing. That’s expected. The domain’s details panel then shows two records under Publish CNAMEs, which look like this:

    Host name:  selector1._domainkey
    Points to:  selector1-yourdomain-co-uk._domainkey.yourcompany.n-v1.dkim.mail.microsoft
    
    Host name:  selector2._domainkey
    Points to:  selector2-yourdomain-co-uk._domainkey.yourcompany.n-v1.dkim.mail.microsoft

    Copy the exact values from the portal rather than typing them yourself. Domains added before May 2025 use an older format ending in onmicrosoft.com, and the letter before -v1 varies between tenants.

    Step 3: add both CNAMEs to your DNS

    At your DNS host, create two CNAME records with those host names and values. You need both, even though only one is used at a time: Microsoft switches between them when it rotates keys.

    A common mistake: some DNS panels add your domain to the host name automatically, so enter just selector1._domainkey rather than the full domain if your panel works that way.

    Step 4: switch on signing

    Once DNS has updated (minutes to a few hours), go back to the domain in the DKIM tab and turn on Sign messages for this domain with DKIM signatures. The status should change to Signing DKIM signatures for this domain. If it still says CnameMissing, give DNS a little longer and check the records for typos.

    Step 5: move to a 2048-bit key

    Microsoft has historically created 1024-bit keys by default. Google recommends 2048-bit keys, and they’re stronger. In the domain’s details, choose Rotate DKIM keys and pick 2048 bits if offered (or use PowerShell: Rotate-DkimSigningConfig -Identity yourdomain.co.uk -KeySize 2048). A rotation takes around four days to take effect, and you need to rotate twice to move both selectors to 2048.

    Step 6: check it’s working

    Send an email from your Microsoft 365 mailbox to a Gmail or Outlook.com address and view the full headers. You’re looking for:

    DKIM-Signature: ... d=yourdomain.co.uk; s=selector1 ...
    Authentication-Results: ... dkim=pass header.d=yourdomain.co.uk

    If the signature shows d=yourcompany.onmicrosoft.com instead, signing isn’t on yet for your custom domain. Our guide to why DKIM fails covers the other common errors.

    Don’t stop at Microsoft 365

    DKIM in Microsoft 365 only covers mail sent from your Microsoft 365 mailboxes. Your newsletter platform, CRM, helpdesk and invoicing system each need their own DKIM set up for your domain. Your DMARC reports will show you which ones are still unsigned. And once everything aligns, you can move your DMARC policy to enforcement.

    Need a hand with Microsoft 365?

    Send a test email from Microsoft 365 to The Inbox Wizard Test to see whether SPF, DKIM and DMARC pass, or talk to us about setting up DKIM for Microsoft 365 and every other platform that sends as your domain.

    5.0 from 12 Google reviews

  • Gmail “550 5.7.26” Unauthenticated Email Error: How to Fix It

    Gmail “550 5.7.26” Unauthenticated Email Error: How to Fix It

    If emails to Gmail addresses are bouncing back with a 550 5.7.26 error, Google has rejected them before they reached the inbox or the spam folder. Since November 2025, Google has been permanently rejecting more non-compliant bulk mail rather than just slowing it down, so this error has become far more common.

    The good news: 5.7.26 is almost always an authentication problem, and authentication problems are fixable.

    What the error says

    The bounce usually contains one of two messages:

    550 5.7.26 This mail has been blocked because the sender is unauthenticated.
    Gmail requires all senders to authenticate with either SPF or DKIM.

    This means neither SPF nor DKIM passed for your email.

    550 5.7.26 Unauthenticated email from yourdomain.co.uk is not accepted due to domain's DMARC policy.

    This means your domain has a DMARC policy of quarantine or reject, and this email failed DMARC, so Gmail is enforcing your own policy.

    Why it’s happening now

    Google introduced its sender requirements in February 2024. All senders need SPF or DKIM, and bulk senders (around 5,000 or more emails a day to Gmail) need SPF, DKIM, DMARC, alignment, one-click unsubscribe and a spam complaint rate below 0.3%. Enforcement started gently with temporary errors, then tightened. From November 2025, Google moved to permanently rejecting more mail that doesn’t comply.

    How to fix it

    1. Find out which email is failing

    Look at the bounce: which address sent it, and from which system? It’s often not your main mailbox but something else sending as your domain: a CRM, an invoicing tool, a website contact form or an old marketing platform.

    2. Check SPF for that sender

    Make sure the service is covered by your SPF record, that you have only one SPF record, and that it stays within the 10-lookup limit. A broken SPF record fails for everything.

    3. Set up DKIM signed with your domain

    In the sending platform’s settings, find “domain authentication” or “DKIM”, add the records it gives you to your DNS, then verify. The signature should read d=yourdomain.co.uk. Our guide to why DKIM fails covers the usual problems.

    4. Check DMARC alignment

    For the DMARC version of the error, SPF or DKIM must not only pass but align: the domain they pass for must match the domain in your From address. A platform that passes SPF for its own bounce domain and signs DKIM with its own domain will fail DMARC even though both checks “pass”.

    5. Don’t fix it by weakening DMARC

    Dropping your DMARC policy back to p=none makes the bounces stop, but it also removes your protection against spoofing. Fix the sender instead. If you need breathing room while you do, read our guide to DMARC policies before changing anything.

    Other things that can trigger 5.7.x rejections

    If authentication is passing and you’re still being rejected, check that you send over TLS, that your sending IP has valid forward and reverse DNS, that marketing email has one-click unsubscribe, and that your spam rate in Google Postmaster Tools is below 0.3%.

    Confirm the fix

    Send a new test to a Gmail address, open it, choose Show original, and check that SPF, DKIM and DMARC all show PASS. Then keep an eye on your DMARC reports for any other service failing in the same way.

    Stop the Gmail bounces

    Send a test email to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, with a score out of 100. If the bounces are coming from a platform you can’t pin down, we’ll find it and fix it.

    5.0 from 12 Google reviews

  • Emails Going to Junk in Outlook or Hotmail? A Guide for UK & Irish Senders

    Emails Going to Junk in Outlook or Hotmail? A Guide for UK & Irish Senders

    Your emails reach Gmail inboxes without trouble, but anyone on Outlook, Hotmail or Live says they found you in junk. It’s one of the most common problems we see from businesses in the UK and Ireland, and Microsoft’s filtering works differently enough from Gmail’s that the usual fixes don’t always carry across.

    Here’s the checklist we work through when a client’s mail is going to junk at Microsoft, in the order that usually finds the problem fastest.

    Why Microsoft matters so much in the UK and Ireland

    A big share of UK and Irish personal email addresses sit with Microsoft: hotmail.co.uk, live.co.uk, live.ie, outlook.com, msn.com and the rest. Plenty of people set up a Hotmail address years ago and never moved. If you sell to consumers, the Microsoft domains are often one of the biggest groups on your list after Gmail.

    It matters for B2B too. Lots of UK and Irish businesses, charities and public bodies run their email on Microsoft 365. Their mail goes through Microsoft’s filtering as well, and their IT team can add stricter rules on top. So when a quote, an invoice or a sales email “never arrived”, Microsoft is often where it went missing.

    Quick check: sort your list by domain and add up the Microsoft ones. That tells you how much of your email (and your revenue) depends on getting this right.

    First: junk or rejected?

    These are two different problems. If your email bounces with an error like 550 5.7.515 Access denied, Microsoft is refusing it outright because authentication failed. Our guide to fixing 550 5.7.515 covers that. If the email arrives but lands in the Junk Email folder, Microsoft accepted it but didn’t trust it enough for the inbox. That’s what this checklist is for.

    1. Authentication: SPF, DKIM and DMARC all passing and aligned

    Since May 2025 Microsoft has required SPF, DKIM and DMARC from high-volume senders to Outlook.com, Hotmail and Live addresses. Even below that volume, mail that fails authentication is far more likely to be junked.

    • Send a test to an Outlook.com address you own and check the headers for spf=pass, dkim=pass and dmarc=pass.
    • Make sure DKIM is signed with your domain, not your email platform’s. Why DKIM fails covers the usual causes.
    • Check you have exactly one SPF record, within the 10-lookup limit.

    2. Sending IP and domain reputation

    Microsoft weighs the reputation of the IP address your mail comes from heavily. If you send from a dedicated IP, register it with Microsoft’s Smart Network Data Services (SNDS), which shows how Outlook.com sees that IP, including complaint rates and spam-trap hits. If you’re on a shared IP through an email platform, your platform manages this, but a sudden drop in placement across all your mail can point to a shared-IP problem worth raising with them.

    Alongside SNDS, sign up to Microsoft’s Junk Mail Reporting Program (JMRP). It sends you a report each time an Outlook.com, Hotmail or Live user marks one of your emails as junk, so you can take them off your list before the complaints pile up. JMRP feeds are now linked to your SNDS account, and since early 2026 the reports no longer include the email body, so add a campaign reference to your headers if you want to know which send caused the complaint. On a shared IP, your email platform usually handles this for you.

    Also check your domain and IPs against the main blocklists. A listing doesn’t always cause junking at Microsoft, but it’s a strong warning sign.

    3. Complaints: people clicking “Report junk”

    Every time an Outlook user marks your email as junk, it counts against you. Common causes:

    • Emailing people who didn’t clearly sign up, or who signed up a long time ago and have forgotten you.
    • An unsubscribe link that’s hard to find, so people report you as junk instead.
    • Sending far more often than people expected when they signed up.

    Microsoft expects a working unsubscribe link in marketing email (and one-click unsubscribe from bulk senders), so make it easy to find.

    4. List hygiene

    Repeatedly sending to addresses that don’t exist tells Microsoft you aren’t maintaining your list. Remove hard bounces straight away, stop mailing people who haven’t opened or clicked in six to twelve months (or send them a short re-engagement campaign first), and never buy or rent lists. Old Hotmail addresses that have been closed are a common source of both bounces and spam traps.

    5. Consistent volume

    Microsoft is suspicious of sudden spikes. If you normally send 2,000 emails a week and suddenly send 40,000 to your whole database, expect a lot of it to land in junk. Build volume up gradually, especially from a new domain or IP. This is called warming.

    6. From and Reply-To addresses

    Use a real, recognisable From name and an address on your own domain that can receive replies. A noreply@ address on a domain that doesn’t match your website looks less trustworthy to filters and to people.

    7. Content and links

    Content matters less than reputation, but it still counts:

    • Avoid link shorteners and links to domains with poor reputation.
    • Keep a sensible balance of text and images. A single large image with little text is a classic spam pattern.
    • Make sure the domains in your links match the brand sending the email.

    8. Engagement

    Microsoft, like Gmail, notices whether people open, reply to and move your emails out of junk. Ask new subscribers to add you to their contacts, and focus regular sends on people who engage. Sending less to unengaged contacts often improves placement for everyone else.

    Test before you guess

    The quickest way to see where you stand is an inbox placement test: you send your campaign to a set of test mailboxes across Outlook, Hotmail, Gmail, Yahoo and corporate Microsoft 365, and see exactly where it lands. It turns “I think we’re going to junk” into a clear answer, and shows whether the problem is Microsoft-specific.

    Find out why you’re landing in junk

    Our deliverability audit runs inbox placement tests across Outlook, Hotmail, Gmail and Microsoft 365, checks your authentication and reputation, and gives you a prioritised list of fixes. Or start by sending a test email to The Inbox Wizard Test, which shows whether SPF, DKIM and DMARC pass.

    5.0 from 12 Google reviews

  • Why DKIM Fails: 6 Common Causes and How to Fix Them

    Why DKIM Fails: 6 Common Causes and How to Fix Them

    DKIM is the part of email authentication that does the heavy lifting. It survives forwarding, it’s what most marketing platforms rely on to pass DMARC, and Google, Yahoo and Microsoft all expect it from bulk senders. So when your headers or DMARC reports show dkim=fail, it’s worth fixing quickly.

    Here are the six causes we see most often, how to spot each one and how to fix it.

    First, a 30-second refresher

    When you send an email, your platform adds a DKIM signature: a header with an encrypted fingerprint of the message, the signing domain (d=) and a selector (s=). The receiving server looks up the public key at selector._domainkey.yourdomain.co.uk and checks the fingerprint still matches. If the key can’t be found, or the message has changed since it was signed, DKIM fails.

    To find which cause you’re dealing with, open the full headers of a failing email and look at the Authentication-Results line. The wording after dkim=fail (or dkim=permerror) usually points straight at the problem.

    Why do you need DKIM as well as SPF? Because they protect different things. SPF checks which server sent the email, and it usually breaks when an email is forwarded. DKIM signs the email itself, so the signature travels with the message and survives forwarding. It also proves the content wasn’t changed on the way. Together with DMARC, they make it very hard for anyone else to send email as you.

    1. The DKIM record is missing or published in the wrong place

    What you’ll see: “no key for signature”, “key not found” or dkim=permerror.

    The receiving server went to look up your public key and found nothing. Usually one of these has happened:

    • The record was never added, or was added to the wrong domain.
    • The DNS panel added your domain to the name automatically, creating s1._domainkey.yourdomain.co.uk.yourdomain.co.uk.
    • The selector in the record doesn’t match the one in the signature (for example, s1 published but s2 used).

    Fix: Compare the s= and d= values in the email’s DKIM signature with the record in your DNS, and look the record up with a DKIM checker to confirm it resolves.

    2. DKIM was set up in DNS but never switched on

    What you’ll see: the email is signed by your platform’s domain instead of yours, or not signed at all.

    Most platforms make you add the DNS records and then click “verify” or “enable” in their settings. Microsoft 365 is the classic example: you publish two CNAME records (selector1._domainkey and selector2._domainkey) and then enable DKIM signing for the domain in the Defender portal. Skip that last step and Microsoft keeps signing with its own default domain.

    Fix: Go back into each platform’s domain authentication settings and confirm DKIM signing shows as active for your domain.

    3. The key has been broken by your DNS panel

    What you’ll see: “invalid public key”, “key syntax error” or dkim=permerror.

    DKIM keys are long. A 2048-bit key is over 400 characters, and a single DNS text string can only hold 255. Some DNS panels split long values automatically and some don’t. Copy-and-paste can also add stray spaces, line breaks or extra quotation marks, or cut off the end of the key.

    Fix: Republish the record exactly as your platform provides it. If your DNS panel struggles with long values, use the CNAME option many platforms offer instead. The platform then hosts the key and keeps it up to date.

    4. The email was changed after it was signed

    What you’ll see: “body hash did not verify” or “signature did not verify”.

    DKIM’s fingerprint covers the message body and key headers. If anything changes them on the way, the fingerprint no longer matches. Common culprits:

    • Email security gateways that rewrite links or add “external sender” banners
    • Mailing lists and Google Groups that add footers or change the subject line
    • Signature or disclaimer tools that add text after sending
    • Forwarding services that alter the message

    Fix: Make sure any tool that modifies outgoing mail does so before DKIM signing, not after. For mailing lists you don’t control, there’s little you can do. That’s normal, and it’s one reason DMARC passes if either SPF or DKIM passes and aligns.

    5. The key was rotated or removed

    What you’ll see: DKIM was passing and suddenly fails across all mail from one service.

    Platforms periodically switch to new keys, and people tidying DNS sometimes delete an “unrecognised” _domainkey record that was still in use. If a key is replaced before the platform stops using it, signatures fail until things catch up.

    Fix: Never delete a _domainkey record without checking your DMARC reports to see whether anything still signs with that selector. Where possible, use CNAME-based DKIM so the platform handles rotation for you. And check you’re on 2048-bit keys: Google recommends them, and some older setups still use weaker 1024-bit keys.

    6. DKIM passes, but not for your domain

    What you’ll see: dkim=pass in the headers, but DKIM shown as failing in DMARC reports.

    This one catches out a lot of people. DKIM can pass perfectly well for the platform’s own domain (for example d=platform-example.com). DMARC, though, only counts DKIM when the signing domain matches your From domain. That’s called alignment. Without it, DKIM is technically working but does nothing for your DMARC result or your sender reputation.

    Fix: Set up custom DKIM (often called “domain authentication” or “branded sending domain”) in every platform that sends as your domain, so the signature reads d=yourdomain.co.uk. This matters even more as you move your DMARC policy from p=none to enforcement.

    A quick DKIM health check

    • Every service that sends as your domain signs with d=yourdomain.co.uk.
    • Every selector in use has a working record in your DNS.
    • Keys are 2048-bit where the platform supports it.
    • Your DMARC reports show DKIM passing and aligned for all legitimate sources.

    Get your DKIM sorted

    DKIM problems are fiddly to track down across several platforms, and they quietly hold back your inbox placement until they’re fixed. Start by sending a test email to The Inbox Wizard Test, or let us find every service sending as your domain and set up aligned, 2048-bit DKIM for each one.

    5.0 from 12 Google reviews

  • Two SPF Records? Why It Breaks Your Email and How to Merge Them

    Two SPF Records? Why It Breaks Your Email and How to Merge Them

    Here’s a mistake that breaks email for thousands of businesses, and it usually starts with good intentions. You sign up for a new email platform, it tells you to “add this SPF record to your DNS”, and you add it. The problem is that you already had one.

    A domain can only have one SPF record. With two, SPF doesn’t check both and pick the best result. It fails completely.

    What is SPF, and what does a record look like?

    SPF, or Sender Policy Framework, is a list of the servers allowed to send email for your domain. You publish it as a TXT record in your DNS. When an email arrives claiming to be from you, the receiving server checks whether it came from one of the servers on that list.

    A typical SPF record looks like this:

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

    It always starts with v=spf1. Each include: adds a service that sends for you, such as Google Workspace or your email platform. It ends with an all rule, which says what to do with everything else: ~all (soft fail) is the usual choice, and -all (hard fail) is stricter.

    SPF on its own doesn’t stop spoofing, because it checks a hidden “envelope” address rather than the From address your subscribers see. That’s why it works alongside DKIM and DMARC. But it’s the first thing mailbox providers check, and the easiest one to break by accident, which is what the rest of this guide is about.

    Why two SPF records break SPF

    The SPF standard (RFC 7208) is explicit: a domain must not publish more than one SPF record. When a receiving server looks up your domain and finds two TXT records that start with v=spf1, it returns a PermError (“permanent error”) and stops. Neither record is used.

    In practice that means:

    • Every email from your domain fails SPF, including your normal day-to-day email from Microsoft 365 or Google Workspace.
    • DMARC can only pass through DKIM. Any service that isn’t signing with DKIM for your domain will fail DMARC.
    • Emails to Outlook and Hotmail can be refused with 550 5.7.515 errors, and once your DMARC policy is quarantine or reject, failing emails go to spam or bounce.

    How to check if you have two SPF records

    Look at the TXT records on your root domain (the one shown as @ or left blank in most DNS panels). Count how many start with v=spf1. More than one means you have the problem.

    Common giveaways:

    • One record from your mailbox provider and a second added later by a marketing, CRM or helpdesk platform.
    • An old record left behind after moving from one email host to another.
    • A record added by your web host or domain registrar automatically, alongside the one you created.
    • A v=spf2.0 record (an old Microsoft “Sender ID” format). It isn’t a second SPF record in the same sense, but it’s obsolete and worth removing while you’re there.

    Send a test email to The Inbox Wizard Test and it shows whether SPF passes or fails for your domain. The link is at the end of this post.

    How to merge them into one

    Say you have these two records:

    v=spf1 include:spf.protection.outlook.com -all
    v=spf1 include:_spf.your-email-platform.com ~all

    Merging them takes four steps.

    1. Keep one v=spf1 at the start

    Every SPF record starts with v=spf1, exactly once.

    2. Combine all the mechanisms in the middle

    Take every include:, ip4:, ip6:, a and mx from both records and list them once each, separated by spaces. Remove duplicates.

    3. Keep one all at the end

    Choose a single ending. ~all (soft fail) is the common choice while you’re setting things up, and -all (hard fail) is stricter. Don’t include both, and make sure all is the last thing in the record. Anything after it is ignored.

    4. Delete the old records and publish the merged one

    v=spf1 include:spf.protection.outlook.com include:_spf.your-email-platform.com ~all

    Publish this as the only SPF TXT record on your root domain, then delete the others.

    Before you merge: two things to check

    Do you still need every entry?

    Merging is a good moment to remove services you no longer use. It’s also worth checking whether a platform needs to be in your SPF at all. Many marketing platforms use their own bounce domain, so your SPF isn’t what they’re checked against. They pass DMARC through DKIM signed with your domain instead.

    Will the merged record go over 10 lookups?

    Combining two records often pushes you over SPF’s 10-lookup limit, which causes a different PermError. If that happens, our guide to fixing “too many DNS lookups” covers how to trim it back.

    What about subdomains?

    The one-record rule applies per domain name. yourdomain.co.uk and news.yourdomain.co.uk can each have their own SPF record. That’s a useful way to give a marketing platform its own SPF without touching the record your main email depends on.

    After you’ve fixed it

    • Wait for DNS to update (usually minutes, occasionally a few hours).
    • Re-check that exactly one v=spf1 record exists.
    • Send a test email from each service and check the headers show spf=pass.
    • Keep an eye on your DMARC reports for a week to confirm everything is passing.

    Test your SPF in seconds

    Not sure whether your SPF is working? Send a test email to The Inbox Wizard Test and it shows whether SPF passes for your domain. If you’d rather someone just sorted it, we’ll merge your records, trim anything you no longer need and confirm every service still passes.

    5.0 from 12 Google reviews

  • SPF PermError “Too Many DNS Lookups”: What It Means and How to Fix It

    SPF PermError “Too Many DNS Lookups”: What It Means and How to Fix It

    If an SPF checker or a bounce message has told you SPF PermError: too many DNS lookups, your SPF record has quietly stopped working. Mailbox providers aren’t partly checking it. As far as they’re concerned, it’s broken, and that can drag down DMARC and your inbox placement with it.

    The good news is that it’s one of the most fixable problems in email authentication. Here’s what’s going on and how to sort it.

    What “too many DNS lookups” means

    Your SPF record lists the services allowed to send email as your domain. To check it, the receiving server has to look up each entry in DNS. To stop SPF checks being abused or slowing mail down, the SPF standard (RFC 7208) caps these lookups at 10 per check.

    Go over 10 and the result is a PermError (“permanent error”). The receiver stops evaluating and treats your SPF as failed. That means:

    • SPF can’t help your emails pass DMARC, so you’re relying entirely on DKIM.
    • Any sender that isn’t signing with DKIM for your domain will fail DMARC. Under Microsoft’s rules for Outlook and Hotmail, that can mean 550 5.7.515 rejections.
    • Once you move DMARC to quarantine or reject, those emails go to spam or bounce.

    What counts towards the limit

    Not everything in an SPF record costs a lookup:

    • Each counts as one lookup: include:, a, mx, ptr, exists: and the redirect= modifier.
    • Free (no lookup): ip4:, ip6: and all.

    The catch is nested lookups. When you add include: for a provider, you also take on every lookup inside their SPF record. One include can cost you three or four lookups on its own.

    There’s also a lesser-known second limit: no more than two “void” lookups. These are lookups that return nothing, typically an include: pointing at a service that has since shut down or changed its address. Go over two and you get a PermError too.

    How UK businesses end up over the limit

    It rarely happens all at once. A typical record grows over a few years: Microsoft 365 or Google Workspace, then a newsletter platform, then a CRM, a helpdesk, accounting software that emails invoices, a booking system, the website’s contact form, and a platform someone trialled in 2022 and never removed. Each one asked you to “add our include to your SPF record”, and nobody added up the total.

    v=spf1 include:spf.protection.outlook.com include:_spf.google.com include:mail.crm-example.com include:sendgrid.net include:helpdesk-example.com a mx ~all

    A record like this can easily need 12 to 15 lookups once the nested includes are counted.

    How to fix it

    1. Count your lookups

    Run your domain through an SPF lookup counter that expands every nested include, so you can see which entries cost the most. Write the list down: you’ll need it for the next steps.

    2. Remove anything you no longer use

    This is the quickest win. Ask “do we still use this?” of every include. Old marketing platforms, a previous email host after a migration, and abandoned trials are all common.

    3. Check whether each platform actually needs to be in your SPF

    SPF checks the Return-Path (bounce) domain, not the From address people see. Many marketing and transactional platforms use their own bounce domain unless you set up a custom one. In that case your include: does nothing for SPF at all. Those emails pass DMARC through DKIM signed with your domain instead. Check each platform’s domain authentication settings before removing anything, but this often frees up several lookups.

    4. Swap a and mx for fixed IP addresses

    If your web server or mail server has a fixed IP address, list it with ip4: (free) instead of a or mx (one lookup each). Only do this for IPs you control and that won’t change without you knowing.

    5. Remove ptr

    The SPF standard says ptr should not be used. It’s slow, unreliable and costs a lookup. If it’s in your record, it can almost always go.

    6. Move some senders to a subdomain

    Send marketing from news.yourdomain.co.uk or invoices from billing.yourdomain.co.uk, each with its own SPF record. Every subdomain gets its own 10-lookup allowance, and it keeps the reputation of your marketing mail separate from your day-to-day business email.

    7. Be careful with “SPF flattening”

    Flattening replaces includes with the IP addresses behind them, which brings the count right down. The risk is that providers change their IPs without telling you, and a flattened record silently goes out of date. If you flatten, use a service that keeps the record updated automatically rather than doing it by hand once.

    After you’ve made the change

    • Make sure you still have exactly one SPF record. Two v=spf1 records is a separate PermError.
    • Re-count the lookups: you want 10 or fewer, ideally with a couple spare for the next tool you adopt.
    • Send test emails from each platform and check the headers show spf=pass or an aligned dkim=pass.
    • Watch your DMARC reports for a week or two to catch any sender you missed.

    Test your SPF now

    Not sure whether your SPF is working? Send a test email to The Inbox Wizard Test and it shows whether SPF passes. If you’d rather hand it over, we’ll untangle your SPF record, set up DKIM for every platform you send from and make sure nothing breaks along the way.

    5.0 from 12 Google reviews

  • How to fix “550 5.7.515 Access denied” from Outlook and Hotmail

    How to fix “550 5.7.515 Access denied” from Outlook and Hotmail

    If you’ve started seeing bounces like this when emailing Outlook, Hotmail or Live addresses, you’re not alone:

    550 5.7.515 Access denied, sending domain [yourdomain.co.uk] doesn't meet the required authentication level.

    It means Microsoft has rejected your email outright. It hasn’t gone to junk; it hasn’t been delivered at all. The good news is that the fix is almost always a DNS change you can make in under an hour.

    Why Microsoft is rejecting your email

    Since 5 May 2025, Microsoft has enforced authentication rules for anyone sending more than 5,000 emails a day to its consumer mailboxes (outlook.com, hotmail.com and live.com, including hotmail.co.uk and live.co.uk). Microsoft originally said non-compliant mail would go to junk. Instead, it chose to reject it, and the 5.7.515 error is the result.

    To get through, your sending domain needs all three of these:

    • SPF must pass: the server sending your email must be listed in your domain’s SPF record.
    • DKIM must pass: your email must carry a valid DKIM signature for your domain.
    • DMARC must exist: at least p=none, and it must align with SPF or DKIM (ideally both).

    The 5,000-a-day threshold is Microsoft’s target, but Microsoft’s own support forums are full of small businesses and individuals hitting this error too. Treat these rules as the minimum for anyone emailing Microsoft customers.

    Step 1: Check what’s actually missing

    Before you touch DNS, find out which of the three checks is failing. You can do this two ways:

    1. Take our free test. Send an email to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, in seconds.
    2. Read the headers of a sent email. Send a message to a Gmail or Outlook address you own, open the original message/headers, and look for the Authentication-Results line. You want spf=pass, dkim=pass and dmarc=pass.

    Step 2: Fix SPF

    Your domain should have one TXT record starting v=spf1, listing every service that sends email as you: your mailbox provider (Microsoft 365 or Google Workspace), your email marketing platform, your CRM, your helpdesk, your invoicing tool and so on.

    v=spf1 include:spf.protection.outlook.com include:_spf.your-email-platform.com ~all

    (Replace the second include: with the value your email platform gives you. Each provider publishes its own.)

    Common mistakes we see:

    • Two SPF records. If you have more than one v=spf1 record, SPF fails for everything. Merge them into one.
    • Too many lookups. SPF allows a maximum of 10 DNS lookups. Pile up enough include: entries and SPF breaks with a PermError.
    • A forgotten sender. A newer tool (a CRM or booking system, say) sending as your domain but not listed in SPF.

    Step 3: Fix DKIM

    DKIM is set up inside each sending platform, not just in DNS. In Microsoft 365, Google Workspace, Mailchimp, Klaviyo, HubSpot and most others, there’s a “domain authentication” or “DKIM” setting that gives you records (usually CNAMEs) to add to your DNS. Add them, then go back and click verify or enable. That last click is the step most people miss.

    The important detail: DKIM must be signed with your domain. If your platform signs with its own domain (for example d=sendingplatform.com), DKIM technically passes but won’t align with DMARC.

    Step 4: Add a DMARC record

    If you have no DMARC record, add a TXT record at _dmarc.yourdomain.co.uk:

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

    p=none is enough to satisfy Microsoft (and Google and Yahoo). The rua address receives daily reports showing every service sending as your domain and whether it passes, which is the information you need to move to a stronger policy later. (Our guide to why DMARC matters covers this in more depth.)

    Step 5: Retest and resend

    DNS changes can take anything from a few minutes to a few hours to take effect. Once they have, send another test email to an Outlook or Hotmail address and check the headers again. When SPF or DKIM passes and aligns with your From domain, and DMARC passes, the 5.7.515 bounces stop.

    Still bouncing?

    If everything passes and you’re still being rejected, the cause is usually one of these:

    • A third-party platform sending as your domain that you didn’t know about (DMARC reports reveal these).
    • Alignment: SPF passes for the platform’s bounce domain but not yours, and DKIM is signed with the platform’s domain.
    • Forwarding, which can break SPF. DKIM is what survives forwarding, so make sure it’s in place.

    Get it sorted today

    Every day these bounces continue, invoices, quotes and campaigns aren’t reaching a big share of your UK customers, as Outlook and Hotmail addresses are everywhere. Send a test email to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, in seconds. Prefer someone to just fix it? We set up and verify SPF, DKIM and DMARC for UK and Irish businesses, usually without any downtime to your email.

    5.0 from 12 Google reviews