Tracking Resource Changes via Object History
See every change to domains, DNS zones, contacts and users, with filters and details
The object history logs every change to your objects, such as domains, DNS zones, contacts, users and billing transactions, whether the change was made in the dashboard, via the API or by the system. Go to Developer > Object History in the left sidebar.
Columns and filters
The table shows Created On, Action, Object ID and Object Type. Object types are shown with their technical names, for example DomainResponse, DnsZoneResponse, BillingTransactionResponse or UserWithAttributes.
You can filter by Created On, Action, Object ID, Object Type, Performed By Type (User, Organization or System), Performed By ID and Log ID. To see the full history of one domain, for example, filter by its object ID.
Actions
- Lifecycle: Created, Updated, Deleted, Imported, Synced After Import, Synced, Renewed, Restored, Deactivated, Reactivated.
- Incoming transfers: Transfer Started, Transfer Completed, Transfer Cancelled, Transfer Failed.
- Outgoing transfers: Transfer Out Started, Transfer Out Completed, Transfer Out Cancelled, Transfer Out Failed, Transfer Out Rejected.
- Billing: Billing Transaction Reserved, Billing Transaction Succeeded, Billing Transaction Failed, Billing Transaction Cancelled.
Object Log Details
Click the eye icon in a row to open the page Object Log Details. It shows:
- Object Information: Log ID, Action, Object Type and Object ID.
- Performed By Type and Performed By ID: who made the change.
- Created On: when the change happened.
- Details: the data of the object at that point, as JSON.
History of a single domain
For domains, there is also a timeline on the domain itself: open the domain under Domains > All Domains and go to the tab History. The timeline view is only available for domains.
Related pages
- The API calls themselves are listed in the request history. See Reading API Request History.
- System events such as renewals, transfers and verifications are listed under Developer > Events, where you can acknowledge them. See Monitoring and Acknowledging Events.
