gTLD	Full Legal Name	E-mail suffix	Detail
.godaddy	Go Daddy East, LLC	godaddy.com	View

Go Daddy’s Registration Data Directory Service (RDDS) (WHOIS Database Services) will be composed of three services: a WHOIS service available through port 43, a Web-based service providing free public query-based access, and a Web-based service providing registrars query-based access. The services access the same data store, which will be updated in near real time.

To achieve and exceed the performance and reliability requirements as set forth in the Service Level Agreement Matrix (Registry Agreement, Specification 10), Go Daddy systems will be compartmentalized into functional areas. These individual areas will be comprised of hardware load-balanced clusters of N+1 servers. For any component server cluster, there will never be less than 2 servers, but there will be as many servers as necessary to meet Specification 10. Individual servers will be added or removed from the component cluster without negatively impacting normal activities or performance of the system component. The complete RDDS system will be deployed in each data center to provide active⁄passive redundancy. (See Attachment 1 to the answer to Question 32 for a representative network diagram.)

PORT 43 WHOIS SERVICE

Go Daddy will provide a transaction-oriented WHOIS service based on Transmission Control Protocol (TCP), which is compliant with RFC 3912. The service will listen on port 43 for incoming requests from WHOIS clients. All requests will be required to be terminated with Carriage Return Line Feed (CRLF) (\r\n). The service will close the TCP connection after the response is sent to a client.

DOMAIN NAME DATA (SPECIFICATION 4.1.4)

To determine information regarding a specific domain in the Go Daddy WHOIS database, for example, ʺDOMAIN EXAMPLEDOMAIN.GTLDʺ, a user would submit the domain name and the response returned would include, but may not be limited to:

1. Domain ID;

2. Domain data (i.e., last update, expiration date, creation date);

3. Sponsoring Registrar information (IANA ID, name, WHOIS server);

4. Domain Status(es);

5. Name server(s);

6. Contact data;

7. Last update of WHOIS database;

8. DNSSEC information.

REGISTRAR DATA (SPECIFICATION 4.1.5)

To determine information regarding a registrar in the Go Daddy WHOIS database, a user would submit the registrar name and the response returned would include, but may not be limited to:

1. Registrar information (name, create date, last updated date, address);

2. Contact information;

3. WHOIS server;

4. Last update of WHOIS database.

NAMESERVER DATA (SPECIFICATION 4.1.6)

To determine information regarding a host (nameserver) in the Go Daddy WHOIS database, a user would submit the host name or IP address and the response returned would include, but may not be limited to:

1. List of host name(s) or IP address(es);

2. Sponsoring registrar;

3. WHOIS server.

CONTACT DATA

In addition to the Specification 4 requirements, Go Daddy will provide a contact data lookup on its WHOIS database for the gTLD. Response to a contact-based query would include, but may not be limited to:

1. Contact data (i.e., name, address, geographic location, phone and fax number(s), email address(es));

2. Sponsoring registrar;

3. Status(es) (last update date, creation date);

4. WHOIS server;

5. Last update of WHOIS database.

PUBLIC WHOIS SERVICE

The public Web-based WHOIS service will have the same functionality as the port 43 service with the addition of limited wildcard searches for Domain, Registrar and Name-server data. The system will be protected from abuse by the use of CAPTCHA and configurable IP-based WHOIS quotas.

REGISTRAR WHOIS SERVICE

The registrar Web-based WHOIS service will have the same functionality as the public WHOIS service with the addition of an expanded set of wildcard searches. The system will provide unlimited access to authenticated users through the registrar portal website.

All three systems will be designed to provide metrics that will aid in future upgrade decisions, which include the detection of any potential failures, and the detection of any abuses of the system. The systems will be capable of limiting access if the terms of use are violated.

RESOURCING PLAN

Resourcing will come from current staff throughout the parent organization: Software Development, Network Operations, IT, Security Operations, and Business Continuity Departments. Go Daddy will incorporate all new gTLDs added to the Go Daddy registry into existing workflows to obtain immediate workability. Go Daddy has anticipated additional headcount in the coming year for all affected departments. See the headcount estimate in the ʺCASH OUTFLOWSʺ section in Go Daddyʹs answer to Question 46.

