EPP Index - Revision history

WikiSysop at 08:39, 10 November 2025

WikiSysop — Mon, 10 Nov 2025 08:39:12 GMT

← Older revision		Revision as of 08:39, 10 November 2025
Line 32:		Line 32:

	===EPP server===		===EPP server===
-	* hostname: https://epp.openprovider.eu (epp.sandbox.openprovider.nl for Sandbox EPP)	+	* hostname: https://epp.openprovider.eu (https://epp.sandbox.openprovider.nl for Sandbox EPP)
	* port: 443		* port: 443
	* username: similar to RCP username		* username: similar to RCP username

WikiSysop at 08:37, 10 November 2025

WikiSysop — Mon, 10 Nov 2025 08:37:40 GMT

← Older revision		Revision as of 08:37, 10 November 2025
Line 32:		Line 32:

	===EPP server===		===EPP server===
-	* hostname: https://epp.openprovider.eu	+	* hostname: https://epp.openprovider.eu (epp.sandbox.openprovider.nl for Sandbox EPP)
	* port: 443		* port: 443
	* username: similar to RCP username		* username: similar to RCP username

WikiSysop: /* EPP server */

WikiSysop — Thu, 26 Jun 2025 19:27:11 GMT

EPP server

← Older revision		Revision as of 19:27, 26 June 2025
Line 35:		Line 35:
	* port: 443		* port: 443
	* username: similar to RCP username		* username: similar to RCP username
