Revision as of 09:03, 22 February 2023 (view source) WikiAdmin (Talk | contribs) (Created page with "{{Infobox nTLD | name = .BOO | image =250px<br><br> | introduced = 2022 | category = Social | registry = Charleston Road Registry | idn capable = Yes ...")		Latest revision as of 10:22, 22 February 2023 (view source) WikiAdmin (Talk | contribs)
Line 17:		Line 17:
	<b>.BOO Security Requirements</b>		<b>.BOO Security Requirements</b>
−	.boo is a secured namespace, meaning that websites using a .dev domain require an SSL certificate to work; .dev websites can only be accessed by web browsers using HTTPS through an encrypted and secured connection.	+	.boo is a secured namespace, meaning that websites using a .boo domain require an SSL certificate to work; .boo websites can only be accessed by web browsers using HTTPS through an encrypted and secured connection.
	SSL certificates may be purchased through the HEXONET Control Panel or via API. More information on SSL certificates, including purchasing and obtaining certificates and API documentation, may be found [https://wiki.hexonet.net/wiki/SSL here].		SSL certificates may be purchased through the HEXONET Control Panel or via API. More information on SSL certificates, including purchasing and obtaining certificates and API documentation, may be found [https://wiki.hexonet.net/wiki/SSL here].
Line 23:		Line 23:
	.boo domain names that do not have an SSL certificate configured may still be used for email and other non-browser based uses.		.boo domain names that do not have an SSL certificate configured may still be used for email and other non-browser based uses.
−	<b>Important:</b> Please note that upon registration, registrants of .dev must be aware of this security requirement, including that:	+	<b>Important:</b> Please note that upon registration, registrants of .boo must be aware of this security requirement, including that:
	* .boo is a secure namespace, and		* .boo is a secure namespace, and
−	* HTTPS is required for all .dev websites, as they will be encrypted by default and will not allow insecure connections	+	* HTTPS is required for all .boo 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.		Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.
Line 154:		Line 154:
	= TLD specific =		= TLD specific =
−	=== .Dev Security Requirement Additional Information ===	+	=== .BOO Security Requirement Additional Information ===
−	Google Registry has added .dev to the [https://hstspreload.org/ 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 .dev domain to function in browsers.	+	Google Registry has added .boo to the [https://hstspreload.org/ 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 .boo domain to function in browsers.
−	<b>Important:</b> Please note that upon registration, registrants of .dev must be aware of the security requirement outlined above, including that:	+	<b>Important:</b> Please note that upon registration, registrants of .boo must be aware of the security requirement outlined above, including that:
−	* .dev is a secure namespace, and	+	* .boo is a secure namespace, and
−	* HTTPS is required for all .dev websites, as they will be encrypted by default and will not allow insecure connections	+	* HTTPS is required for all .boo 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.		Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.

---

Latest revision as of 10:22, 22 February 2023

Whether you’re building a website for love, laughs, or a surprise, .boo is a fun and memorable domain that’s also secure.

.BOO Security Requirements

.boo is a secured namespace, meaning that websites using a .boo domain require an SSL certificate to work; .boo websites can only be accessed by web browsers using HTTPS through an encrypted and secured connection.

SSL certificates may be purchased through the HEXONET Control Panel or via API. More information on SSL certificates, including purchasing and obtaining certificates and API documentation, may be found here.

.boo domain names that do not have an SSL certificate configured may still be used for email and other non-browser based uses.

Important: Please note that upon registration, registrants of .boo must be aware of this security requirement, including that:

• .boo is a secure namespace, and
• HTTPS is required for all .boo 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.

.BOO
Overview
Introduced	2022
Category	Social
Registry	Charleston Road Registry
IDN Capable	Yes
Dispute Policy	ICANN Rules
Webpage	Register .BOO
Legal Information
Legal	[ Registry 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 .BOO Security Requirement Additional Information 4.2 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	Charleston Road Registry
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	www.registry.google
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: 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	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
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	0 days
Finalization Period	35 days
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.

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>

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

[edit] .BOO Security Requirement Additional Information

Google Registry has added .boo 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 .boo domain to function in browsers.

Important: Please note that upon registration, registrants of .boo must be aware of the security requirement outlined above, including that:

• .boo is a secure namespace, and
• HTTPS is required for all .boo 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.

[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] 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 (WHOISTRUSTEE_CRR)	X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1	1 month	All Contacts

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