ds

.canon

Generic top-level domain

RDAPbrand TLD

Nobody outside the registry can register here. .canon is a brand TLD run by Canon Inc., which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.

Registration
Closedno public names
Operator
Canon Inc.
Lookup
RDAPanswers for it
DNSSEC
Signed1 DS record in the root
Level
Secondmybrand.canon

Check a name

Names under .canon cannot be registered, but ds will still tell you what the registry says.

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 canon

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 .canon, 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, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.

Who can register

Nobody outside Canon Inc. — see the note at the top of this page.

How ds answers for it

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

RDAP
https://rdap.gmoregistry.net/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.gmoregistry.net/rdap/domain/mybrand.canon — a 404 means the name is free.

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

The registry

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

Run by
Canon Inc.Based in Japan. Delegated 2015-01-29, record last updated 2019-08-20.
Registry site
nic.canonWhere the registry documents .canon — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.gmoregistry.net · whois.nic.canonWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
a.gmoregistry.netb.gmoregistry.netk.gmoregistry.netl.gmoregistry.netThe 4 authoritative servers for the .canon 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"
  • brand ICANN records Specification 13 — a brand TLD, closed to the public
  • 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 .canon was delegated to; this is what the root actually answers with when a resolver asks it where .canon lives.

Delegated to
  • a.gmoregistry.net37.209.192.42001:dcd:1::4
  • b.gmoregistry.net37.209.194.42001:dcd:2::4
  • k.gmoregistry.net37.209.196.4
  • l.gmoregistry.net37.209.198.42001:dcd:4::4
The 4 name servers the root hands out for .canon, with the glue addresses that come with them — 3 of them answer 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 5225RSA/SHA-256 · SHA-2569A1FC16A90ACF3C7D3233480F45F595DEBDEF3F71AE637BF3F8093670DDA7D8A
Each one is a fingerprint of .canon'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 .canon 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 canon. NS and dig +norec @a.root-servers.net canon. DS.

Also answered by rdap.gmoregistry.net

and 33 more zones on the same server.