tld.report · La ronde 2026

Instantané du 8 octobre 2026 · ICANN APS, champs publics

Candidatures / .wix / WIX2694T-T59656 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.wix

TLD de marque · Spec 13Active

Wix.com LTD., IL Q1·Q25

Fiche ICANN ↗

Opérateur de registre, bureau d'enregistrement ou affilié existant, tel que déclaré : Q12

Wix.com is an accredited registrar, IANA 3817.

§ 1 — Sens de la chaîne Q118·Q120

No English translation. "Wix" is a coined, invented brand name and registered trademark of Wix.com Ltd. It has no intended descriptive meaning.

" /wɪks/ Single syllable. Pronunciation: voiced labio-velar approximant /w/ + near-close near-front unrounded vowel /ɪ/ + voiceless velar plosive /k/ + voiceless alveolar sibilant /s/. Rhymes with: fix, mix, six. coined brand term.

§ 2 — Mission et objet Q133

The mission of the .wix top-level domain is to establish and operate a secure, authoritative, and exclusively controlled brand namespace for Wix.com Ltd. and its Affiliates, providing a trusted and cohesive digital identity infrastructure for the company's global product portfolio, corporate communications, and operational systems. Intended Registrants and Users The .wix TLD will be operated as a Specification 13 .Brand TLD in accordance with Section 9.3 of Specification 13 of the Base Registry Agreement. All domain name registrations under .wix will be held exclusively by Wix.com Ltd. and its Affiliates as defined in the Registry Agreement. No third-party registrations will be offered or permitted. The intended users of .wix domains are employees, customers, partners, and developers of Wix.com Ltd. accessing official Wix products, services, and resources through the .wix namespace. Related Activities Wix.com Ltd. was founded in 2006 and is listed on the Nasdaq Global Select Market (ticker: WIX). The company serves over 300 million registered users globally, providing cloud-based website creation, e-commerce, AI-powered application development, and digital business solutions. Its flagship products include Wix Harmony, an AI-driven website builder; Base44, a no-code AI application development platform that reached approximately USD 150 million in annualised recurring revenue as of May 2026; Wix Studio, a professional design platform for agencies and developers; and Wix Payments, an integrated commerce and payment solution. The .wix namespace may be used to host domain names for these and future Wix products, corporate functions, developer infrastructure, regional operations, and investor and press communications. Representative intended uses include: studio.wix, harmony.wix, base44.wix, api.wix, pay.wix, ir.wix, press.wix, careers.wix, security.wix, and docs.wix. Security and Anti-Phishing A further purpose of the .wix TLD is brand security and anti-phishing protection. Wix.com Ltd. currently faces impersonation via lookalike domains used to target its users. Official communications and services originating from domains under .wix will be immediately identifiable as authentic, providing users with a reliable trust signal and reducing the risk of phishing and fraud targeting the Wix user community. Future Growth The .wix namespace is designed to support Wix.com Ltd.'s long-term growth and product expansion. As the company continues to develop AI-powered tools, no-code application platforms, global partner programmes, and new commerce and payments infrastructure, the .wix namespace provides a permanent, scalable, and exclusively controlled digital identity infrastructure that grows with the business. New products and services launched by Wix.com Ltd. and its Affiliates can be immediately and authentically represented under .wix without dependence on third-party TLDs or lookalike domains. Wix.com Ltd. is a publicly listed company with annual revenue of approximately USD 1.99 billion and annual free cash flow of USD 573 million as of FY2025, audited by Kost Forer Gabbay and Kasierer (EY Israel), providing the financial foundation to operate .wix for the duration of the Registry Agreement and well beyond.

§ 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–Q169Non à chacune
PIC de sauvegarde volontaires Q170·Q171Aucun · 90 candidatures de la ronde en proposent
Registry Voluntary Commitments Q172·Q173Aucun · 5 en proposent
Critères de TLD de marque confirmés, certificat de marque joint Q180·Q181Oui · certificat non publié
Confirme que la chaîne n'est pas une « generic string » Q183Oui
Déclaration Spec 11 §3(d) Q184

