RSVP - Revision history

WikiAdmin at 10:24, 22 February 2023

2023-02-22T10:24:40Z

WikiAdmin at 09:12, 22 February 2023

2023-02-22T09:12:00Z

WikiAdmin: Created page with "{{Infobox nTLD | name = .RSVP | image =250px

| introduced = 2022 | category = Social | registry = Charleston Road Registry | idn capable = Yes..."

2023-02-22T09:10:38Z

Created page with "{{Infobox nTLD | name = .RSVP | image =250px | introduced = 2022 | category = Social | registry = Charleston Road Registry | idn capable = Yes..."

New page

{{Infobox nTLD
| name = .RSVP
| image =[[File:Dev-logo.png|250px]] 
| introduced = 2022
| category = Social
| registry = Charleston Road Registry
| idn capable = Yes
| webpage = [https://www.hexonet.net/ Register .RSVP]
| legal = [ Registry Policies]
}}
{{#repositoryinfo: CRR-LIVE-1API | rsvp }}
{{Sidebar}}
<div style="font-size: 250%;">'''.RSVP'''</div> 

.rsvp is a secure domain for events and reservations. Whether you're celebrating a wedding, throwing a fundraiser, or accepting bookings for your business, register a memorable domain on .rsvp that helps guests confirm their plans with you.

.RSVP Security Requirements

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

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

.rsvp 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 .dev must be aware of this security requirement, including that:
* .rsvp 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

Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.

__TOC__

= Registry =
{{Summarybox
| TLD={{#IfEmpty: {{#var:TLD}} | {{#var:TLD}} | - }}
| Registry={{#IfEmpty: {{#var:REGISTRYURL}} | [{{#var:REGISTRYURL}} {{#var:REGISTRYURLNAME}}] | - }}
| Dispute Policy={{#IfEmpty: {{#var:REGISTRYDISPUTEPOLICY}} | [{{#var:REGISTRYDISPUTEPOLICY}} Rules] | - }}
| Registrar={{#var:REGISTRAR}}
| WHOIS-Server={{#var:REGISTRYWHOISSERVER}}
| WHOIS-Update={{#var:REGISTRYWHOISUPDATE}}
| IDN capable={{#var:REGISTRYIDNCAPABLE}}
| Restore capable={{#var:RESTOREPOLICY}}
| Handle Updates={{#var:REGISTRYHANDLEUPDATE}}
| Registration System={{#var:REGISTRYREGISTRATIONSYSTEM}}
| Min. Characters={{#var:REGISTRYCHARSMIN}}
| Max. Characters={{#var:REGISTRYCHARSMAX}}
| Charset={{#var:REGISTRYDOMAINNAMECHARSET}}
| Limitations={{#var:CONTACTSLIMITATIONSENTENCE}}
| Transferclass={{#var:REGISTRYTRANSFERCLASS}}
| Transfer Period={{#var:ZONETRANSFERPERIODS}}
| Transfer Authcode required={{#var:REGISTRYTRANSFERREQUIREAUTHCODE}} {{#var:REGISTRYTRANSFERREQUIREAUTHCODEADDITION}}
| Transfer ACK by={{#var:REGISTRYTRANSFERACKBY}}
| Transfer NACK by={{#var:REGISTRYTRANSFERNACKBY}}
| Transfer Real-Time={{#var:REGISTRYTRANSFERREALTIME}}
| Transfer Lock={{#var:REGISTRYTRANSFERLOCK}}
| Transfer Pending Period={{#var:REGISTRYTRANSFERPENDINGPERIOD}}
| Transfer Expire Action={{#var:REGISTRYTRANSFEREXPIREACTION}}
| Transfer Confirmation={{#var:ZONEPOLICYDOMAINTRANSFERCONFIRMATION}}
| Transfer included={{#var:REGISTRYTRADETRANSFERINCLUDED}}
| Owner Change by={{#var:ZONEPOLICYREGISTRANTNAMECHANGEBY}}
| Trade Period={{#var:ZONETRADEPERIODS}}
| Trade Real-Time={{#var:REGISTRYTRADEREALTIME}}
| Trade Confirmation={{#var:ZONEPOLICYDOMAINTRADECONFIRMATION}}
| Trade ACK by={{#var:REGISTRYTRADEACKBY}}
| Trade NACK by={{#var:REGISTRYTRADENACKBY}}
| Nameservers={{#var:NAMESERVERMIN}} to {{#var:NAMESERVERMAX}}
| Nameserverchecks={{#var:REGISTRYNAMESERVERCHECKS}}
| Host IP-Adresses Type={{#var:HOSTIPADDRESSESTYPE}}
| Hosts managed as={{#var:HOSTMANAGEDAS}}
| Root DNS Update={{#var:REGISTRYNAMESERVERROOTUPDATE}}
| SEC DNS Interface={{#var:ZONESECDNSINTERFACE}}
}}

= Periods =
{{Summarybox
| Registration Period={{#var:ZONEREGISTRATIONPERIODS}}
| Add Grace Period={{#var:ZONEREGISTRATIONGRACEPERIOD}}
| Finalization Period={{#var:ZONERENEWALFINALIZATIONPERIOD}}
| Failure Period={{#var:ZONERENEWALFAILUREPERIOD}}
| Accounting Period={{#var:ZONERENEWALACCOUNTINGPERIOD}}
| Payment Period={{#var:ZONERENEWALPAYMENTPERIOD}}
| Deletion Restorable Period={{#var:DELETIONRESTORABLEPERIOD}}
| Deletion Hold Period={{#var:DELETIONHOLDPERIOD}}
| Explicit Renewal={{#var:REGISTRYEXPLICITRENEWAL}}
| Renewal Period={{#var:ZONERENEWALPERIODS}}
}}

= API =

=== Domain Registration ===
{{#var:REGISTRATIONSENTENCE}}
{{#var:ADDDOMAINCOMMAND}}
REQUIRED
<pre>
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
</pre>

OPTIONAL
<pre>
auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)
</pre>

=== Domain Transfer ===
{{#var:TRANSFERSENTENCE}}
{{#var:TRANSFERDOMAINCOMMAND}}
REQUIRED
<pre>
auth = (TEXT)
</pre>

OPTIONAL
<pre>
period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
</pre>

=== Delete Domain ===
{{#var:DELETESENTENCE}}
{{#var:DELETEDOMAINCOMMAND}}

=== Restore Domain ===
{{#var:RESTOREPOLICYSENTENCE}}
{{#var:RESTOREDOMAINCOMMAND}}

OPTIONAL
<pre>
subuser = (TEXT)
renewalmode = (NULL) | (TEXT)
</pre>

=== Ownerchange ===
{{#var:TRADESENTENCE}}
<pre>
command = ModifyDomain
domain = (DOMAIN)
</pre>

REQUIRED
<pre>
ownercontact0 = (CONTACT)
</pre>

= TLD specific =

=== .Dev 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.

Important: Please note that upon registration, registrants of .dev must be aware of the security requirement outlined above, including that:
* .dev 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

Additionally, registrants must be provided with resources about configuring HTTPS and obtaining an SSL certificate for their domain.

=== 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: 
<pre>
command = ModifyDomain
domain = (DOMAIN)
</pre>

REQUIRED
<pre>
generaterandomauth = 1
</pre>

= Addons =

{{#var:DOMAINADDONTABLE}}

= RegistrarOC =

{{#var:REGISTRAROCSENTENCE}}

{{#var:CATEGORY}}

@@ Line 17: / Line 17: @@
 <b>.RSVP Security Requirements</b>
-.rsvp 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.
+.rsvp is a secured namespace, meaning that websites using a .rsvp domain require an SSL certificate to work; .rsvp 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].
@@ Line 23: / Line 23: @@
 .rsvp 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 .rsvp must be aware of this security requirement, including that:
 * .rsvp 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 .rsvp 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.
@@ Line 154: / Line 154: @@
 = TLD specific =
-=== .Dev Security Requirement Additional Information ===
+=== .RSVP 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 .rsvp 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 .rsvp 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 .rsvp must be aware of the security requirement outlined above, including that:
-* .dev is a secure namespace, and
+* .rsvp 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 .rsvp 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.

@@ Line 1: / Line 1: @@
 {{Infobox nTLD
 | name = .RSVP
-| image    =[[File:Dev-logo.png|250px]]<br><br>
+| image    =[[File:Rsvp-logo.png|250px]]<br><br>
 | introduced = 2022
 | category = Social

RSVP - Revision history

WikiAdmin at 10:24, 22 February 2023

WikiAdmin at 09:12, 22 February 2023

WikiAdmin: Created page with "{{Infobox nTLD | name = .RSVP | image =250px | introduced = 2022 | category = Social | registry = Charleston Road Registry | idn capable = Yes..."

WikiAdmin: Created page with "{{Infobox nTLD | name = .RSVP | image =250px

| introduced = 2022 | category = Social | registry = Charleston Road Registry | idn capable = Yes..."