Latest revision as of 15:19, 1 April 2022

.PRO

A .PRO domain name is the top-level domain created for professionals operated by RegistryPro. A .PRO domain name can be used by any professional that services the public in all fields including legal, medical, accounting, engineering, sports, art, and more!

[edit] Registry

Introduced	2004
TLD Type	Generic
Category	Professions
Registry	Registry Pro
IDN Capable	No
Webpage	Register .PRO

TLD	.pro
Allowed TLDs	.pro, med.pro, law.pro, bar.pro, jur.pro, cpa.pro, aca.pro, eng.pro, aaa.pro, acct.pro, avocat.pro, recht.pro
Registry	Donuts Inc.
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.donuts.co
WHOIS-Update	Real-Time
Min. Characters	1
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 13
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object

SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer Pending Period	5 days
Transfer Expire Action	ACK
Transfer ACK by	Registrar
Transfer NACK by	Registrar
Transfer Lock	Yes

Owner Change by	ICANN-TRADE

[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)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <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 Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

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> | <NULL>
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

OPTIONAL

order = CREATE | REPLACE | UPDATE
subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

[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)

OPTIONAL

domainalerttriggercode = <TEXT> | <NULL>
repository = <TEXT> | <NULL>

[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

renewalmode = <NULL> | <TEXT>
subuser = <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>

[edit] TLD specific

[edit] Domain Limitations and Requirements (DEPRECATED - .PRO is now UNRESTRICTED)

All .PRO related X-FLAGS are deprecated. .PRO became UNRESTRICTED on November 16, 2015

X-PRO-PROFESSION: (deprecated) The stated profession of the Registrant
X-PRO-AUTHORITY: (deprecated) The name of the Authority that the Registrant receives their professional credential from
X-PRO-AUTHORITYWEBSITE: (deprecated) Website of the Authority, preferably a member search/directory
X-PRO-LICENSENUMBER: (deprecated) The license number of the Registrant's Credential
X-PRO-ACCEPT-TOU: (deprecated) http://www.registry.pro/legal/user-terms

You have to specify at least 2 nameservers for a .PRO domain to become active.

[edit] Addons

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Addon Class	Parameter to (de)activate *1)	Renewal term *2)	Affected Parameters *3)
Proxy (SHIELDWHOIS_DONUTS_NAMEISP)	X-PROXY = 0 \| SHIELDWHOIS	1 month	All Contacts

*1) Parameter to (de)activate: When accessing our backend through the API, you can either activate the addon with X-PROXY=SHIELDWHOIS or deactivate it with
X-PROXY=0

*2) Renewal Term: Is the minimum renewal term of the "Addon Class"

*3) If you are using a "Proxy" Domain Addon normally all contact handles are affected (registrant, admin, tech, and billing contact).

