Topic starter
11/11/2026 6:05 pm
TL;DR: Applied-for gTLD strings and applicant details become visible on String Reveal Day, MarkMonitor reports, creating a deadline-driven review point for brands. Domain, legal and security teams then need to decide which terms justify monitoring, objection or defensive registration.
Editorial analysis by NHI Mgmt Group, based on content published by MarkMonitor: “Why ICANN String Reveal Day Matters to Every Brand Holder”.
Key questions
Q: Why does a confusingly similar domain string create brand risk?
A: A confusingly similar domain string creates brand risk because it can impersonate a trusted name, divert traffic, and support phishing or fraud through lookalike registration.
Q: How does the Trademark Clearinghouse support new gTLD monitoring?
A: The Trademark Clearinghouse supports new gTLD monitoring by giving trademark holders a central record used for claims notices and sunrise eligibility.
Q: What signs suggest a new gTLD string should be escalated?
A: Escalate a new gTLD string when it is identical or confusingly similar to a core mark, resembles a product or support channel, or appears to fit a suspicious business model.
Practitioner guidance
- Define the review universe List the trademarks, product names, brand names and priority terms that will be checked against the revealed strings.
- Assign decision owners early Name the internal reviewers and external advisors who will assess applications, recommend action and approve time-sensitive responses.
- Set escalation thresholds Predefine when a string triggers monitoring, defensive registration, formal objection or no action so decisions stay consistent under deadline pressure.
Bottom line: Public string disclosure changes brand protection from speculation to evidence-based triage.
Glossary terms: gTLD, Contention Set, Legal Rights Objection, Trademark Clearinghouse
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:06 pm
String reveal is a governance event, not a filing update. The important shift is that rights holders move from speculation to evidence once applicants, variants and contention sets are public. That changes the decision model from broad watching to selective action, because teams can test whether a string creates legal, commercial or trust exposure before launch pressure builds. Practitioners should treat the reveal as the moment to rank risks, not to close them.
A question worth separating out:
Q: What is the best way to organise cross-functional domain review?
A: The best way to organise cross-functional domain review is to use a single approval workflow that includes legal, brand, security, and DNS or infrastructure owners. That review should check trademark exposure, spoofing risk, delegation changes, registrar access, renewal status, and dispute handling. Clear ownership and a documented escalation path prevent unreviewed registrations and conflicting decisions.
👉 Read our full editorial: String reveal day makes gTLD applications actionable for brand owners