Can You Register a .data Domain?

You cannot currently buy a .data domain through the normal public checkout used for .com, .tech, or .cloud. The extension exists in the DNS root, and DISH DBS Corporation publishes a .data registration policy, but the policy makes registration conditional on eligibility, intended use, registry approval, and an authorized registrar.

That is different from saying nobody can ever register one. The policy recognizes DISH-related applicants, people or entities with a meaningful media nexus, and a broad class of “Qualified Applicants” connected with online services or data. The registry decides whether an applicant qualifies. As of 16 August 2026, the official .data registry page provides policies and an abuse contact, but no public registrar list, application button, retail checkout, or retail price.

1) Separate TLD delegation from public registration

IANA's Root Zone Database answers a technical question: is .data a real top-level domain in the public DNS, and who manages it? Its current record identifies .data as a generic TLD, names Dish DBS Corporation as the sponsoring organization, and lists the registry's WHOIS and RDAP services.

That record does not say every person can register name.data. Delegation and retail availability sit at different layers:

1. Delegation: IANA places the TLD in the root and records its operator and technical services.
2. Registry policy: the operator defines eligible registrants, acceptable uses, allocation, verification, and enforcement within its ICANN contract.
3. Registrar access: an accredited registrar must have a working route into the registry and offer the TLD to the relevant applicant.
4. Registration: the registry accepts the applicant and allocates the requested second-level name.
5. DNS use: the registered name receives nameservers and can resolve on the internet.

Many misleading .data pages collapse all five steps into a green “available” result. A text box accepting example.data proves only that the website can parse the string. It does not prove registry access, applicant eligibility, allocation, or checkout completion.

The availability guide explains the wider difference between a search response, registration data, DNS, and a completed registrar transaction.

2) Check who the registry says may qualify

The official DISH registration policy does not describe .data as open to everyone. It says a registrant must fall into at least one of three groups, as determined by the registry:

• own, work for, be associated with, or be affiliated with DISH and its affiliates;
• have a meaningful nexus with television or media content broadcasting or production; or
• be a Qualified Applicant.

The policy defines Qualified Applicants broadly. It includes entities providing online or cloud-based services or products, entities involved in delivering data, and entities sharing an interest in the provision, enhancement, or use of data. Examples in the definition include government or regulatory bodies, consultants, resellers, academia, law firms, and engineers.

That breadth does not create an automatic right to a domain. The registry retains sole discretion over eligibility. The applicant must also show a bona fide intention to use the name in support of the TLD's mission and a clear, logical connection between the applicant, the intended use, and the requested label.

The policy further allows the registry to:

• request evidence before approval;
• verify eligibility before or after registration;
• reject an application even after a fee has been accepted;
• suspend, transfer, cancel, or revoke a name that fails the rules; and
• allocate names by first come, first served, auction, request for proposal, or registry designation.

Eligibility is therefore only the first gate. A data company may appear to fit the definition and still lack a registrar route or registry approval for the exact name.

3) Use the current evidence, not an old launch page

The most reliable current checks point in the same direction, but each proves something different.

The live RDAP check matters because it avoids another common error. A TLD can be delegated but unused at the second level. On 16 August 2026, the IANA-listed RDAP service returned nic.data with active status. Its record showed a registration event on 9 April 2025 and a last database update on 15 August 2026.

That is evidence of one specific registry name. It is not a defensible count of all .data registrations. FlashDomains found a secondary zone-monitor page claiming one zone name, but did not use that count as a fact because the source is not the registry and a zone file is not identical to the full registration database.

4) Treat “pre-register” as an unfulfilled request

Current search results include pages that say “buy,” “register,” or “pre-register” a .data domain. Those phrases can describe very different transactions.

A legitimate registration path should identify the contracting registrar, the eligibility documents, registry review, allocation method, total charges, renewal terms, and refund treatment if the registry rejects the request. If the seller cannot supply those details, do not treat the offer as registrable inventory.

The registry policy is unusually important here. It states that accepting registration fees does not itself constitute registration. A name is registered only after registry approval of the registrant's eligibility and subsequent allocation through a registrar or another permitted route.

5) Follow a controlled application check

If your organization plausibly fits the registry's policy and the exact .data name has strategic value, use a written verification process.

1. Describe the applicant. Record the legal entity, its services, and the connection to online services, cloud products, data delivery, media, or another policy category.
2. Describe the intended use. State what the domain will host, who will use it, and why the label has a logical connection to that purpose.
3. Contact the registry. Use the current registry site and ask which accredited registrar can submit a .data application, what evidence is required, and whether applications are being accepted.
4. Verify the registrar. Confirm the seller is ICANN-accredited and has a current registry agreement or an authorized route for .data.
5. Get the economics in writing. Ask for the application fee, registration price, renewal price, premium classification, taxes, refund terms, and any non-refundable review charge.
6. Confirm allocation. Ask whether the name is first come, first served, auctioned, reserved, registry-designated, or subject to a proposal process.
7. Wait for approval. Do not announce the address, print it, or redirect customers until the registrar confirms a completed registration and RDAP shows the record.
8. Check DNS. Verify nameservers, DNSSEC where used, web resolution, email records, and renewal controls.

Keep the registry response and registrar terms with the domain record. The policy allows later eligibility verification and enforcement, so the organization needs evidence that its use continues to fit.

6) Compare open alternatives before applying

Most data products need a usable address now. Compare the complete name under open retail TLDs before committing time to a restricted application.

These prices are public, standard-name examples from one registrar. They can change by promotion, account, country, tax, term, premium status, and checkout. The first-year price is not the decision price. Compare at least three years of renewal cost and test the full name for conflict and spoken recall.

For example, a concise atlascloud.com may be stronger than a theoretical atlas.data that cannot be ordered. A clean atlas.tech may be more useful than an awkward .com with two qualifiers. The %%EDITORIAL_4%% page, %%EDITORIAL_5%% page, and TLD guide provide the next comparison layers.

7) Verify any future public launch again

Registry status can change. A later public launch would need fresh evidence, not an update to a reseller's marketing copy.

Before changing this answer, verify all of the following:

• the official registry site announces an application or launch phase;
• an accredited registrar identifies .data as currently orderable;
• the registrar provides the eligibility workflow and registry review terms;
• a live search returns a defined status for the exact name;
• checkout discloses registration, renewal, premium, and non-refundable charges; and
• a successful test registration appears in the registry's RDAP service.

IANA delegation alone will remain insufficient. So will a “coming soon” page, a stored interest form, or an estimated price.

FlashDomains should classify .data as restricted, registry-approved, and not available through ordinary retail search, rather than showing a normal availability verdict or sending a buyer to a generic registrar checkout.

8) Use this decision rule

Use the shortest accurate route:

• Ordinary buyer: do not plan around .data; compare open alternatives.
• Data or cloud organization: you may fit the published definition, but first obtain the current registrar and registry approval process.
• Media organization: document the media nexus and intended use, then ask the registry whether applications are active.
• DISH affiliate: follow the operator's internal or approved registrar process.
• Anyone shown a price: verify what the payment buys and whether rejection is refundable.
• Anyone shown “available”: require a registry-backed order path before relying on the result.

The right answer is not that .data is imaginary, open to everyone, or permanently closed. It is a real, delegated, restricted namespace with a broad eligibility policy but no verified public retail route or public retail price as of 16 August 2026.

Research the registry first. If the route remains unclear, choose a domain you can register, renew, and deploy with known terms.