Purging of unlinked contact objects

Purging of Unused Contact Objects

In order to comply with data protection legislation, CentralNic purges unused contact objects from the registry database. When a domain is updated to remove a contact, and that contact loses the “linked” status, then it will gain the “pendingDelete” status, and then will later be deleted from the database.

Registrars can opt-out of this system on the Account Settings page of the Registrar Console.

Restoring Contacts on Pending Delete

Registrars can “restore” a contact object that is scheduled for deletion by submitting a “no-op” <contact:update> EPP command. An example of such a command is below.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<update>
<contact:update
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
<contact:id>sh8013</contact:id>
<contact:chg />
</contact:update>
</update>
<clTRID>ABC-12345</clTRID>
</command>
</epp>

 

When the server receives this command, the pendingDelete status is removed from the contact object and it will not be deleted. However, the object may still be deleted in future if it is not linked to a domain name once restored.

Was this article helpful?
0 out of 0 found this helpful