gTLD	Full Legal Name	E-mail suffix	Detail
.casa	Go Daddy East, LLC	godaddy.com	View

Go Daddy’s Registration Data Directory Service (RDDS) (WHOIS Database Services) will be composed of three services: a WHOIS service available through port 43, a Web-based service providing free public query-based access, and a Web-based service providing registrars query-based access. The services access the same data store, which will be updated in near real time.

To achieve and exceed the performance and reliability requirements as set forth in the Service Level Agreement Matrix (Registry Agreement, Specification 10), Go Daddy systems will be compartmentalized into functional areas. These individual areas will be comprised of hardware load-balanced clusters of N+1 servers. For any component server cluster, there will never be less than 2 servers, but there will be as many servers as necessary to meet Specification 10. Individual servers will be added or removed from the component cluster without negatively impacting normal activities or performance of the system component. The complete RDDS system will be deployed in each data center to provide active⁄passive redundancy. (See Attachment 1 to the answer to Question 32 for a representative network diagram.)

PORT 43 WHOIS SERVICE

Go Daddy will provide a transaction-oriented WHOIS service based on Transmission Control Protocol (TCP), which is compliant with RFC 3912. The service will listen on port 43 for incoming requests from WHOIS clients. All requests will be required to be terminated with Carriage Return Line Feed (CRLF) (\r\n). The service will close the TCP connection after the response is sent to a client.

DOMAIN NAME DATA (SPECIFICATION 4.1.4)

To determine information regarding a specific domain in the Go Daddy WHOIS database, for example, ʺDOMAIN EXAMPLEDOMAIN.GTLDʺ, a user would submit the domain name and the response returned would include, but may not be limited to:

1. Domain ID;

2. Domain data (i.e., last update, expiration date, creation date);

3. Sponsoring Registrar information (IANA ID, name, WHOIS server);

4. Domain Status(es);

5. Name server(s);

6. Contact data;

7. Last update of WHOIS database;

8. DNSSEC information.

REGISTRAR DATA (SPECIFICATION 4.1.5)

To determine information regarding a registrar in the Go Daddy WHOIS database, a user would submit the registrar name and the response returned would include, but may not be limited to:

1. Registrar information (name, create date, last updated date, address);

2. Contact information;

3. WHOIS server;

4. Last update of WHOIS database.

NAMESERVER DATA (SPECIFICATION 4.1.6)

To determine information regarding a host (nameserver) in the Go Daddy WHOIS database, a user would submit the host name or IP address and the response returned would include, but may not be limited to:

1. List of host name(s) or IP address(es);

2. Sponsoring registrar;

3. WHOIS server.

CONTACT DATA

In addition to the Specification 4 requirements, Go Daddy will provide a contact data lookup on its WHOIS database for the gTLD. Response to a contact-based query would include, but may not be limited to:

1. Contact data (i.e., name, address, geographic location, phone and fax number(s), email address(es));

2. Sponsoring registrar;

3. Status(es) (last update date, creation date);

4. WHOIS server;

5. Last update of WHOIS database.

PUBLIC WHOIS SERVICE

The public Web-based WHOIS service will have the same functionality as the port 43 service with the addition of limited wildcard searches for Domain, Registrar and Name-server data. The system will be protected from abuse by the use of CAPTCHA and configurable IP-based WHOIS quotas.

REGISTRAR WHOIS SERVICE

The registrar Web-based WHOIS service will have the same functionality as the public WHOIS service with the addition of an expanded set of wildcard searches. The system will provide unlimited access to authenticated users through the registrar portal website.

All three systems will be designed to provide metrics that will aid in future upgrade decisions, which include the detection of any potential failures, and the detection of any abuses of the system. The systems will be capable of limiting access if the terms of use are violated.

RESOURCING PLAN

Resourcing will come from current staff throughout the parent organization: Software Development, Network Operations, IT, Security Operations, and Business Continuity Departments. Go Daddy will incorporate all new gTLDs added to the Go Daddy registry into existing workflows to obtain immediate workability. Go Daddy has anticipated additional headcount in the coming year for all affected departments. See the headcount estimate in the ʺCASH OUTFLOWSʺ section in Go Daddyʹs answer to Question 46.