From HEXONET Wiki
(5 intermediate revisions by one user not shown) | |||
Line 9: | Line 9: | ||
| legal = [https://policies.google.com/terms Registry Policies] | | legal = [https://policies.google.com/terms Registry Policies] | ||
}} | }} | ||
− | {{#repositoryinfo: | + | {{#repositoryinfo: RRPPROXY-LIVE-1API | new }} |
{{Sidebar}} | {{Sidebar}} | ||
<div style="font-size: 250%;">'''.NEW'''</div><br/> | <div style="font-size: 250%;">'''.NEW'''</div><br/> | ||
Line 87: | Line 87: | ||
nameserver1 = (NAMESERVER) | nameserver1 = (NAMESERVER) | ||
− | |||
</pre> | </pre> | ||
Line 160: | Line 159: | ||
generaterandomauth = 1 | generaterandomauth = 1 | ||
</pre> | </pre> | ||
− | |||
− | |||
=== .NEW Security Requirement Additional Information === | === .NEW Security Requirement Additional Information === | ||
Line 172: | Line 169: | ||
Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain. | Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain. | ||
+ | |||
+ | Registrants must explicitly acknowledge this security requirement using the following parameter: | ||
+ | <pre> | ||
+ | X-ACCEPT-SSL-REQUIREMENT = 1 | ||
+ | </pre> | ||
= RegistrarOC = | = RegistrarOC = |
Latest revision as of 06:25, 22 June 2023
.NEW | |
250px | |
Overview | |
Introduced | 2019 |
---|---|
Category | Technology |
Registry | Google Registry |
IDN Capable | Yes |
Dispute Policy | ICANN Rules |
Webpage | Register .NEW |
Legal Information | |
Legal | Registry Policies |
Contents |
[edit] Registry
TLD |
- |
Registry | |
Dispute Policy | |
Registrar |
1api GmbH |
WHOIS-Server |
whois.centralnic.net |
WHOIS-Update |
Real-Time |
Min. Characters |
1 |
Max. Characters |
63 |
Character Set |
|
Limitations |
|
IDN capable |
Yes |
Restore capable |
Real-Time |
Handle Updates |
Supported |
Registration System |
Real-Time |
Allowed number of NS |
0 to 10 |
Registry Nameservercheck |
No |
Host IP-Addresses Type |
IPv4 / IPv6 |
Hosts managed as |
Object |
Root Nameserver Update |
every 15min |
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
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) 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 Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.
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>
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 domain:
- Minimum 8 characters
- having at least one (1) numeric,
- one (1) alphabetic, and
- one (1) special character
You may generate a valid random auth code by adding this parameter to the ModifyDomain command:
command = ModifyDomain domain = (DOMAIN)
REQUIRED
generaterandomauth = 1
[edit] .NEW Security Requirement Additional Information
Google Registry has added .new to the HSTS preload list, which means that all websites using this TLD will be encrypted by default and will not allow insecure connections. Registrants must configure HTTPS serving for their domains in order for them to work in all major browsers. That is, they need to configure an SSL certificate in order for their .new domain to function in browsers.
Important: Please note that upon registration, registrants of .new must be aware of the security requirement outlined above, including that:
- .new is a secure namespace, and
- HTTPS is required for all .new websites, as they will be encrypted by default and will not allow insecure connections
Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.
Registrants must explicitly acknowledge this security requirement using the following parameter:
X-ACCEPT-SSL-REQUIREMENT = 1