.globo

Generic top-level domain

RDAP

Register: —first year
Renew: —a year
Transfer: —to move it
Registrars: —quoting it
Lookup: RDAPanswers for it
DNSSEC: Signed1 DS record in the root
Level: Secondmybrand.globo

Check a name

One command, straight against the registry — no account, no page to load.

Name

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld globo

Add --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.

What it costs

No registrar in the price table bundled with ds quotes .globo, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.

Who can register

No eligibility rule is on file for .globo, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.

How `ds` answers for it

RDAP first, WHOIS second — the same order for every TLD. .globo has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.

RDAP: https://rdap.gtlds.nic.brFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.gtlds.nic.br/domain/mybrand.globo — a 404 means the name is free.

ds mybrand --tld globo --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .globo today. See Accuracy notes.

The registry

From IANA's delegation record for .globo. .globo is a generic TLD.

Run by: Globo Comunicação e Participações S.ABased in Brazil. Delegated 2014-02-20, record last updated 2025-08-14.
Registry site: nic.globoWhere the registry documents .globo — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services: rdap.gtlds.nic.brWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers: a.dns.brb.dns.brc.dns.brd.dns.bre.dns.brf.dns.brThe 6 authoritative servers for the .globo zone — what the root delegates to. Nothing ds queries directly; they are what makes a registered name resolve.

What it is

Derived from the root zone and ICANN's registry list — each one is a fact with a source.

generic IANA Root Zone Database types it "generic"
new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

In the root zone

The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .globo was delegated to; this is what the root actually answers with when a resolver asks it where .globo lives.

Delegated to: a.dns.br200.219.148.102001:12f8:6::10
b.dns.br200.189.41.102001:12f8:8::10
c.dns.br200.192.233.102001:12f8:a::10
d.dns.br200.219.154.102001:12f8:4::10
e.dns.br200.229.248.102001:12f8:2::10
f.dns.br200.219.159.102001:12f8:c::10
The 6 name servers the root hands out for .globo, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC: Signed — 1 DS record in the root
key 50876ECDSA P-256/SHA-256 · SHA-256FE98518CAB979F2D0D8021EF06AE5DC713C79A5870FF8FFF8E38B67CF6578FB8
Each one is a fingerprint of .globo's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .globo came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net globo. NS and dig +norec @a.root-servers.net globo. DS.