DKIM: signature expired (x= tag in the past) — signed message too old when verified
The DKIM signature has an expiry time and it passed before the message was verified.
DKIM signature expireddkim=fail (signature expired)signature has expired x= tagdkim=permerror signature expiredDKIM verification failed: signature expired Meaning
Delayed delivery (long retry queues), replays or archived messages hit the x= expiry. Use a reasonable signature lifetime (days, not minutes) or omit x=; fix the delay that caused the old message to arrive late. Check that the sender's clock is correct.
Common causes
- Signature lifetime too short
- Message delayed in queue/retries
- Wrong sender clock
- Message re-verified from archive
- Signer configured with a tiny expiry
⚡ Quick fix
- Remove or lengthen the
x=expiry - Fix mail queue delays
- Sync clocks (NTP)
Detailed fix by platform
Config
# OpenDKIM: SignatureTTL 604800 # 7 days
How to diagnose
- x= — In the past?
- Delay — Where?
- Clock — Correct?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 5.4.310 Exchange Online: 550 5.4.310 DNS domain does not exist (DNS domain name could not be resolved)
- 550 5.1.8 550 5.1.8 Sender address rejected: Domain not found (sender domain has no DNS A/MX)
- bh mismatch DKIM: body hash did not verify — message modified after signing (footers, mailing list, line wrapping)
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- Laravel: Connection could not be established with host Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
- self-signed certificate (SMTP TLS) Nodemailer: Error: self signed certificate in certificate chain (code: 'ESOCKET') / unable to verify the first certificate
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026