The auth layer, not the routing layer
MX says where mail goes. SPF, DKIM, and DMARC say who is allowed to send it. All three live in TXT records, and DNSTimeMachine keeps each edit dated and separate from the MX history.
SPF record history
See the SPF record that changed before mail broke.
Email authentication can fail after an SPF include is removed, a DKIM selector rotates, or a DMARC policy tightens. DNSTimeMachine shows previously observed authentication values and the date each change first appeared, so you can compare the TXT history with the deliverability timeline.
Enter the mail domain whose SPF, DKIM, or DMARC history you need.
Publicly observed DNS history, not a complete zone backup.
For email administrators and deliverability teams tracing an authentication failure to a past TXT value.
How the history reads
The record, before and after.
Each captured answer is stored with its observation date, so you can compare the earlier value with the change that replaced it.
Catch the change that broke DKIM
A removed SPF include or a rotated DKIM selector can break authentication with no clear error of its own. The dated trail shows the value that changed and gives the deliverability investigation a concrete lead.
DMARC policy over time
See when a domain moved from p=none to quarantine or reject. Useful for a sudden spam-folder problem, or an investigation into messages spoofed under an older, weaker policy.
When you reach for this.
- DMARC reports show failures and you need the old SPF value
- DKIM verification broke after a key rotation
- Good mail started landing in spam after an SPF edit
- Investigating a spoofed message against past auth records
"What did this used to be?"
The question a live lookup cannot answer. Enter the domain above and we will send its history the moment access opens.
Look up a domainDirect answers
Questions about spf record history.
Can I see a domain's old SPF record?
If the public TXT value was observed before it changed, DNS history can show the earlier SPF policy and the first date its replacement appeared.
Does SPF record history include DKIM and DMARC?
They are separate TXT-based mechanisms. A useful email-authentication timeline can show SPF policy changes, public DKIM selector records, and DMARC policy changes together.
Can an old SPF value be copied back safely?
Not automatically. Sending services, keys, and policy requirements may have changed. Treat the old value as evidence and validate it before restoring anything.