Date: Fri, 29 Mar 2024 12:18:42 +0100 (CET) Message-ID: <671533004.3929.1711711122901@de.help.internetx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3928_1488941743.1711711122898" ------=_Part_3928_1488941743.1711711122898 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Deletes the given domain at the registry. Domain deletion requests are c= arried out with a time delay and therefore you will always receive "command= completed; action pending", as well as the deletion&= nbsp;date in the domain extensi= ons as a response.
Note
If a domain deletion is to take place shortly before the domain expirati= on date (2 days), it will be deleted on the domain expire date instead.
Request without defined deletion date
<epp x= mlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <command> <delete> <domain:delete xmlns:domain=3D"urn:ietf:params:xml:ns:domain= -1.0"> <domain:name>example.com</domain:name> </domain:delete> </delete> <clTRID>ABC-12345</clTRID> </command> </epp>
Request with defined deletion date
<epp x= mlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <command> <delete> <domain:delete xmlns:domain=3D"urn:ietf:params:xml:ns:domain= -1.0"> <domain:name>example.com</domain:name> </domain:delete> </delete> =09=09<extension> <domainrobot:domain xmlns:domainrobot=3D"urn:org:domainrobot= :ns:ext-1.0"> <domainrobot:deletion>2017-05-22T12:47:12.000Z</do= mainrobot:deletion> </domainrobot:domain> </extension> =09=09<clTRID>ABC-12345</clTRID> </command> </epp>
<epp x= mlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <response> <result code=3D"1001"> <msg lang=3D"en">Command completed successfully; action p= ending</msg> </result> <extension> <domainrobot:domain xmlns:domainrobot=3D"urn:org:domainrobot= :ns:ext-1.0"> <domainrobot:deletion>2018-05-22T12:47:12.000Z</do= mainrobot:deletion> </domainrobot:domain> </extension> <trID> <clTRID>ABC-12345</clTRID> </trID> </response> </epp>