.BR is the ccTLD of Brazil.
In order to successfully register a COM.BR domain, the registrant must meet specific requirements as mandated by the BR Registry (Registro Br). If all requirements are met when the request is submitted, the registration should complete within a day; however, in some cases it can take up to 45 days before a domain registration completes.
COM.BR registrations do not occur real-time; they are done through an asynchronous process. When a COM.BR registration request is submitted, the order is placed in your Reseller account’s in progress queue and the order state is waiting for registry response. API based queries of in progress orders will return a status of waiting.
Registration details can be found in the TLD reference chart.
Any person or organization that is legally established in Brazil as a legal entity (institution) or as an individual (liberal professional or natural person) with a contact location within the Brazilian national territory can register a .COM.BR domain name.
To prove their eligibility, they must submit a legal identification number issued by the government organization, the Secretariat of the Federal Revenue of Brazil (Secretaria da Receita Federal). For organizations, this is the CNPJ (Business Identifier / Cadastro Nacional de Pessoa Juridica); for individuals, this is the CPF (Individual Tax Number / Cadastro de Pessoa Fisica).
The registry validates the registrant name, company name, and owner contact address associated with the CNPJ or CPF with the federal revenue service of Brazil (Secretariat of the Federal Revenue of Brazil). You can view the information associated with a CNPJ on the Secretariat of the Frederal Revenue of Brazil’s website at: http://www.receita.fazenda.gov.br/pessoajuridica/cnpj/cnpjreva/cnpjreva_solicitacao.asp
If the CPF or CNPJ has already been used for a COM.BR registration with another Registrar, the registrant needs to contact the BR Registry and request a change of Registrarbefore they register a new COM.BR domain with OpenSRS.
We recommend that you implement a programmatic validation routine when accepting a CNPJ or CPF number to ensure that the submitted values are in the correct format.
- CNPJ Format (14 digits): NN.NNN.NNN/NNNN-NN
- CPF Format (11 digits): NNN.NNN.NNN-NN
Google Gadgets hosts a CPF & CNPJ validation tool here:
You can find additional information on the CNPJ, including examples of validation scripts on this page:
Note: This page is in Portuguese and you may prefer to view it through a translator.
This page provides additional information on the CPF including examples of validation scripts:
Foreign companies may be able to register COM.BR domains, but in order to do so, they must meet the additional requirements outlined below in the section Registrations by Foreign Entities.
Contact Information requirements
COM.BR registrations require four contact types: Owner, Admin, Technical, and Billing. The Owner and Billing contact information must include real Brazilian addresses, and all information must be entered correctly, as the addresses will be validated by the Registry.
Note: Contact validation is not performed by OpenSRS; it is done by the BR Registry after the registration request is submitted by OpenSRS.
Street and city names that include accents must be submitted in UTF-8 encoding. For example, the UTF-8 encoding of São Paulo would be: S[c3][a3]o Paulo.
When using the OpenSRS Control Panel to register a domain name, make sure that your browser’s encoding is set to UTF-8 so that you can submit accented characters properly, for example entering São Paulo as the city.
When submitting registrations through the API, make sure that the programming language that you use can submit information in UTF-8 encoding.
Further information on UTF-8 encoding is available here:
If the country submitted is BR (Brazil), then the state must be a valid Brazilian state code: AC, AL, AP, AM, BA, CE, DF, ES, GO, MA, MT, MS, MG, PA, PB, PR, PE, PI, RJ, RN, RS, RO, RR, SC, SP, SE, or TO
We recommend that you validate the postal code format and that the state that is submitted correctly correlates to the postal code that is submitted.
You can find information about Brazilian postal codes here:
Nameserver & DNS Requirements
When registering a COM.BR domain, you must submit two authoritative nameservers, and these nameservers must respond to DNS queries by the BR Registry
If the nameservers exist, but are not yet responding to queries for the domain being registered, they are not considered authoritative for the domain, and the order will remain in a waiting state in the in progress queue until the DNS is verified by the BR Registry. If the DNS cannot be verified, the request will expire after 14 days.
You can use nameservers within the same namespace as a domain only after that domain has been successfully registered.
The BR Registry provides a web-based tool that can be used to check the validity of the DNS settings prior to submitting a registration: http://registro.br/cgi-bin/nicbr/dnscheck
Important: The OpenSRS System_DNS Service nameservers cannot be used when registering a COM.BR domain. Zone entries cannot be set up in SystemDNS unless the domain has been registered. Once a COM.BR domain has been successfully registered, it can then use the SystemDNS service.
Transfers into your OpenSRS reseller account are processed manually by our support team. Please contact us with the following information to process a transfer:
- domain name
- reseller account username
- registrant contact ID at NIC.BR <http://NIC.BR> registry
- registrant contact password at NIC.BR <http://NIC.BR> registry
There is a charge for .BR transfers and a domain transfer of a .BR domain will not renew the domain or extend the registration term.
Registering Dropped Names
When domains expire and are not renewed they are made available to be registered again. These are referred to as dropped domains. The BR Registry only drops domains three to four times per year, and not on a specific schedule.
Although names become available for registration when you query the registry, it can take up to 45 days to complete the registration of dropped names due to the review process that is performed by the BR Registry.
Additionally, multiple end users could apply for the same droppeddomain name. If this happens, the domain registration could stay in a waiting state (in progress) for as long as 45 days. If domain registration does not complete within 45 days, OpenSRS declines the registration.
When a registrant submits a request for a dropped domain, they can choose to certify that they have a demonstrable legal right to that domain. If they choose this option, but they cannot provide a document showing that they have a legal right to that domain, the registry will not award the domain AND they reserve the right to hold a bias against the registrant if they make any future applications for dropped domains. In order to demonstrate proof of a legal right to a domain, the registry will accept the following:
- A copy of the trademark certificate (fully registered trademark) granted by the INPI, identical to the domain name requested.
- A copy of the registrant's Articles of Incorporation where the Company Name is identical (or confusingly similar) to the domain name requested. The holder must also submit proof that they have been using this Company Name with the pubic for more than thirty (30) months.
There is still no guarantee that the registry will award the domain name, even when these documents are provided, but your chances are significantly higher if you can provide these supporting documents. In any case, DO NOT indicate that you can demonstrate a legal right to that domain name if you do not have the supporting documentation.
Registering Related Names
Domains that are similar, where something like the presence of a hyphen or accented characters is the only difference, can only be registered by a single applicant.
Attempts to register accented or non-accented versions of a domain that is already registered will fail unless the identification and contact information that is submitted for the new domain registration matches that of the existing registered domain.
Accented character example: pensãoboa.com.br and pensaoboa.com.br
When the Registry checks domain name registration requests that include hyphens, the hyphens are stripped out and this could result in a name that is already registered. When this happens, the registration request will fail unless the identification and contact information that is submitted for the new domain registration request matches that of the existing registered domain.
Hyphen example: oneexample.com.br and one-example.com.br
Registry errors are recorded in the notes field of a registration order. Some of the most common errors are explained here.
CNPJ/CPF & Contact Set Errors
If the CNPJ/CPF number has been used with a different registrar for a different domain, it cannot be re-used with OpenSRS and the domain registration will fail.
An example of such a scenario:
"Parameter value syntax error\ntext Invalid attribute value syntax; Could not get registry contact for ownercontact (P-XXX0000: 531 Authorization failed; CNPJ/CPF (000.000.000-00) belongs to another provider (000))"
If the CNPJ/CPF has been previously used to successfully register a domain with an OpenSRS reseller and a request to register a new domain is being submitted with the same CNPJ/CPF, all contact data must match what was submitted previously or the following error will occur:
"Could not create owner, possibly due to CNPJ/CPF re-use. Owner contact data must match owner from previous pending sw_order 123456"
Another example for a similar CNPJ/CPF re-use situation:
"Parameter value syntax error\ntext Contact error ; Could not get registry contact for ownercontact (P-XXX000: 549 Command failed; [Could not create organization!])"
Additional errors where the CNPJ/CPF may be invalid or the submitted contact information does not match what is on file:
“Parameter value syntax error text Invalid attribute value syntax; Could not get registry contact for ownercontact (P-XXXXX: 541 Invalid attribute value; Could not create organization); Could not get registry contact for admincontact (P-XXXXX: 541 Invalid attribute value [contact:pc => 13526965: Incompatible Postal code and city]); Could not get registry contact for techcontact (P-XXXXX: 541 Invalid attribute value [contact:pc => 13526965: Incompatible Postal code and city]); Could not get registry contact for billingcontact (P-XXXXX: 541 Invalid attribute value [contact:pc => 13526965: Incompatible Postal code and city]) [contact:pc => 13526965: Incompatible Postal code and city]”
“Parameter value syntax error text Invalid attribute value syntax; Could not get registry contact for ownercontact (P-ACS2985: 541 Invalid attribute value; Could not create organization); Could not get registry contact for admincontact (P-ACS2985: 541 Invalid attribute value [contact:pc => 66000000: Incompatible Postal code and city]); Could not get registry contact for techcontact (P-ACS2985: 541 Invalid attribute value [contact:pc => 66000000: Incompatible Postal code and city]); Could not get registry contact for billingcontact (P-ACS2985: 541 Invalid attribute value [contact:pc => 66000000: Incompatible Postal code and city]) [contact:pc => 66000000: Incompatible Postal code and city]”
“Command failed text Command failed [Inexistent organization]”
“Command failed text Command failed [Irregular CNPJ]”
“At 2011-11-06 14:45:22 UTC we received a poll message DOMAIN_REGISTRATION_FAILED:The document does not exist in the SRF database.”
“At 2011-11-06 15:30:28 UTC we received a poll message DOMAIN_REGISTRATION_FAILED:The document is cancelled according to the SRF.”
“At 2011-11-06 23:00:27 UTC we received a poll message DOMAIN_REGISTRATION_FAILED:The document is suspended according to the SRF.’
“At 2011-11-06 23:45:24 UTC we received a poll message DOMAIN_REGISTRATION_FAILED:The document is irregular according to the SRF.”
Example for invalid street number:
"541 Invalid attribute value [contact:street: Invalid address number]"
Nameserver & DNS Errors
An invalid nameservers submitted:
“Request failed validation: Name server 'ns2.livednsdomain.com' is not found at the registry.Please double check the nameserver and re-submit. Name server 'ns3.livednsdomain.com' is not found at the registry.Please double check the nameserver and re-submit. Name server 'ns1.livednsdomain.com' is not found at the registry.Please double check the nameserver and re-submit.”
Example error for failing the authoritative zone validation:
“Command failed text Command failed [dns precheck failed!]”
Registrations by Foreign Entities
Foreign companies may be able to register COM.BR domains with OpenSRS; however, all of the following requirements must first be met.
In order for a foreign company to register a .BR domain, it must appoint a legally established attorney-in-fact in the country, the company must be registered with the BR Registry, and it must meet some additional criteria. Once the foreign company is registered with the BR Registry, the company will receive an identification number (CNPJ) that must be submitted with the domain registration request.
To register a foreign company with the BR Registry you must provide the following:
- A power of attorney notarized in the company’s country of origin, conferring authority on the attorney-in-fact to perform acts regarding domain registry, domain cancellation, domain ownership transfer and change of the contact person for the entity.
- A statement, duly notarized in the company’s country of origin, declaring the commercial activity of the company, including the following: trade name, full registered address, telephone number, business purpose, activities performed, name and position of the legal representative.
- A statement, duly notarized in the company’s country of origin, declaring the company’s commitment to permanently carry out its activities in Brazil, within 12 months from the receipt of the statement.
- A sworn translation of the power of attorney, the commercial activity statement and the commitment statement.
- A copy of the CNPJ or CPF (individual tax payer registration number) of the attorney-in-fact.
- An official letter from the attorney-in-fact establishing the ID of the contact for the foreign entity.
An official letter from the attorney-in-fact establishing the ID of the contact for the foreign entity.
All documents must be certified by the Brazilian Consulate in the company’s country of origin.
If the attorney-in-fact does not have an entity registered in the BR Registry system, this registration would also have to be made, and all pertinent information regarding the attorney-in-fact must be sent: CNPJ/CPF, trade name/ name, full address, telephone number and ID of the contact for the entity.
All documents must be sent to Registro.br at this address:
A/C Hostmaster - Registro .br
Subject: Cadastro de empresa estrangeira
Av. das Nações Unidas, 11541, 7° andar
04578-000 - São Paulo – SP
- The domain billing contacts registered by the company must be residents in Brazil.
- The trade name of the foreign company can only be altered administratively by Registro.br.
For additional information, refer to the BR Registry (http://registro.br).