[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.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.

[edit] RegistrarOC specific parameters

As the owner of a .PRO repository you do not have to provide the following extension:

X-PRO-ACCEPT-TOU = 0 | 1 (deprecated)

@@ Line 1: / Line 1: @@
-{{#repositoryinfo:  PRO-LIVE-1API | pro }}
+{{Infobox gTLD
+| name = .PRO
+| image    =[[File:Pro.png|250px]]
+| introduced = 2004
+| tld type = Generic
+| category = Professions
+| registry = Registry Pro
+| idn capable = No
+| webpage = [https://www.hexonet.net/domain-name/pro Register .PRO]
+}}
+{{#repositoryinfo:  DONUTS-LIVE-1API | pro }}
 {{Sidebar}}
+<div style="font-size: 250%;">'''.PRO'''</div><br/>
-{{#var:ABOUTTLD}}
+A .PRO domain name is the top-level domain created for professionals operated by RegistryPro. A .PRO domain name can be used by any professional that services the public in all fields including legal, medical, accounting, engineering, sports, art, and more!
-<br><br>
 = Registry =
 {{Summarybox
 | TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
+| Allowed TLDs={{#IfEmpty: {{#var:ADDTLD}} | {{#var:ADDTLD}} | - }}
 | Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRYURL}} {{#var:REGISTRYURLNAME}}] | - }}
 | Dispute Policy={{#IfEmpty: {{#var:REGISTRYDISPUTEPOLICY}} | [{{#var:REGISTRYDISPUTEPOLICY}} Rules] | - }}
@@ Line 79: / Line 87: @@
 <span class="label label-info">OPTIONAL</span>
 <pre>
-secdns-ds# = <LONGTEXT> | <NULL>
-secdns-key# = <LONGTEXT> | <NULL>
-secdns-maxsiglife = <INT>
 auth = <TEXT> | <NULL>
-host# = <TEXT> | <NULL>
 transferlock = 0 | 1 | <NULL>
 subuser = <TEXT> | <NULL>
-nameserverset = <TEXT> | <NULL>
 </pre>
@@ Line 98: / Line 99: @@
 auth = <TEXT> | <NULL>
 action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
-domainauth = <TEXT>
 </pre>
@@ Line 104: / Line 104: @@
 <pre>
 order = CREATE | REPLACE | UPDATE
-orderid = <INT>
-emaillanguage = <TEXT>
-emailurl = <TEXT>
-emaillanguage = <TEXT>
-emailtac = <TEXT>
-requestentity = <TEXT>
-emailsender = <TEXT> | <NULL>
-emailsubject = <TEXT> | <NULL>
-preconfirmed = <TEXT>
-transferconfirmationemailoverride = <EMAIL> | <NULL>
-nameserver# = <TEXT> | <NULL>
-host# = <TEXT> | <NULL>
 subuser = <TEXT> | <NULL>
 period = <PERIOD>
-x-idn-language = <TEXT> | <NULL>
-ownercontact0 = <CONTACT> | <NULL>
-admincontact0 = <CONTACT> | <NULL>
-techcontact0 = <CONTACT> | <NULL>
-billingcontact0 = <CONTACT> | <NULL>
 transferlock = 0 | 1 | <NULL>
-repository = <NULL> | <TEXT>
 </pre>
@@ Line 134: / Line 112: @@
 {{#var:DELETESENTENCE}}
 {{#var:DELETEDOMAINCOMMAND}}
-<span class="label label-important">REQUIRED</span>
-<pre>
-n/a
-</pre>
 <span class="label label-info">OPTIONAL</span>
@@ Line 144: / Line 118: @@
 repository = <TEXT> | <NULL>
 </pre>
 === Restore Domain ===
 {{#var:RESTOREPOLICYSENTENCE}}
 {{#var:RESTOREDOMAINCOMMAND}}
-<span class="label label-important">REQUIRED</span>
-<pre>
-n/a
-</pre>
 <span class="label label-info">OPTIONAL</span>
 <pre>
-force = 0 | 1 | <NULL>
 renewalmode = <NULL> | <TEXT>
 subuser = <TEXT>
 </pre>
 === Ownerchange ===
@@ Line 166: / Line 133: @@
 = TLD specific =
-=== Domain Limitations and Requirements ===
-{{warnbox | You have to create an A/V record after registering a 2nd or 3rd level resolving .PRO domain. We automatically request the URL that you need in order to complete your A/V record on the registry website. As long as you do not complete the data for the A/V record, the domain is inactive and does not resolve. You can access the URL by using the [[API:StatusDomain|StatusDomain]] command. Please note that it might take a few minutes until the registry issues the URL. Furthermore the property X-PRO-INACTIVE indicates whether a domain name is still inactive.}}
+=== Domain Limitations and Requirements ('''DEPRECATED - .PRO is now UNRESTRICTED''') ===
+All .PRO related X-FLAGS are deprecated. .PRO became UNRESTRICTED on November 16, 2015
+'''X-PRO-PROFESSION:''' (deprecated) The stated profession of the Registrant<br>
+'''X-PRO-AUTHORITY:''' (deprecated) The name of the Authority that the Registrant receives their professional credential from<br>
+'''X-PRO-AUTHORITYWEBSITE:''' (deprecated) Website of the Authority, preferably a member search/directory<br>
+'''X-PRO-LICENSENUMBER:''' (deprecated) The license number of the Registrant's Credential<br>
+'''X-PRO-ACCEPT-TOU:''' (deprecated) http://www.registry.pro/legal/user-terms<br>
+<br>
 {{warnbox | You have to specify at least 2 nameservers for a .PRO domain to become active.}}
@@ Line 185: / Line 161: @@
 <pre>
-X-PRO-ACCEPT-TOU = 0 | 1 (optional)
+X-PRO-ACCEPT-TOU = 0 | 1 (deprecated)
 </pre>
-==== Completing the A/V data ====
-Besides the possibility that you may request the URL that allows your customer to complete the A/V data at the registry website we can also configure your account to automatically request this URL. Alternatively, you can submit the A/V data using the API specifying '''all''' of the following parameters with the [[API:AddDomainAvRecord|AddDomainAvRecord]] command:
-<pre>
-PROFESSIONTYPE = <TEXT>: identifier for the profession of the license
-JURISDICTIONCOUNTRY = <COUNTRY>: the ISO country code within which the license has been issued
-LICENSEAUTHORITY = <TEXT>: the licensing authority that issued the license (this can be a state or province, or it can be the full name of the licensing authority)
-LICENSENUMBER = <TEXT>: the license number
-LICENSEDATE = <TEXT>: the date the license was issued
-FIRSTNAME = <TEXT>: the first name of the person to which the license was issued
-LASTNAME = <TEXT>: the family name of the person to which the license was issued
-BIRTHDATE = <TEXT>: the date of birth of the professional
-WEBSITE = <TEXT>: the URL of the licensing authority that issued the license
-</pre>
-'''In this case, it is not necessary to do the confirmation using the URL provided in the response.'''
-For the [[API:AddDomainAvRecord|AddDomainAvRecord]] command you can submit additional extensions:
-<pre>
-HOST = <TEXT> (max. 255 chars.)(optional)
-</pre>
-Possible values:
-'''registryTK-registryUI''' - Default value. The registrar will create an A/V object indicating a host type of RegistryTK-RegistryUI and indicating the ContactId of the registrant contact object. (The registrant contact is the link between a domain and an A/V object.)  RegistryPro responds with a URL (containing the identifier of the A/V object) of the RegistryPro hosted A/V site, and the registrar refers the registrant to this site. RegistryPro collects and verifies the A/V data, then activates the domain.
-'''registryTK-registrarUI''' - In the second option, RegistryPro also performs all the checks, but the registrar may provide the user interface for collecting the A/V data. The registrar, first, collects the A/V data directly from the registrant. The registrar, then, creates an A/V object indicating RegistryTK-RegistrarUI and includes the A/V data in the <create> request. Again, when creating the A/V object, the registrar should associate the object with the registrant contact of the domain being registered. There are no retries on professional data; if it doesn’t verify the A/V object is marked final and failed. If the professional verification succeeds, RegistryPro will automatically activate the domain name.
-<pre>
-CHECKTYPE= <TEXT> (max. 255 chars) (optional)
-</pre>
-The check type specifies what A/V data must be collected and verified in an A/V Check. Clients should set this parameter to a value appropriate to the purpose of the A/V object. This parameter currently supports only the following value:
-<headertabs/>

Personal tools

Difference between revisions of "PRO" - HEXONET Wiki

Search

Domains

Services

API & SDK

Modules & Tools

Control Panel & Tools

ICANN Policies

HEXONET & Partners

From HEXONET Wiki

Latest revision as of 15:19, 1 April 2022

Contents

[edit] Registry

[edit] Periods

[edit] API

[edit] Domain Registration

[edit] Domain Transfer

[edit] Delete Domain

[edit] Restore Domain

[edit] Ownerchange

[edit] TLD specific

[edit] Domain Limitations and Requirements (DEPRECATED - .PRO is now UNRESTRICTED)

[edit] Addons

[edit] RegistrarOC

ICANN Whois Data Reminder Policy (WDRP)

ICANN Registrar Data Escrow Program (RDE)

Restore Process

[edit] RegistrarOC specific parameters

	This page was last modified on 1 April 2022, at 15:19. This page has been accessed 61,315 times. Disclaimers
	Mozilla Cavendish Theme based on Cavendish style by Gabriel Wicke modified by DaSch for the Web Community Wiki github Projectpage – Report Bug – Skin-Version: 1.6.4