| gTLD | Full Legal Name | E-mail suffix | Detail | | .uol | UBN INTERNET LTDA. | registro.br | View |
1. Description
The Whois service is provided by a NIC.br (Núcleo de Informação e
Coordernação do Ponto BR) implementation. It supports lookup
functionality for domains, user IDs and registrar data.
Service is available via port 43 in accordance with RFC 3912 (Request
For Comments), and as a web-based directory service at
whois.nic.UOL.
2. High availability and performance
To guarantee high availability of the service, it is redundant by
having different instances of the server software running on separate
machines behind a load balancer hardware. The [Q26-diagram1]
illustrates that topology:
With this architecture, availability of whois service is possible even
during partial hardware failures or system maintenance windows.
Requested data is fetched from a database server that is configured as
read-only and is kept synchronized with the main database through
replication. Although data replication is asynchronous,
synchronization delay between the primary master database server and
each read-only database server is continuous and is measured in terms
of milliseconds most of the time.
Performance tests carried out in a lab environment, which was
equivalent to the planned production hardware and software, gives us
confidence that the planned initial setup with 2 whois servers is able
to handle hundreds of simultaneous clients without negatively
affecting service performance.
During these performance tests, round-trip times (RTTs) of whois
queries averaged around 10 milliseconds on local network. Even
considering a scenario with RTTs of 500 milliseconds for clients with
very poor connectivity to our network, Service Level Agreement (SLA)
specified in the Registry Agreement can still be easily honored. As a
benchmark, RTTs for DNS queries sent from our network to servers in
the US West Coast is under 200 milliseconds, to servers in Europe is
around 210 milliseconds, and to servers in Southeast Asia is around
320 milliseconds.
3. Security
Even though the whois specification does not make strong provisions
for security, our implementation has a mechanism to help avoid abuse
by limiting the rate of queries per IP (Internet Protocol). For
instance, a limit could be set for the number of queries per 5 minute
period and⁄or queries per hour, and so on. Because this query rate
limit is based on the client IP address, the load balancer works in a
way that guarantees that queries originating from one client are
always directed to the same real server.
Since there may be some service providers and registrars that require
to make a significant amount of legitimate queries on our whois
server, there is the option of adding some IP addresses to a white
list. Additionally, there is also a black list where known abusers can
be included and therefore will no longer be allowed to send whois
queries.
4. Query⁄Response Examples
4.1 Domain Name Data
4.1.1 Query format: whois example.UOL
4.1.2 Response format:
Domain Name: example.UOL
Domain ID: d-123-tld
Whois Server: whois.nic.UOL
Creation Date: 2012-01-01 08:00:00
Last Update Date: 2012-01-01 08:00:00
Expiration Date: 2014-01-01 08:00:00
Sponsoring Registrar ID: R-EXR-TLD
Sponsoring Registrar Name: Example Registrar Ltda
Domain Status: clientTransferProhibited
Registrant ID: ABCDE-TLD
Registrant Name: Example Registrant Org
Registrant Organization: Example Registrant Org
Registrant Street: 111 Example Street
Registrant City: Example City
Registrant State⁄Province:
Registrant Postal Code: 11111
Registrant Country: BR
Registrant Phone: +55.1155555555
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email@example.UOL
Admin ID: XYYZZ-TLD
Admin Name: Example Registrant Admin
Admin Organization: Example Registrant Org
Admin Street: 111 Example Street
Admin City: Example City
Admin State⁄Province:
Admin Postal Code: 11111
Admin Country: BR
Admin Phone: +55.1155555556
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email@example.UOL
Tech ID: XYYZZ-TLD
Tech Name: Example Registrant Tech
Tech Organization: Example Registrant Org
Tech Street: 111 Example Street
Tech City: Example City
Tech State⁄Province:
Tech Postal Code: 11111
Tech Country: BR
Tech Phone: +55.1155555556
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: email@example.UOL
Name server: ns1.exampleregistrar.UOL
Name server check status: 2012-01-10 AA
Name server last AA status: 2012-01-10
Name server: ns2.exampleregistrar.UOL
Name server check status: 2012-01-10 AA
Name server last AA status: 2012-01-10
DNSSEC: signed
DS: 57436 RSA⁄SHA-1 CCB7D717A8868B8739A78FEC8FB60E62EBE2D89B
DS check status: 2012-01-10 DSOK
4.2 Contact Data
4.2.1 Query format: whois XYYZZ-TLD
4.2.2 Response format:
Contact ID: XYYZZ-TLD
Contact Name: Example Registrant
Contact Organization: Example Registrant Org
Contact Street: 111 Example Street
Contact City: Example City
Contact State⁄Province:
Contact Postal Code: 11111
Contact Country: BR
Contact Phone: +55.1155555556
Contact Phone Ext:
Contact Fax:
Contact Fax Ext:
Contact Email: email@example.UOL
4.3 Registrar Data
4.3.1 Query format: whois R-EXR-TLD
4.3.2 Response format:
Registrar ID: R-EXR-TLD
Registrar Name: Example Registrar Ltda
Registrar Street: 222 Example Street
Registrar City: Example City
Registrar State⁄Province:
Registrar Postal Code: 22222
Registrar Country: BR
Registrar Phone: +55.1155555550
Registrar Phone Ext:
Registrar Fax:
Registrar Fax Ext:
Registrar Email: email@exampleregistrar.UOL
Registrar Whois Server: whois.exampleregistrar.UOL
Registrar URL: http:⁄⁄www.exampleregistrar.UOL
Admin ID: EXREG-TLD
Admin Name: Example Registrar Admin
Admin Organization: Example Registrar
Admin Street: 111 Example Street
Admin City: Example City
Admin State⁄Province:
Admin Postal Code: 11111
Admin Country: BR
Admin Phone: +55.1155555556
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email@exampleregistrar.UOL
4.4 Nameserver Data
This query is not supported because hostnames are mapped as domain
attributes.
5. Bulk Registration Data Access to ICANN (Internet Corporation for
Assigned Names and Numbers)
A weekly report on all registered domain names and sponsoring
registrars will be made available to ICANN. This report will contain
a subset of the Data Escrow Records and be formatted according to
the Data Escrow Format Specification, as specified in the new .UOL
TLD (Top Level Domain) Agreement.
A Data Escrow formatted file reporting all domain names of a given
registrar will also be made available at ICANN request.
6. Resourcing plan
.UOL back-end registry will be fully outsourced to NIC.br.
The Whois component of the Registry System is built on current NIC.br
infrastructure and acquisition of new server hardware. This combined
hardware system will be used for all NIC.br new gTLDs operations and
is detailed in response to question 32.
Initial hardware and software configuration setup and service
maintenance for all NIC.br new gTLD operations will be trusted to the
personnel who currently run the .br Registry operations: network,
system and software engineer teams composed of 12 engineers, along
with NIC.br 24x7 Network Operations Center (NOC).
These setup and operational costs are distributed among all NIC.br new
gTLDs operations as detailed in each Financial Projections as
Operating (Technical Labor and Operation of SRS) and Capital (Hardware
and Software) Expenditures.
| gTLD | Full Legal Name | E-mail suffix | Detail | | .globo | Globo Comunicação e Participações S.A | registro.br | View |
1. Description
The Whois service is provided by a NIC.br (Núcleo de Informação e Coordernação do Ponto BR) implementation. It supports lookup functionality for domains, user IDs and registrar data.
Service is available via port 43 in accordance with RFC 3912 (Request For Comments), and as a web-based directory service at whois.nic.GLOBO.
2. High availability and performance
To guarantee high availability of the service, it is redundant by having different instances of the server software running on separate machines behind a load balancer hardware. The [Q26-diagram1] illustrates that topology:
With this architecture, availability of whois service is possible even during partial hardware failures or system maintenance windows.
Requested data is fetched from a database server that is configured as read-only and is kept synchronized with the main database through replication. Although data replication is asynchronous, synchronization delay between the primary master database server and each read-only database server is continuous and is measured in terms of milliseconds most of the time.
Performance tests carried out in a lab environment, which was equivalent to the planned production hardware and software, gives us confidence that the planned initial setup with 2 whois servers is able to handle hundreds of simultaneous clients without negatively affecting service performance.
During these performance tests, round-trip times (RTTs) of whois queries averaged around 10 milliseconds on local network. Even considering a scenario with RTTs of 500 milliseconds for clients with very poor connectivity to our network, Service Level Agreement (SLA) specified in the Registry Agreement can still be easily honored. As a benchmark, RTTs for DNS queries sent from our network to servers in the US West Coast is under 200 milliseconds, to servers in Europe is around 210 milliseconds, and to servers in Southeast Asia is around 320 milliseconds.
3. Security
Even though the whois specification does not make strong provisions for security, our implementation has a mechanism to help avoid abuse by limiting the rate of queries per IP (Internet Protocol). For instance, a limit could be set for the number of queries per 5 minute period and⁄or queries per hour, and so on. Because this query rate limit is based on the client IP address, the load balancer works in a way that guarantees that queries originating from one client are always directed to the same real server.
Since there may be some service providers and registrars that require to make a significant amount of legitimate queries on our whois server, there is the option of adding some IP addresses to a white list. Additionally, there is also a black list where known abusers can be included and therefore will no longer be allowed to send whois queries.
4. Query⁄Response Examples
4.1 Domain Name Data
4.1.1 Query format: whois example.GLOBO
4.1.2 Response format:
Domain Name: example.GLOBO
Domain ID: d-123-tld
Whois Server: whois.nic.GLOBO
Creation Date: 2012-01-01 08:00:00
Last Update Date: 2012-01-01 08:00:00
Expiration Date: 2014-01-01 08:00:00
Sponsoring Registrar ID: R-EXR-TLD
Sponsoring Registrar Name: Example Registrar Ltda
Domain Status: clientTransferProhibited
Registrant ID: ABCDE-TLD
Registrant Name: Example Registrant Org
Registrant Organization: Example Registrant Org
Registrant Street: 111 Example Street
Registrant City: Example City
Registrant State⁄Province:
Registrant Postal Code: 11111
Registrant Country: BR
Registrant Phone: +55.1155555555
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email@example.GLOBO
Admin ID: XYYZZ-TLD
Admin Name: Example Registrant Admin
Admin Organization: Example Registrant Org
Admin Street: 111 Example Street
Admin City: Example City
Admin State⁄Province:
Admin Postal Code: 11111
Admin Country: BR
Admin Phone: +55.1155555556
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email@example.GLOBO
Tech ID: XYYZZ-TLD
Tech Name: Example Registrant Tech
Tech Organization: Example Registrant Org
Tech Street: 111 Example Street
Tech City: Example City
Tech State⁄Province:
Tech Postal Code: 11111
Tech Country: BR
Tech Phone: +55.1155555556
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: email@example.GLOBO
Name server: ns1.exampleregistrar.GLOBO
Name server check status: 2012-01-10 AA
Name server last AA status: 2012-01-10
Name server: ns2.exampleregistrar.GLOBO
Name server check status: 2012-01-10 AA
Name server last AA status: 2012-01-10
DNSSEC: signed
DS: 57436 RSA⁄SHA-1 CCB7D717A8868B8739A78FEC8FB60E62EBE2D89B
DS check status: 2012-01-10 DSOK
4.2 Contact Data
4.2.1 Query format: whois XYYZZ-TLD
4.2.2 Response format:
Contact ID: XYYZZ-TLD
Contact Name: Example Registrant
Contact Organization: Example Registrant Org
Contact Street: 111 Example Street
Contact City: Example City
Contact State⁄Province:
Contact Postal Code: 11111
Contact Country: BR
Contact Phone: +55.1155555556
Contact Phone Ext:
Contact Fax:
Contact Fax Ext:
Contact Email: email@example.GLOBO
4.3 Registrar Data
4.3.1 Query format: whois R-EXR-TLD
4.3.2 Response format:
Registrar ID: R-EXR-TLD
Registrar Name: Example Registrar Ltda
Registrar Street: 222 Example Street
Registrar City: Example City
Registrar State⁄Province:
Registrar Postal Code: 22222
Registrar Country: BR
Registrar Phone: +55.1155555550
Registrar Phone Ext:
Registrar Fax:
Registrar Fax Ext:
Registrar Email: email@exampleregistrar.GLOBO
Registrar Whois Server: whois.exampleregistrar.GLOBO
Registrar URL: http:⁄⁄www.exampleregistrar.GLOBO
Admin ID: EXREG-TLD
Admin Name: Example Registrar Admin
Admin Organization: Example Registrar
Admin Street: 111 Example Street
Admin City: Example City
Admin State⁄Province:
Admin Postal Code: 11111
Admin Country: BR
Admin Phone: +55.1155555556
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email@exampleregistrar.GLOBO
4.4 Nameserver Data
This query is not supported because hostnames are mapped as domain attributes.
5. Bulk Registration Data Access to ICANN (Internet Corporation for
Assigned Names and Numbers)
A weekly report on all registered domain names and sponsoring registrars will be made available to ICANN. This report will contain a subset of the Data Escrow Records and be formatted according to the Data Escrow Format Specification, as specified in the new .GLOBO TLD (Top Level Domain) Agreement.
A Data Escrow formatted file reporting all domain names of a given registrar will also be made available at ICANN request.
6. Resourcing plan
.GLOBO back-end registry will be fully outsourced to NIC.br.
The Whois component of the Registry System is built on current NIC.br infrastructure and acquisition of new server hardware. This combined hardware system will be used for all NIC.br new gTLDs operations and is detailed in response to question 32.
Initial hardware and software configuration setup and service maintenance for all NIC.br new gTLD operations will be trusted to the personnel who currently run the .br Registry operations: network, system and software engineer teams composed of 12 engineers, along with NIC.br 24x7 Network Operations Center (NOC).
These setup and operational costs are distributed among all NIC.br new gTLDs operations as detailed in each Financial Projections as Operating (Technical Labor and Operation of SRS) and Capital (Hardware and Software) Expenditures.