Mail routing, by date
Each MX change is recorded the day it appeared. See which provider a domain used, and when it moved off Google Workspace or Microsoft 365, without asking the previous admin.
Past MX records
Mail can fail after an MX record changes and delivery shifts provider. DNSTimeMachine shows the previously observed mail hosts and the first-seen date of the new routing, giving an email administrator a concrete cutover point to investigate.
Enter the domain that stopped receiving mail or recently changed provider.
Publicly observed DNS history, not a complete zone backup.
For email administrators and MSPs diagnosing a failed Google Workspace, Microsoft 365, or other provider migration.
How the history reads
Each captured answer is stored with its observation date, so you can compare the earlier value with the change that replaced it.
Each MX change is recorded the day it appeared. See which provider a domain used, and when it moved off Google Workspace or Microsoft 365, without asking the previous admin.
Mail problems are rarely just MX. DNSTimeMachine keeps the TXT history too, so SPF and DKIM changes line up with the routing changes on the same day.
After a mail migration, the useful answer is what the records were before the cutover. That is exactly what the past MX history shows, provider and date together.
"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
Historical MX observations can show the mail hosts seen before a routing change and the date the replacement was first observed.
Often, mail-host names indicate providers such as Google Workspace or Microsoft 365. Custom gateways and relays may require additional investigation.
Only after verifying that the old provider and mailboxes still exist. DNS history helps identify the prior routing, but it cannot confirm that the previous service remains valid.