From HEXONET Wiki
(16 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | {{Sidebar}} | + | {{Sidebar}} |
+ | |||
+ | <div style="font-size: 160%;">EPP Gateway</div> | ||
+ | |||
HEXONET offers a domain-robot via a real EPP 1.0 (Extensible Provisioning Protocol) strict to RFC 4930-4933. EPP is the recommended RFC 4930-4933 communication-protocol between Domain-Registars and the respective Registries. | HEXONET offers a domain-robot via a real EPP 1.0 (Extensible Provisioning Protocol) strict to RFC 4930-4933. EPP is the recommended RFC 4930-4933 communication-protocol between Domain-Registars and the respective Registries. | ||
With this EPP Implementation you now have access to more than 200 different TLDs through one single protocol. In the event that you hold different own accreditations then you now also have the possibility of managing your accreditation through RegistrarOC and connect to them through EPP. | With this EPP Implementation you now have access to more than 200 different TLDs through one single protocol. In the event that you hold different own accreditations then you now also have the possibility of managing your accreditation through RegistrarOC and connect to them through EPP. | ||
− | + | __TOC__ | |
− | + | ||
− | + | ||
− | |||
− | {| class=" | + | ==EPP Gateway Document: Downloads== |
+ | '''Download EPP Manual:''' {{Template:Pdf|epp_manual.pdf | EPP Manual}} with further information and EPP examples.<br> | ||
+ | |||
+ | |||
+ | ==EPP Gateway Demonstration== | ||
+ | See also: [[NetDri|EPP access using the Net::DRI perl library]]<br> | ||
+ | We also provide an [https://www.hexonet.net/de/software/epp-gateway-live-test EPP Demonstrator] where you can easily execute EPP commands in our OT&E environment. | ||
+ | |||
+ | |||
+ | ==EPP Gateway Command: Online Document== | ||
+ | *[[EPP examples|EPP examples and Commands]] | ||
+ | |||
+ | |||
+ | ==EPP Gateway Information== | ||
+ | |||
+ | {| class="tablehexonet-striped" | ||
|- | |- | ||
− | ! | + | ! !! EPP production environment !! EPP Testbed / OTE |
|- | |- | ||
| Socket: || epp.ispapi.net:700 || epp.ispapi.net:1700 | | Socket: || epp.ispapi.net:700 || epp.ispapi.net:1700 | ||
Line 20: | Line 35: | ||
| Password: || Your Password || Your Password | | Password: || Your Password || Your Password | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 18:25, 28 March 2014
HEXONET offers a domain-robot via a real EPP 1.0 (Extensible Provisioning Protocol) strict to RFC 4930-4933. EPP is the recommended RFC 4930-4933 communication-protocol between Domain-Registars and the respective Registries. With this EPP Implementation you now have access to more than 200 different TLDs through one single protocol. In the event that you hold different own accreditations then you now also have the possibility of managing your accreditation through RegistrarOC and connect to them through EPP.
Contents |
[edit] EPP Gateway Document: Downloads
Download EPP Manual: EPP Manual with further information and EPP examples.
[edit] EPP Gateway Demonstration
See also: EPP access using the Net::DRI perl library
We also provide an EPP Demonstrator where you can easily execute EPP commands in our OT&E environment.
[edit] EPP Gateway Command: Online Document
[edit] EPP Gateway Information
EPP production environment | EPP Testbed / OTE | |
---|---|---|
Socket: | epp.ispapi.net:700 | epp.ispapi.net:1700 |
Login: | Your Username | Your Username |
Password: | Your Password | Your Password |