From HEXONET Wiki
(→Domain Limitations and Requirements) |
|||
| Line 1: | Line 1: | ||
| + | {{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: PRO-LIVE-1API | pro }} | {{#repositoryinfo: PRO-LIVE-1API | pro }} | ||
| − | |||
{{Sidebar}} | {{Sidebar}} | ||
| − | + | <div style="font-size: 200%;">'''.PRO'''</div><br/> | |
| − | <br> | + | A .PRO domain name is the first and only restricted top-level domain created exclusively for professionals, approved and regulated by the Internet Corporation for Assigned Names and Numbers (ICANN) and operated by RegistryPro. A .PRO domain name can be used and registered by persons and organizations that are licensed or otherwise authorized by the appropriate government agencies or organizations to provide professional services to the public in the legal, medical, accounting and engineering fields. |
| Line 192: | Line 201: | ||
CHECKTYPE= <TEXT> (max. 255 chars) (optional) | CHECKTYPE= <TEXT> (max. 255 chars) (optional) | ||
</pre> | </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: | + | 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: |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 23:00, 12 March 2014
 |
|
| Introduced | 2004 |
|---|---|
| TLD Type | Generic |
| Category | Professions |
| Registry | Registry Pro |
| IDN Capable | No |
| Webpage | Register .PRO |
Contents |
Registry
| TLD |
- |
| Allowed TLDs |
- |
| Registry |
- |
| Dispute Policy |
- |
| Limitations |
|
| Allowed number of NS |
to |
Periods
API
Domain Registration
Domains can be registered with the API AddDomain command.
command = AddDomain domain = (DOMAIN)
REQUIRED
ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER) x-pro-profession = <PROFESSION> x-pro-accept-tou = 1
OPTIONAL
auth = <TEXT> | <NULL> transferlock = 0 | 1 | <NULL> subuser = <TEXT> | <NULL> x-pro-authority = <AUTHORITY> (optional) x-pro-authoritywebsite = <AUTHORITYWEBSITE> (optional) x-pro-licensenumber =<LICENSENUMBER> (optional)
Domain Transfer
There is a special procedure to handle a domain transfer. Please contact our Support-Team if you should need further information.
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>
Delete Domain
Domains can be deleted with the API DeleteDomain command.
There is no Deletion Restorable Period.
command = DeleteDomain domain = (DOMAIN)
OPTIONAL
domainalerttriggercode = <TEXT> | <NULL> repository = <TEXT> | <NULL>
Restore Domain
command = RestoreDomain domain = (DOMAIN)
OPTIONAL
renewalmode = <NULL> | <TEXT> subuser = <TEXT>
Ownerchange
TLD specific
Domain Limitations and Requirements
X-PRO-PROFESSION: The stated profession of the Registrant
X-PRO-AUTHORITY: The name of the Authority that the Registrant receives their professional credential from
X-PRO-AUTHORITYWEBSITE: Website of the Authority, preferably a member search/directory
X-PRO-LICENSENUMBER: The license number of the Registrant's Credential
X-PRO-ACCEPT-TOU: http://www.registry.pro/legal/user-terms
Addons
RegistrarOC
No special procedures.
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 (optional)
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 AddDomainAvRecord command:
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
In this case, it is not necessary to do the confirmation using the URL provided in the response.
For the AddDomainAvRecord command you can submit additional extensions:
HOST = <TEXT> (max. 255 chars.)(optional)
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.
CHECKTYPE= <TEXT> (max. 255 chars) (optional)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:
