Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Protecting a brand during a new domain-extension launch requires three coordinated steps: keep trademark records and proof of use current, enroll eligible marks in the Trademark Clearinghouse (TMCH), and track each extension’s Sunrise and Trademark Claims dates. Then decide in advance which domains to register, monitor, or challenge. TMCH can provide priority access and alerts, but it does not reserve every matching domain or automatically block all registrations.
Why new domain extensions create a brand-protection problem
When a registry launches a new top-level domain (TLD), customers may begin seeing addresses that end in a new extension rather than a familiar country code or generic ending. A brand could be used in that extension by the legitimate owner, an unrelated business, a reseller, a critic, or an abusive registrant. The risk is not limited to a single website: a matching domain can be used for phishing, counterfeit sales, misleading advertising, impersonation, or customer-support fraud.
There is no universal launch day for all new extensions. Each registry submits its own Sunrise and Claims schedule, and its allocation rules determine who receives a contested name. ICANN’s New gTLD Program: 2026 Round application period closed on 12 August 2026 after running from 30 April. ICANN reported more than 1,600 applications. The program’s published milestones set Reveal Day for 7 October 2026, a Replacement Period from 8–21 October, and String Confirmation Day for 17 November. Those are program milestones, not dates when every extension becomes available to the public.
For practical brand protection, the registry-specific calendar matters more than the application-round headlines. For example, ICANN’s TLD Startup Information table listed a Sunrise period for .phone from 6 October 2026 through 4 January 2027, followed by Claims from 5 January through 5 April 2027. It listed Sunrise for .eat and .here from 1 September through 9 November 2026. Dates can change, so check the live table and the individual registry’s rules before submitting or paying for a registration.
#1 Best Overall
What the Trademark Clearinghouse does
The Trademark Clearinghouse is a central system that verifies and maintains qualifying trademark information. A verified record can support rights-protection services across participating new gTLDs, so the same rights information does not have to be verified separately for every extension.
| TMCH function | What it provides | What it does not provide |
|---|---|---|
| Rights verification | Authentication of eligible trademark or other qualifying rights information | A guarantee that a domain will be awarded to the trademark holder |
| Sunrise support | Eligibility to use a verified mark record when a registry offers its priority-registration period | Automatic registration or ownership of every corresponding name |
| Claims support | Notice to prospective registrants and, for matching registrations, notice to the matching rights holder | A blanket block on registration or a finding of infringement |
| Matching labels | Corresponding domain labels generated under TMCH rules | Automatic coverage for every typo, translation, abbreviation, or variation |
ICANN’s FAQ says that up to 10 corresponding domain names per mark record are included in the initial verification cost; additional labels can be added for an additional fee. Review the exact labels in the record. Do not assume that a misspelling, translated term, plural, slogan, or product nickname is included merely because it resembles the mark.
TMCH is not a domain-reservation service. Different parties may have legitimate rights in the same trademark, including rights in different jurisdictions or classes of goods and services. A record therefore supports the applicable rights-protection mechanisms; it does not settle every ownership question in advance.
Prepare your brand before a TLD opens
1. Build a prioritized name inventory
Start with the names whose misuse would create the greatest customer, revenue, or safety risk. Include:
- The primary house mark and legally registered versions.
- Important product and service marks.
- Distinctive abbreviations or spelling variants that customers actually use.
- Names tied to markets where the organization sells, operates, or has meaningful commercial exposure.
- Existing official domains and the labels used in advertising, support, and email.
This is a risk-planning list, not an ICANN-mandated filing. Keep the reason for each priority decision: customer confusion, impersonation risk, market importance, or likely abuse. A documented rationale helps when the cost of registering every possible label is greater than the business value.
2. Audit trademark records and evidence of use
Confirm that registration details, owner information, jurisdiction, goods and services, renewal status, and assigned representatives are accurate. TMCH accepts registered trademarks and certain other qualifying rights, but the exact eligibility rules apply to the record submitted.
Sunrise participation requires Proof of Use. Assemble public-facing evidence such as advertising, marketing materials, or product packaging, together with the required signed declaration. Make sure the evidence shows the mark being used for the goods or services covered by the right; a bare registration certificate does not replace Proof of Use for Sunrise.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchResolve discrepancies before a launch. A changed corporate name, assignment, expired registration, or inconsistent mark presentation can delay verification or leave the record unable to support the registration you want.
3. Enroll eligible marks in TMCH
- Choose the marks that meet the eligibility rules and match your priority inventory.
- Submit the rights information and supporting documentation for verification.
- Provide the required Proof of Use and signed declaration if you intend to use Sunrise services.
- Review the generated matching labels, including the limit of up to 10 labels included in the initial verification cost.
- Record the verified status, renewal or maintenance obligations, and the person responsible for updates.
A single verified record can support rights-protection services across new gTLDs, but every registration still follows the particular registry’s policy and registrar process.
Understand Sunrise before you register
ICANN defines a Sunrise Period as a period of at least 30 days when eligible trademark holders have an advanced opportunity to request domain names corresponding to their marks before names are generally available. The minimum is 30 days; a registry may offer a longer period.
What Sunrise gives you
- Priority to request a corresponding domain before general registration.
- A defined application window with registry-specific eligibility and allocation rules.
- An opportunity to reduce the chance that an unrelated party obtains the exact matching label first.
What Sunrise does not give you
- Automatic ownership of every domain that resembles the mark.
- Priority for labels outside the applicable matching rules.
- A guarantee that two eligible applicants will not compete for the same name.
- A substitute for monitoring or dispute procedures after launch.
When more than one eligible party requests a name, the registry’s published policy controls the outcome. Possible allocation methods and documentation requirements differ by extension, so read that registry’s Sunrise rules rather than relying on a generic assumption.
Understand Trademark Claims during general availability
Trademark Claims applies for at least the first 90 days after general registration opens. When a prospective registrant requests a label that matches a recorded mark under the applicable rules, the registrant receives a notice describing the mark information. The registrant may still proceed after acknowledging the notice. If the registration goes ahead, the matching rights holder can receive a notice as well.
Claims therefore informs and alerts; it does not categorically prevent registration. Treat each notice as an intake event. Assign a person or team to record the domain, date, extension, registrant information available from the notice, website and email behavior, and the assessment of legitimate use versus likely abuse.
A practical notice-triage workflow
- Authenticate the notice. Confirm that it came through the expected TMCH or registrar channel before opening links or sending information.
- Check the match. Compare the requested label with the exact mark and the TMCH matching rules.
- Assess the use. Look for a legitimate business, criticism, resale, fan activity, phishing, counterfeit sales, or impersonation.
- Capture evidence. Save dated screenshots, DNS data, email headers, advertisements, checkout pages, and customer reports where relevant.
- Escalate by risk. Route suspected credential theft, payment fraud, or active customer harm immediately; route lower-risk or legitimate uses for documented review.
Track every extension with a launch calendar
Use ICANN’s live TLD Startup Information table as the cross-program starting point, then verify the registry’s own policy and the registrar’s submission process. For each relevant TLD, record:
| Calendar item | Why it matters |
|---|---|
| Sunrise opening and closing | Defines when an eligible holder can submit a priority request. |
| Proof-of-Use and documentation deadline | Missing evidence can make an otherwise eligible request invalid. |
| Claims start and end | Defines the period when matching registrants receive notices and rights holders may receive alerts. |
| General availability date | Marks the point when ordinary registrations open under the registry’s rules. |
| Allocation or contention method | Explains what happens if multiple eligible applicants request the same label. |
| Renewal and premium-name terms | Determines ongoing cost and whether a selected name is financially sustainable. |
Do not treat an application-round milestone as a public-sale date. A string can be confirmed while its registry is still preparing Sunrise, Claims, reserved names, or general availability.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Choose what to register, monitor, or leave alone
Registering every possible label is rarely a defensible strategy. Use a written decision for each mark-extension combination.
| Situation | Usually appropriate first action | Questions to document |
|---|---|---|
| Core mark in an important operating market | Attempt Sunrise registration if eligible | Is Proof of Use ready? Is the extension relevant to customers or fraud risk? |
| Distinctive mark with high impersonation risk | Register or closely monitor during Claims and general availability | Could the label support phishing, fake support, or counterfeit sales? |
| Extension unrelated to the business | Monitor rather than automatically register | Would ownership materially reduce confusion or abuse? |
| Common word shared by many legitimate parties | Review registry rules and likely contention before spending | Do other parties have legitimate rights? Is the mark match exact? |
| Suspicious domain already registered | Preserve evidence and evaluate a dispute route | Is there bad faith, confusion, or a legitimate noncommercial use? |
Base the decision on the mark-to-domain match, Sunrise eligibility, Proof of Use, extension dates, registry policy, evidence of bad faith or confusion, urgency, likely remedy, and business importance. ICANN’s mechanisms define the available processes; they do not decide the facts of an individual dispute.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Respond when someone registers a matching or abusive domain
URS for clear-cut cases
The Uniform Rapid Suspension System (URS) is designed for clear-cut infringement cases. If a complaint is upheld, the domain can be suspended. Suspension is a focused remedy and is not the same as transferring the domain to the trademark holder. Because URS has specific evidentiary and procedural requirements, obtain qualified advice before filing.
Rank #4
- Used Book in Good Condition
UDRP for certain registrant disputes
The Uniform Domain-Name Dispute-Resolution Policy (UDRP) provides arbitration before an approved provider for certain trademark or service-mark claims against a registrant. Its elements, evidence requirements, available remedies, and timing differ from URS. A registrant dispute should be assessed against the facts and the specific domain’s policy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Post-delegation procedure for registry conduct
The Trademark Post-Delegation Dispute Resolution Procedure addresses qualifying complaints about a new gTLD registry operator’s conduct. It is aimed at registry-level behavior, not an ordinary dispute with an individual domain registrant.
| Procedure | Primary target | General purpose |
|---|---|---|
| URS | Clear-cut domain-name infringement | Potential suspension after an upheld complaint |
| UDRP | Registrant in a qualifying trademark or service-mark dispute | Arbitrated dispute resolution under the policy |
| Post-delegation dispute procedure | Qualifying registry-operator conduct | Challenge to registry-level behavior |
These procedures are not interchangeable. Preserve evidence first, identify whether the problem is the registrant or the registry, and obtain qualified legal advice for a specific case.
Common mistakes that weaken protection
- Assuming TMCH blocks every registration. It verifies rights and supports Sunrise and Claims; it is not an automatic blocking system.
- Waiting for one universal launch date. Sunrise and Claims dates vary by TLD and can be updated.
- Submitting Sunrise requests without Proof of Use. Registration evidence alone may not satisfy the Sunrise requirement.
- Assuming every variant is covered. Review the generated labels; typos, translations, and abbreviations may require separate treatment.
- Registering without reading registry rules. Allocation, reserved names, contention, premium pricing, and eligibility are extension-specific.
- Ignoring Claims notices. A notice is an early signal that should enter a documented review process.
- Choosing a remedy by name recognition. URS, UDRP, and registry-conduct procedures address different targets and facts.
- Promising ownership or guaranteed protection internally. Neither a TMCH record nor a Sunrise request guarantees a domain or eliminates infringement.
A launch checklist for brand, legal, and IT teams
- List core marks, products, variants, and priority markets.
- Verify ownership, jurisdiction, goods and services, renewal status, and contact details.
- Collect acceptable public Proof-of-Use materials and the required declaration.
- Submit eligible marks to TMCH and review the resulting matching labels.
- Create a TLD calendar from ICANN’s startup table and each registry’s policy.
- Assign an owner for Sunrise submissions, registrar coordination, and deadlines.
- Set a registration budget and a written threshold for registering versus monitoring.
- Prepare Claims-notice intake, evidence storage, escalation, and customer-protection procedures.
- Monitor DNS, websites, email, advertising, and customer reports after launch.
- For abuse, identify whether URS, UDRP, or a registry-level process fits the facts and seek qualified advice.
What to expect from the 2026 round
The 2026 application round’s more than 1,600 reported applications indicate a substantial pipeline of proposed strings, but that figure does not tell you when any particular extension will be available or whether it will be approved and delegated. Reveal Day, the Replacement Period, and String Confirmation Day describe stages in ICANN’s program. Your operational plan should remain tied to the live Sunrise and Claims dates for the specific TLDs relevant to your marks.
As schedules change, assign someone to recheck the official table before each filing window. A date captured in an internal calendar is a planning aid, not a substitute for the registry’s current notice.
The practical bottom line
Use TMCH to verify eligible rights and support Sunrise and Claims, but treat it as one layer of a broader program. Keep Proof of Use ready, track each TLD’s own dates, register only the names whose risk justifies the cost, review Claims alerts, and match any dispute procedure to the actual target and evidence. That combination gives your team priority opportunities and earlier warnings without claiming protection that the systems do not provide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
