https://wiki.webhosting24.com/index.php?action=history&feed=atom&title=API_RDE 2026-11-14T13:30:04Z Revision history for this page on the wiki MediaWiki 1.42.7 https://wiki.webhosting24.com/index.php?title=API_RDE&diff=4585&oldid=prev 2025-03-14T10:56:33Z

<p>1 revision imported</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <tr class="diff-title" lang="en"> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 11:56, 14 March 2025</td> </tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div> </td></tr></table>

Sro7xw https://wiki.webhosting24.com/index.php?title=API_RDE&diff=4584&oldid=prev 2025-01-01T12:00:00Z

<p>Imported from old wiki</p> <p><b>New page</b></p><div>{{Sidebar}}__NOTOC__<br /> == Overview == <br /> <br /> === WHY IS THE RDE PROGRAM BEING IMPLEMENTED? ===<br /> <br /> If a problem ever occurs with an ICANN-accredited registrar, ICANN needs to know that a copy of the domain name registration information held by that registrar is protected. There are cases, such as if a registrar’s ICANN-accredited status is terminated, that ICANN may have to step in and take measures to transfer those domain names to another registrar. With this data in an escrow account held by a neutral third party, the domain name information is protected and secured.<br /> <br /> === HEXONET&#039;s RegistrarOC and RDE ===<br /> <br /> HEXONET can optionally handle the complete RDE transmission with IronMountain for all registrar account managed by RegistrarOC.<br /> <br /> === ICANN RDE specification ===<br /> <br /> {{Template:Pdf|RDE-specs.pdf| Registrar Data Escrow Specifications}}<br /> <br /> <br /> == HEXONET&#039;s RDE transmission to IronMountain ==<br /> <br /> ==== Domain Data File ====<br /> <br /> The domain data file is generated as described in the RDE specification in chapter 4.1.2.<br /> The syntax of the CSV file is as followed:<br /> <br /> domain,expiration_date,nameservers,holder_contact,admin_contact,tech_contact,billing_contact<br /> hexonet.com,2009-08-29 00:00:00,ns1.hexonet.net ns2.hexonet.net ns3.hexonet.net,P-ABC123,P-ABC123,P-ABC123,P-ABC123<br /> hexonet.net,2009-08-29 00:00:00,ns1.hexonet.com ns2.hexonet.com ns3.hexonet.com,P-ABC456,P-ABC456,P-ABC456,P-ABC456<br /> ...<br /> <br /> ==== Contact Data File ====<br /> <br /> HEXONET is using its own (meta) contact handles. That&#039;s why the contact data is transmitted as own data file as proposed in the RDE specification in chapter 4.1.9. <br /> The syntax of the CSV file is as followed:<br /> <br /> contact,name,organization,street,city,state,zip,country,phone,fax<br /> P-ABC123,Max Mustermann,Testorganization,Teststreet 1,Testcity,Teststate,11111,DE,+4901111112,+4901111113<br /> P-ABC456,Michael Mustermann,Testorganization Ltd.,Teststreet 1,Testcity,Teststate,22222,DE,+4901111114,+4901111115<br /> ...<br /> <br /> ==== Hash Data File ====<br /> <br /> There is Hash Data File with two entries: one for the Domain Data File and one for the Contact Data File.<br /> Details can be found in the RDE specification in chapter 4.1.18.<br /> <br /> An example for the content of such a Hash Data File is below:<br /> <br /> 899ea7ca78a225c122440eac3934af56a04c88a5f1ae27178f2353fc6cb8a685 000_RDE_2008-01-01_full_0<br /> 8dbd2f7ef8b1ee672c67ec23f63cvc44b9e01a09b0540fc15ed4c87b257b9cf0 000_RDE_2008-01-01_hdl_0</div>

local>ImportBot