From HEXONET Wiki
| Line 9: | Line 9: | ||
<h2>EPP Gateway Information</h2> | <h2>EPP Gateway Information</h2> | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | ! Überschrift !! EPP production environmen !! EPP Testbed / OTE | ||
| + | |- | ||
| + | | Socket: || epp.ispapi.net:700 || epp.ispapi.net:1700 | ||
| + | |- | ||
| + | | Login: || Your Username || Your Username | ||
| + | |- | ||
| + | | Password: || Your Password || Your Password | ||
| + | |} | ||
| + | |||
<b>EPP production environment:</b><br> | <b>EPP production environment:</b><br> | ||
Revision as of 07:43, 10 September 2012
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.
We also provide an EPP Demonstrator where you can easily execute EPP commands in our OT&E environment.
EPP Gateway Information
| Überschrift | EPP production environmen | EPP Testbed / OTE |
|---|---|---|
| Socket: | epp.ispapi.net:700 | epp.ispapi.net:1700 |
| Login: | Your Username | Your Username |
| Password: | Your Password | Your Password |
EPP production environment:
Socket: epp.ispapi.net:700
Login: Your Username
Password: Your Password
EPP Testbed / OTE:
Socket: epp.ispapi.net:1700
Login: Your Username
Password: Your Password