-	** ''Note: EPP defines a maximum length of 16 characters for the username. If your RCP username is longer, please contact ~~our support team to change it to~~ a ~~shorter one~~.''	+	** ''Note: EPP defines a maximum length of 16 characters for the username. If your RCP username is longer, please create a new technical contact and specify a username (example: "myeppuser") with maximum length of 16 characters (Tech contact username doesn't need to be an email address).''
	* password: similar to RCP password		* password: similar to RCP password

WikiSysop at 08:03, 27 September 2017

WikiSysop — Wed, 27 Sep 2017 08:03:44 GMT

← Older revision		Revision as of 08:03, 27 September 2017
Line 35:		Line 35:
	* port: 443		* port: 443
	* username: similar to RCP username		* username: similar to RCP username
		+	** ''Note: EPP defines a maximum length of 16 characters for the username. If your RCP username is longer, please contact our support team to change it to a shorter one.''
	* password: similar to RCP password		* password: similar to RCP password

WikiSysop at 15:03, 4 June 2015

WikiSysop — Thu, 04 Jun 2015 15:03:01 GMT

WikiSysop at 14:49, 4 June 2015

WikiSysop — Thu, 04 Jun 2015 14:49:46 GMT

← Older revision		Revision as of 14:49, 4 June 2015
Line 895:		Line 895:
	</epp>		</epp>

-	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''~~int~~''	+	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''
	* '''<contact:id>''' is ignored by Openprovider		* '''<contact:id>''' is ignored by Openprovider
	* '''<contact:pw>''' is ignored by Openprovider		* '''<contact:pw>''' is ignored by Openprovider
Line 1,091:		Line 1,091:
	</epp>		</epp>

-	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''~~int~~''	+	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''
	* '''<contact:status>''' and it's attributes are ignored by Openprovider		* '''<contact:status>''' and it's attributes are ignored by Openprovider
	* '''<contact:pw>''' is ignored by Openprovider but required by EPP protocol, leave it blank		* '''<contact:pw>''' is ignored by Openprovider but required by EPP protocol, leave it blank

WikiSysop: /* Update */

WikiSysop — Fri, 06 Jun 2014 08:16:14 GMT

Update

← Older revision		Revision as of 08:16, 6 June 2014
Line 1,044:		Line 1,044:
	<contact:id>IB000545-NL</contact:id>		<contact:id>IB000545-NL</contact:id>
	<contact:chg>		<contact:chg>
-	<contact:postalInfo type="~~int~~">	+	<contact:postalInfo type="loc">
	<contact:org/>		<contact:org/>
	<contact:addr>		<contact:addr>
Line 1,109:		Line 1,109:
	</response>		</response>
	</epp>		</epp>
-

	==Host==		==Host==

WikiSysop: /* Create */

WikiSysop — Fri, 06 Jun 2014 08:15:49 GMT

Create

← Older revision		Revision as of 08:15, 6 June 2014
Line 845:		Line 845:
	<contact:create xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd">		<contact:create xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xsi:schemaLocation="urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd">
	<contact:id>IGNORED</contact:id>		<contact:id>IGNORED</contact:id>
-	<contact:postalInfo type="~~int~~">	+	<contact:postalInfo type="loc">
	<contact:name>John Doe</contact:name>		<contact:name>John Doe</contact:name>
	<contact:org>Example Inc.</contact:org>		<contact:org>Example Inc.</contact:org>
Line 919:		Line 919:
	</response>		</response>
	</epp>		</epp>
-

	===Delete===		===Delete===

WikiSysop at 14:36, 21 May 2014

WikiSysop — Wed, 21 May 2014 14:36:56 GMT

← Older revision		Revision as of 14:36, 21 May 2014
Line 690:		Line 690:

	* '''<contact:pw/> element''' is NOT used but required by EPP protocol, leave it blank		* '''<contact:pw/> element''' is NOT used but required by EPP protocol, leave it blank
		+
		+	===Support for new gTLDs and their launch phases===
		+	;General information
		+	* Openprovider follows the existing RFCs for launch phase support, although there are some small changes because of the registrar situation (instead of registry situation). See examples below.
		+	* The '''domain:check''' can optionally be used to see if trademark claims applies; if so, you know that Openprovider will send a trademark claims notice to the proposed domain holder. The domain:create command is not different for a domain with or without claims.
		+	* The '''domain:create''' command may contain the launch phase, see examples below. The supported launch phases are the following; for exact dates and times per extension, please look at the TLD detail pages on our [https://www.openprovider.co.uk/new-gtlds/overview-new-gtlds/ website]:
		+	** '''<launch:phase>sunrise</launch:phase>''' (base64 encoded SMD file required); accepted during Sunrise
		+	** '''<launch:phase>landrush</launch:phase>'''; accepted during Landrush
		+	** '''<launch:phase>claims</launch:phase>'''; accepted during trademark claims phase
		+	** '''<launch:phase name="preregistration">custom</launch:phase>'''; accepted until 3 hours before General Availability starts
		+
		+	;Example check command+response to check if trademark claims applies
		+	<?xml version="1.0" encoding="UTF-8" standalone="no"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	<command>
		+	<check>
		+	<domain:check xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
		+	<domain:name>trademark.tld</domain:name>
		+	</domain:check>
		+	</check>
		+	'''<extension>
		+	''' <launch:check xmlns:launch="urn:ietf:params:xml:ns:launch-1.0" type="claims">
		+	''' <launch:phase>claims</launch:phase>
		+	''' </launch:check>
		+	'''</extension>
		+	<clTRID>C68D3D5A-2F3C-11DE-8EF9-80000000DC4F</clTRID>
		+	</command>
		+	</epp>
		+
		+	<?xml version="1.0" encoding="UTF-8"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	<response>
		+	<result code="1000">
		+	<msg>Command completed successfully</msg>
		+	</result>
		+	'''<extension>
		+	''' <launch:chkData xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
		+	''' <launch:phase>claims</launch:phase>
		+	''' <launch:cd>
		+	''' <launch:name exists="true">trademark.tld</launch:name>
		+	''' </launch:cd>
		+	''' </launch:chkData>
		+	'''</extension>
		+	<trID>
		+	<clTRID>C68D3D5A-2F3C-11DE-8EF9-80000000DC4F</clTRID>
		+	<svTRID>37080027-DB39-416A-A82E-AF793FB14AE9</svTRID>
		+	</trID>
		+	</response>
		+	</epp>
		+
		+	;Example create command for a Sunrise application
		+	<?xml version="1.0" encoding="UTF-8" standalone="no"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	<command>
		+	<create>
		+	<domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
		+	<domain:name>example.tld</domain:name>
		+	... (other standard domain attributes)
		+	</domain:create>
		+	</create>
		+	'''<extension>
		+	''' <launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
		+	''' <launch:phase>sunrise</launch:phase>
		+	''' <smd:encodedSignedMark xmlns:smd="urn:ietf:params:xml:ns:signedMark-1.0">
		+	''' ... (base64-encoded SMD file)
		+	''' </smd:encodedSignedMark>
		+	''' </launch:create>
		+	<op:ext xmlns:op="http://www.openprovider.nl/epp/xml/opprov-1.0">
		+	<op:create>
		+	<op:domain>
		+	... (optional standard Openprovider extensions)
		+	</op:domain>
		+	</op:create>
		+	</op:ext>
		+	</extension>
		+	<clTRID>3F169D90-411F-11DE-84A7-80000000274B</clTRID>
		+	</command>
		+	</epp>
		+
		+	;Example create extension for Landrush, claims and pre-registration orders
		+	<?xml version="1.0" encoding="UTF-8" standalone="no"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	...
		+	<extension>
		+	<launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
		+	''' <launch:phase>landrush</launch:phase>
		+	</launch:create>
		+	...
		+
		+	<?xml version="1.0" encoding="UTF-8" standalone="no"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	...
		+	<extension>
		+	<launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
		+	''' <launch:phase>claims</launch:phase>
		+	</launch:create>
		+	...
		+
		+	<?xml version="1.0" encoding="UTF-8" standalone="no"?>
		+	<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
		+	...
		+	<extension>
		+	<launch:create xmlns:launch="urn:ietf:params:xml:ns:launch-1.0">
		+	''' <launch:phase name="preregistration">custom</launch:phase>
		+	</launch:create>
		+	...

	==Contact==		==Contact==

WikiSysop at 06:21, 19 April 2014

WikiSysop — Sat, 19 Apr 2014 06:21:00 GMT

← Older revision		Revision as of 06:21, 19 April 2014
Line 29:		Line 29:

	===Example===		===Example===
-	~~Not yet available~~	+	* A basic PHP-example: [[Example Script EPP PHP\|example-epp.php]]

	===EPP server===		===EPP server===

← Older revision		Revision as of 15:03, 4 June 2015
Line 242:		Line 242:
	</epp>		</epp>

-	* ''<domain:pw>'' parameter is required by the EPP protocol, but is ignored by Openprovider	+	* ''<domain:pw>'' parameter is required by the EPP protocol, but is ignored by Openprovider; please leave it blank
	* ''<domain:contact>'': the only supported contact types are ''admin'' and ''tech''		* ''<domain:contact>'': the only supported contact types are ''admin'' and ''tech''
	* ''<op:autorenew>'': accepted values: ''on'', ''off'', ''default''		* ''<op:autorenew>'': accepted values: ''on'', ''off'', ''default''
Line 689:		Line 689:
	</epp>		</epp>

-	* '''<contact:pw/> element''' is NOT used but required by EPP protocol, leave it blank	+	* '''<contact:pw/> element''' is NOT used but required by EPP protocol; please leave it blank

	===Support for new gTLDs and their launch phases===		===Support for new gTLDs and their launch phases===
Line 897:		Line 897:
	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''		* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''
	* '''<contact:id>''' is ignored by Openprovider		* '''<contact:id>''' is ignored by Openprovider
-	* '''<contact:pw>''' is ignored by Openprovider	+	* '''<contact:pw>''' is ignored by Openprovider but required by the EPP protocol; please leave it blank
	* '''<contact:disclose>''' is ignored by Openprovider		* '''<contact:disclose>''' is ignored by Openprovider

Line 1,093:		Line 1,093:
	* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''		* '''<contact:postalInfo>''' ''type'' attribute is restricted to only one value: ''loc''
	* '''<contact:status>''' and it's attributes are ignored by Openprovider		* '''<contact:status>''' and it's attributes are ignored by Openprovider
-	* '''<contact:pw>''' is ignored by Openprovider but required by EPP protocol, leave it blank	+	* '''<contact:pw>''' is ignored by Openprovider but required by EPP protocol; please leave it blank
	* '''<contact:disclose>''' is ignored by Openprovider		* '''<contact:disclose>''' is ignored by Openprovider