TrueTLD

.moto Domain — Registry Information

.moto, delegated in 2016, is operated by Motorola Trademark Holdings, LLC. It is a closed brand extension. See more about .moto →

.moto is a closed brand extension. Only Motorola Trademark Holdings, LLC and the companies it allows can register names under it, so you cannot buy a .moto domain from a registrar.

Official registry site →

Some companies hold a top-level domain of their own, and .moto is one of them. It is kept for the company's own use and is not sold to the public the way .com is. ICANN accepted applications for these in 2012.

The registry agreement between ICANN and Motorola Trademark Holdings, LLC for .moto is dated 4 June 2015. ICANN records it as a brand agreement (Specification 13). ICANN also published a notice of exemption from the registry code of conduct, a step open to registries that serve their own organisation.

If you want to register .moto, note that a registrar page that appears to sell it cannot fill the order: only the company and the companies it allows can register names under .moto. The registry's site is motorola.com.

Background: ICANN.

Technical details

Type gTLD · New generic
Registry Motorola Trademark Holdings, LLC
Delegated 12 November 2016
WHOIS server whois.nic.moto
Domain level Top-level domain
Extension itself is an IDN No (Latin letters)
DNSSEC Supported
Registration term Up to 10 years (ICANN limit)
Label length Up to 63 characters (DNS limit)

.moto questions

What kind of domain is .moto?

.moto is a brand extension, kept for one company's own use. Motorola Trademark Holdings, LLC runs the registry, and it was delegated in 2016.

Can I register a .moto domain?

No. .moto is a closed brand extension. Only Motorola Trademark Holdings, LLC and the companies it allows can register names under it, so no registrar sells it.

Who operates .moto?

.moto is operated by Motorola Trademark Holdings, LLC. IANA lists the delegation date as 12 November 2016.

Does .moto support DNSSEC?

Yes. DNSSEC is available for .moto domains at the registry level, so a signed zone can be validated by resolvers.