The applied-for string "wix" does not constitute a "generic string" as defined in Section 3(d) of Specification 11 of the Base Registry Agreement, and accordingly no conflict with Section 3(d) arises. The following sets out the basis for this position and explains how Wix.com Ltd. intends to operate the .wix TLD in a manner fully consistent with the Base Registry Agreement. 1. "wix" is not a generic string Section 3(d) of Specification 11 defines a "generic string" as one "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." "wix" is a coined, invented term with no dictionary meaning in English. It does not denominate or describe any general class of goods, services, groups, organisations or things. It was created as the exclusive brand identifier of Wix.com Ltd. and is used solely to distinguish Wix.com Ltd.'s specific products, services, and business from those of others. This is confirmed by Wix.com Ltd.'s registered trademarks for “WIX”, including USPTO Registration No. 3655335 (registered 14 July 2009), and USPTO Registration No. 5759746 (registered 28 May 2019, being the applicable trademark registration submitted at Q181 and verified through the TMCH SMD file at Q182), reflecting Wix.com Ltd.'s continuous commercial use of the mark 'WIX' since 31 December 2006. Wix.com Ltd. holds numerous additional trademark registrations for "WIX" across multiple jurisdictions globally. The ICANN Applicant Guidebook (V2-2026.04.24, §3.1.7) confirms: ".Brand TLDs do not describe a general class of goods, services, groups, organizations or things and are therefore not subject to the prohibition on closed generics." As a Specification 13 .Brand TLD, .wix falls squarely within this category. 2. Intended operation of .wix under Specification 13 Wix.com Ltd. intends to operate .wix as a Specification 13 .Brand TLD exclusively for the use of Wix.com Ltd. and its Affiliates as defined in the Base Registry Agreement. All domain name registrations in the .wix TLD will be registered to, and maintained by, Wix.com Ltd. for the exclusive use of Wix.com Ltd. and its Affiliates. No registrations will be made available to third parties. This operational model is expressly contemplated and permitted by Specification 13, Section 9.3 of the Base Registry Agreement, which provides that ".Brand TLDs are TLDs where only Registry Operator, its Affiliates or Trademark Licensees are registrants of domain names in the TLD." The restriction of registrations to Wix.com Ltd. and its Affiliates is therefore not a violation of Section 3(d) — it is the defining characteristic of a .Brand TLD as established in the Base Registry Agreement itself. Section 3(d) prohibits a registry operator of a generic string from imposing exclusivity — it does not prohibit a .Brand TLD operator from operating a closed namespace where the string is a coined brand term. The closed generic prohibition exists to protect public access to descriptive generic words, not to prevent a brand owner from operating its own brand namespace. "wix" presents no such concern as it does not belong to, or describe, any general class of goods, services, groups, organizations or things recognisable to the general public independent of the Wix.com Ltd. brand. 3. Conclusion No conflict with Section 3(d) exists or is anticipated. "wix" is a coined brand term exclusively associated with Wix.com Ltd.; operation of .wix as a closed Specification 13 .Brand TLD is expressly provided for under the Base Registry Agreement, and .Brand TLDs are explicitly exempted from the closed generic prohibition. Wix.com Ltd. confirms its obligation to maintain .Brand TLD status and to communicate to ICANN any changes in registration policies that could potentially disqualify the TLD as a .Brand TLD.

§ 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.

Q206Q3.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 the applying entity’s financial statements are provided by a Qualified Parent Entity (QPE), 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: SC3.2-1.1 - As of the submission date of the application, the applying entity is currently a listed member in one or more of the public stock exchanges identified on ICANN’s list from Market Statistics (https://focus.world-exchanges.org/issue/december-2025/market-statistics, as of December 2025), including information on both the relevant exchange and the current registration ticker symbol. SC3.2-1.2 - The applying entity is in good standing with the public stock exchange in which it is a listed member. SC3.2-1.3 - The applying entity commits to the long-term funding of all applied-for gTLD strings. SC3.2-1.4 - 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.

Q3.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 the applying entity’s financial statements are provided by a Qualified Parent Entity (QPE), 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: SC3.2-1.1 - As of the submission date of the application, the applying entity is currently a listed member in one or more of the public stock exchanges identified on ICANN’s list from Market Statistics (https://focus.world-exchanges.org/issue/december-2025/market-statistics, as of December 2025), including information on both the relevant exchange and the current registration ticker symbol. SC3.2-1.2 - The applying entity is in good standing with the public stock exchange in which it is a listed member. SC3.2-1.3 - The applying entity commits to the long-term funding of all applied-for gTLD strings. SC3.2-1.4 - 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.

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.

Q119Script of String

Script of String

Latin

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