Candidatures / .omg / NA2631T-T98126 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08
.omg
StandardActiveRegistry Services, LLC, US Q1·Q25
Contrôle ultime déclaré : GoDaddy Inc. Q108 · Fiche ICANN ↗
1. Existing Registry Operator and Affiliate of Registrars
2. Affiliated Registrars:
GoDaddy.com, LLC (IANA 146)
Bombora Technologies Pty Ltd (IANA 353)
Wild West Domains, LLC (IANA 440)
Blue Razor Domains, LLC (IANA 612)
Go China Domains, LLC (IANA 1149)
Go Canada Domains, LLC (IANA 1150)
Go Australia Domains, LLC (IANA 1151)
Go Montenegro Domains, LLC (IANA 1152)
Go France Domains, LLC (IANA 1153)
Mesh Digital Limited (IANA 1390)
123-Reg Limited (IANA 1515)
GoDaddy Online Services Cayman Islands Ltd (IANA 1659)
GoDaddy Corporate Domains, LLC (IANA 3786)
§ 1 — Sens de la chaîne Q118·Q120
"omg" is an initialism of the exclamation "oh my God" (or "oh my goodness"), used informally to express strong surprise, shock, excitement, disbelief, or amazement.
/ˌoʊ ɛm ˈdʒiː/
§ 2 — Mission et objet Q133
1. Mission and Purpose of the Applied-for gTLD
"omg" captures a single, instantly recognizable burst of reaction. It is one of the most widely typed expressions of surprise and delight in modern communication, understood across languages and age groups. As a naming layer, .omg gives brands, creators, and campaigns a web address that reads like a reaction rather than a formal label, ideal for moments meant to grab attention, spark sharing, and travel across social feeds. A product reveal, a limited drop, a fan community, a giveaway, or a piece of viral content can live at a name that already signals excitement before anyone clicks. Because the string is short, phonetic, and pre-loaded with emotion, it helps a name feel current, playful, and worth clicking. The purpose of .omg is to give expressive online presences a home: a place where entertainment, e-commerce hype moments, creator content, and reaction-driven marketing can turn a name into something people instantly react to and remember. It positions the address itself as part of the message.
While adjacent expressive or lifestyle namespaces lean on identity or interest, .omg is built specifically for surprise, hype, and delight. It differentiates by making the address itself an exclamation, best deployed at the peak of attention: the reveal, the drop, the "you have to see this" share. This keeps it distinct from descriptive TLDs and positions it as the natural home for anything designed to be reacted to.
Intended Registrants: Consumer brands, entertainment and media companies, content creators, social apps, viral marketing campaigns, event organizers, and individuals seeking a short, expressive, memorable web address.
Related Activities Supporting the Purpose:
• Awareness-building through creators, entertainment partners, and social-first marketing that showcases short, reaction-driven web addresses.
• Registrar distribution aimed at consumer and creator audiences.
• Registrant education on using a compact, expressive name for campaigns, drops, and shareable links.
• Community outreach connecting the string to fan culture, pop culture, and viral moments.
• Responsible registry operations.
2. Sustainability of the Purpose Over Time
The word behind .omg is an act of reaction, and reaction is woven into how people communicate every day. Surprise, delight, and disbelief are among the most reliably expressed human emotions, and shorthand for them spreads quickly and sticks. "omg" earned its cultural footing precisely because it compresses a full emotional beat into three letters that can be spoken, typed, captioned, or exclaimed anywhere. That compactness is what carries it across contexts: text threads, headlines, product launches, sports moments, and comment sections all borrow the same charge.
What reinforces its continued relevance is the way it moves between generations of communication. It began as messaging slang, migrated into everyday speech, then into marketing copy, merchandise, and pop culture reference. Each wave of adoption embeds it more deeply, and its meaning does not depend on any single platform or trend. New audiences learn it the moment they see it used, because the emotion it names is universal and the letters are self-explanatory.
Reaction culture also keeps renewing demand for it. Attention online is driven by moments worth reacting to: reveals, surprises, wins, and shocks. Whenever there is something to be amazed by, there is a need to name that amazement quickly and shareably. A naming layer built on that exact impulse stays useful because the impulse recurs constantly across entertainment, commerce, and social life. The concept is not tied to a fashion in slang that fades; it is tied to the emotion itself, which remains constant even as the vocabulary around it shifts.
§ 3 — Engagements et sauvegardes Q164–Q188
| Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169 | Non à chacune |
|---|---|
| PIC de sauvegarde volontaires Q170·Q171 | Aucun · 90 candidatures de la ronde en proposent |
| Registry Voluntary Commitments Q172·Q173 | Aucun · 5 en proposent |
| Exemption du Code de conduite demandée Q185·Q188 | Non |
§ 4 — Toutes les autres réponses publiées
Toutes les autres réponses que l'ICANN a publiées pour cette candidature, dans l'ordre du formulaire. Les coordonnées (Q17–Q24) sont laissées à la fiche ICANN.
Q199Q2.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO, and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE) of the applying entity, the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Q2.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO, and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE) of the applying entity, the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q200Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).
Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.
Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.
Q121As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.
true
Q223By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true
Q224By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.
true