Revision as of 18:10, 27 February 2015 (view source) WikiAdmin (Talk | contribs) ← Older edit		Latest revision as of 19:31, 16 February 2022 (view source) WikiAdmin (Talk | contribs)
(5 intermediate revisions by one user not shown)
Line 7:		Line 7:
	| idn capable = Yes		| idn capable = Yes
	| webpage = [https://www.hexonet.net/preregistrations/paris Register .PARIS]		| webpage = [https://www.hexonet.net/preregistrations/paris Register .PARIS]
−	| legal = [http://bienvenue.paris/wp-content/uploads/2014/09/Registry_Policies_Paris.pdf Registry Policies (English)	+	| legal = [http://bienvenue.paris/wp-content/uploads/2014/09/Registry_Policies_Paris.pdf English Policies]<br />
		+	[http://bienvenue.paris/wp-content/uploads/2014/09/Politiques_d_enregistrement_Paris.pdf French Policies]
	}}		}}
Line 85:		Line 86:
	nameserver0 = (NAMESERVER)		nameserver0 = (NAMESERVER)
	nameserver1 = (NAMESERVER)		nameserver1 = (NAMESERVER)
		+	X-PARIS-ACCEPT-REGISTRATION-TAC = 1
	</pre>		</pre>
Line 142:		Line 144:
	There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:		There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:
−	*Minimum 8 characters	+	*Minimum 12 characters
	*having at least one (1) numeric,		*having at least one (1) numeric,
−	*one (1) alphabetic, and	+	*one (1) alphabetic and
−	*one (1) special character	+	*one (1) capital alphabetic
	You may generate a valid random auth code by adding this parameter to the ModifyDomain command:<br>		You may generate a valid random auth code by adding this parameter to the ModifyDomain command:<br>

---

Latest revision as of 19:31, 16 February 2022

.PARIS
Overview
Introduced	2014
Category	Geographic
Registry	dotParis
IDN Capable	Yes
Dispute Policy	ICANN Rules
Webpage	Register .PARIS
Legal Information
Legal	English Policies French Policies

Contents 1 Registry 2 Periods 3 API 3.1 Domain Registration 3.2 Domain Transfer 3.3 Delete Domain 3.4 Restore Domain 3.5 Ownerchange 4 TLD specific 4.1 Authorization code 5 Addons 6 RegistrarOC 6.1 ICANN Whois Data Reminder Policy (WDRP) 6.2 ICANN Registrar Data Escrow Program (RDE) 6.3 Restore Process

[edit] Registry

TLD	-
Registry	AFNIC
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.afnic.fr
WHOIS-Update	-
Min. Characters	2
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: not allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 1 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	NO
Restore capable	Real-Time
Handle Updates	Supported
Registration System	Real-Time
Allowed number of NS	0 to 8
Registry Nameservercheck	Yes
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
Root Nameserver Update	hourly
SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer ACK by	Registrar
Transfer NACK by	Registry
Transfer Lock	Yes
Owner Change by	ICANN-TRADE
Trade Real-Time	No
Transfer included	Yes
Trade ACK by	Both
Trade NACK by	Customer

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-5 days
Finalization Period	1 day
Failure Period	44 days
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	5 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

[edit] API

[edit] Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
X-PARIS-ACCEPT-REGISTRATION-TAC = 1

OPTIONAL

auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

[edit] Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registry.

Please note that HEXONET is acting in compliance with ICANN Transfer Guidelines. The respective policies can be viewed under http://www.icann.org/transfers/ :

As soon as you have submitted a transfer request, the HEXONET system start the transfer through the official registry and the losing registrar will receive the transfer request. The losing registrar will then send an email to the domain registrant/administrative contact, allowing them to deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

auth = (TEXT)

OPTIONAL

period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

[edit] Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

[edit] Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

subuser = (TEXT)
renewalmode = (NULL) | (TEXT)

[edit] Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>

A Change of Registrar with the simultaneous change in the Registrant is possible. The trade request also includes a transfer request if the domain is currently managed by another registrar.

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

[edit] Authorization code

There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:

• Minimum 12 characters
• having at least one (1) numeric,
• one (1) alphabetic and
• one (1) capital alphabetic

You may generate a valid random auth code by adding this parameter to the ModifyDomain command:

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

generaterandomauth = 1

[edit] Addons

[edit] RegistrarOC

ICANN Whois Data Reminder Policy (WDRP)

At least annually, a registrar must present to the registrant the current Whois information, and remind the registrant that provision of false Whois information can be grounds for cancellation of his domain name registration. Registrants must review their Whois data, and make any corrections.

ICANN Registrar Data Escrow Program (RDE)

Under the data escrow provision of the Registrar Accreditation Agreement (RAA), all ICANN-accredited registrars must regularly deposit a backup copy of their gTLD registration data with ICANN through ICANN's arrangement with Iron Mountain or they may elect to use a Third Party Provider of RDE services that has been approved by ICANN.

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.