What does “550 5.7.26 This email has been blocked because the sender is unauthenticated” mean?
Gmail blocked the message because it passed neither SPF nor DKIM.
Last read from the sources at the foot of this page.
This email has been blocked because the sender is unauthenticated
What does it mean?
Gmail checked two things: whether the sending server is listed in your SPF record, and whether the message carried a valid DKIM signature. Both failed.
The 421 4.7.26 wording below is the same finding with a temporary limit instead of a block.
What exactly does the source say?
550 5.7.26 This email has been blocked because the sender is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = did not pass SPF [domain-name] with ip: [ip-address] = did not pass. For instructions on setting up authentication, go to Email sender guidelines.
Gmail's page writes domain-name and ip-address where your bounce shows your own domain and the sending address.
421 4.7.26 This email has been rate limited because it is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = did not pass SPF domain-name with ip: ip-address = did not pass. To resolve this issue, go to Email sender guidelines.Why would a small firm see it?
Your domain has no SPF record, or the service that sent this message is not in it, and the service does not sign with DKIM.
How do I fix it?
- List every service that sends mail as your domain: your mailboxes, your invoicing or accounting tool, your booking system, your newsletter tool, your website's contact form.
- Find each service's SPF include in its own help pages.
- Send yourself a message through the service and open its headers.Look for spf=pass.
- Turn on DKIM signing for your domain at your mail provider, and at each other service that sends as your domain.Each one gives you a record to publish.
Keep one SPF record. Add the service inside the one record you have, before its last word, and keep every service already in it. A second SPF record makes the check fail for every message.
An SPF record may make at most 10 DNS lookups. Each include counts, and so do the includes inside it. Past 10 the check fails, so take out services you no longer use before adding a new one.
What else do the sources say?
Starting February 1, 2024, all email senders who send email to Gmail accounts must meet the requirements in this section. Important: If you send more than 5,000 messages per day to Gmail accounts, follow the Requirements for sending 5,000 or more messages per day. Set up SPF or DKIM email authentication for your sending domains.
Messages that aren't authenticated with these methods might be marked as spam or rejected with a 5.7.26 error.
Where does this come from?
- Google Workspace: Gmail SMTP errors and codesknowledge.workspace.google.comRead 14 October 2026
- Gmail: Email sender guidelinessupport.google.comRead 14 October 2026
See what is open before anyone else does.
We read from outside, find each way in first, and show it with a check anyone can re-run. No access, nothing tested, no obligation.
- We read your firm from outside.
- You see what is open, with the proof for the lead finding.
- If it is worth it, you order.
What happens if you go ahead. More at getleaktrace.com/see-it-first/.
Read the transcript
- 72 hours. One domain. Nothing to install.
- Discover. Every way in, found from outside.
- Validate. Every finding, proven. Dated and checkable by anyone.
- Close. Forged email: one click per step, where we reach your DNS host and you approve it.
- You get the fix for the rest, step by step, and we re-check until it is closed.
- Monitor. On monitoring: email settings, look-alikes and new host names re-checked every hour. Alerts within the hour.
- Every paid assessment is human-verified before release.
- The AI defense layer for businesses. getleaktrace.com/see-it-first/