Personal tools

From HEXONET Wiki

Jump to: navigation, search
 
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{Infobox nTLD
 
{{Infobox nTLD
 
| name = .KYOTO
 
| name = .KYOTO
| image    =[[File:Logo_kyoto.png|250px]]
+
| image    =[[File:Logo_kyoto.png|200px]]
 
| introduced = 2015
 
| introduced = 2015
 
| category = Geographic
 
| category = Geographic
Line 18: Line 18:
 
= Registrant Eligibility Requirement =
 
= Registrant Eligibility Requirement =
  
# '''Kyoto Physical Address '''.  Registrant must have a a valid physical address in Kyoto Prefecture, Japan.
+
# Kyoto municipalities and local governments;
# '''Proxy Registration'''.  No trustee or proxy services of any kind will be
+
# Public and private institutions with a valid physical address in Kyoto;
 +
# Organizations, companies, and other businesses with a valid physical address in Kyoto; and
 +
# Natural persons with a valid physical address in Kyoto.
 +
# '''Proxy Registration'''.  Trustee or proxy services are not allowed.
  
  

Latest revision as of 15:41, 16 October 2015

.KYOTO


.KYOTO
Logo kyoto.png
Overview
Introduced 2015
Category Geographic
Registry GMO Registry
IDN Capable N/A
Dispute Policy ICANN Rules
Webpage Register .KYOTO
Legal Information
Legal TBA

Contents


[edit] Registrant Eligibility Requirement

  1. Kyoto municipalities and local governments;
  2. Public and private institutions with a valid physical address in Kyoto;
  3. Organizations, companies, and other businesses with a valid physical address in Kyoto; and
  4. Natural persons with a valid physical address in Kyoto.
  5. Proxy Registration. Trustee or proxy services are not allowed.


[edit] Registry

TLD

-

Registry

GMO Registry

Dispute Policy

Rules

Registrar

1api GmbH

WHOIS-Server

whois.gmoregistry.net

WHOIS-Update

Real-Time

Min. Characters

3

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 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)
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 .COM 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

[edit] RegistrarOC

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.