Topic · Authentication
DKIM signature expiration
A DKIM signature may carry an x= timestamp after which the signature is no longer intended to be valid.
How it works
The verifier compares x= with the validation time, using the related signing time where present.
What can go wrong
Delayed queues or stale replayed mail may encounter expiration-related verification problems.
What to check or do
Inspect t= and x= timestamps, clock synchronization and queue delays when investigating failure.
Practical scenario
A notification service signs a message with a short x= expiration, then experiences a long outbound queue backlog. The eventual recipient sees an expired DKIM signature even though the sender was authorized when the mail was prepared.
Verification checklist
- Compare signature x= and t= timestamps with the delivery time.
- Check sender and receiver clock synchronization.
- Review queue-age metrics and actual retry delays.
- Adjust signature lifetime only after confirming operational and replay-risk needs.
How to investigate DKIM signature expiration
- Signal to investigate
- A message delayed in transit may reach the receiver after a DKIM x= expiration.
- Evidence to collect
- Compare signature t= and x= with the received timestamp and plausible queue delays.
- Common wrong conclusion
- A signature time limit affects DKIM validation, not whether the mailbox itself exists.
Put this into practice
Run a focused check, then explore protection if your domain needs it.