Application Details

Last published on: 7 October 2026 at 15:37 UTC

Application Type: New gTLD

Primary String: wix

TLD Types: Brand

Application ID: WIX2694T-T59656

Application Priority Number: --

Application Status: Active

Processing Stage: Pre-Evaluation Processing

Comment Period: --

View:

Summary Responses Clarifying Questions Change Requests Documents Objections

Application Responses

Section: Applying Entity Information

This question set collects information regarding the legal entity that would enter into a Registry Agreement with ICANN upon successful completion of all relevant application processes. The information collected is intended to be used for background screening.

AGB Q1. Full Legal Name

Provide the full legal name of the applying entity as it appears on the official registration documents. Do not use abbreviations.

Wix.com LTD.

AGB Q2. Doing Business As

Provide the name under which the applying entity is doing business, if different from the full legal name answered in Question 1. Such a name must be registered with appropriate local jurisdiction or public authority.

Wix.com

AGB Q3. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the applying entity as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation. No additional information should be provided as this will be used for the automatic population of the Registry Agreement.

Wix.com LTD.

AGB Q4. Jurisdiction

The jurisdiction indicates the location in which the business of the applying entity is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the applying entity is registered. No additional information should be provided as this will be used for the automatic population of the Base Registry Agreement. Examples include "Delaware", "Germany", etc.

Israel

AGB Q10. Website URL

Provide the website URL of the applying entity, if available.

https://wix.com

AGB Q11. Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?

1. Choose Yes or No. 2. Use the definition of Affiliate from the Base Registry Agreement (see https://www.icann.org/en/registry-agreements/base-agreement).

true

AGB Q12. If "Yes", explain.

1. Specify if the applying entity is an existing registry operator, ICANN accredited registrar, and/or an Affiliate of a registry operator and/or registrar. 2. If the applying entity is an Affiliate, provide the details of such Affiliate relationship, including the name of the affiliated registry operator and/or registrar. 3. If the applying entity is an ICANN accredited registrar, specify the registrar ID number.

Wix.com is an accredited registrar, IANA 3817.

AGB Q13. Is the applying entity a back-end registry service provider (RSP), an ICANN-approved data escrow agent, an emergency back-end registry operator, a Uniform Rapid Suspension (URS) service provider, an ICANN dispute resolution service provider, a Privacy or Proxy Service Provider, or a Reseller?

Choose Yes or No.

false

AGB Q15. Stock Symbol

1. If the applying entity is publicly traded, provide its stock symbol. 2. If the applying entity is traded under multiple symbols/tickers, provide the symbol of the entity's primary equity listing that has the most units outstanding.

WIX

AGB Q16. Stock Exchange

1. If the applying entity is publicly traded, select the Stock Exchange with which the applying entity is listed. 2. If the applying entity is traded on multiple exchanges, provide the exchange of the entity's primary equity listing.

Nasdaq US

AGB Q17. Phone Country Code

972

AGB Q18. Primary Business Phone

Provide the primary business phone number without including the country code.

525244194

AGB Q19. Primary Business Email Address

Provide the primary business email address of the applying entity.

legal@wix.com

AGB Q20. Address Line 1

Enter the street address (no PO Box).

Yunitsman 5 St.

AGB Q22. Locality

Enter the city, village, municipality, etc.

Tel Aviv

AGB Q23. State/Province/Region

Enter the state, province, department, territory, prefecture, oblast, etc., if applicable.

Israel

AGB Q24. Postal Code

1. Enter the postal code, if applicable. 2. If a postal code does not exist, type “Not Applicable”.

6936025

AGB Q25. Country Code of Location

AGB Q26. Full Legal Name

If applicable, provide the full legal name as it appears on the official registration documents of the Direct Parent Company of the applying entity. Do not use abbreviations.

Wix.com LTD.

AGB Q27. Doing Business As

Provide the name under which the Direct Parent Company is doing business, if different from the full legal name answered in Question 26. Such a name must be registered with appropriate local jurisdiction or public authority.

Wix.com

AGB Q28. Legal Entity Form/Business Structure

Provide the long form (no acronyms) of the legal entity form/business structure of the Direct Parent Company as it appears on the official registration documents. If the original script of the legal entity form/business structure is not English, ONLY provide its official English translation.

Wix.com LTD.

AGB Q29. Jurisdiction

The jurisdiction indicates the location in which the business of the Direct Parent Company is registered for legal and financial purposes. This is either 1) a country name, or a 2) state/territory name, depending on where the Direct Parent Company is registered. Examples include "Delaware", "Germany", etc.

Israel

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Provide a single document for Self-Certification question AGB Q221, Q5.2-1. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. Do not modify any of the Self-Certification statements. If the applicant cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.

AGB Q221. 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.

1. Provide a single document for Self-Certification question Q5.2-1. 2. The document must include only the SC5.2-1.1 through SC5.2-1.7 statements. 3. Do not modify any of the Self-Certification statements. 4. If the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements, provide a document that explains why the applying entity cannot Self-Certify the SC5.2-1.1 through SC5.2-1.7 statements.

Has Documents

Section: Primary String

This question set collects basic information regarding the string that is being applied for (for example, a-label, meaning, script). If the applying entity opts to designate a replacement string, it must answer the same set of questions for the replacement string from the AGB Question Set 5 on.

AGB Q116. Applied-for Primary String (ASCII Label)

wix

AGB Q118. What is the meaning/definition of the applied-for gTLD string?

Provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applying entity. If there is no literal meaning in English (for example, a brand name or a proper noun without a translation) simply state "No English Translation"

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

AGB Q119. Script of String

If an IDN, provide the script of the string (both in English and as referenced by the RZ-LGR/ISO 15924)

Latin

AGB Q120. Phonetic Representation

Provide a representation of the string according to the International Phonetic Alphabet.

" /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.

AGB Q121. 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.

Confirm the statement using a checkbox.

true

AGB Q133. What is the mission and purpose of the applied-for gTLD?

1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 1a. If applying for a variant of an existing gTLD, please also describe the mission and purpose of the existing gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose. 2. Explain how this purpose is sustainable over time.

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.

Section: Safeguard Identification

This question set collects information related to determining whether certain Safeguard Public Interest Commitments (Safeguard PICs) are required for the applied-for gTLD string. See Section 7.8.2.3 Safeguard PICs. Answers to these questions will inform assessment by ICANN on whether and which Safeguard PICs must be incorporated in the applicable Registry Agreement (RA) if the string proceeds to delegation. The answers themselves will not automatically make such a determination.

AGB Q164. Will people see a domain name as more trustworthy because it is registered in your TLD? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. 2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

AGB Q165. Is it likely that consumers will face significant risks if domain names in the TLD(s) in the application are abused? Think about how people around the world will understand the TLD string(s) in the application, including literal and informal meanings in different languages and regions.

AGB Q166. Would people generally think that this TLD will be used by entities that require strict licensing or accreditation to do business? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q167. Would most people think that (domains in) the TLD(s) in the application are used for activities that require regular government reporting, inspections, and oversight in various countries? Think about how the TLD string(s) in the application will be understood around the world, including both literal and informal meanings in different languages and regions.

AGB Q168. Could people reasonably believe that (domains in) your TLD will cause or lead to harassment, harm, aggression, complaints, criticism, distress, or embarrassment? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

AGB Q169. Would most people think that the TLD is used for something usually done by governments? Think about how the TLD string(s) in the application will be understood globally, including different languages and cultures.

1. When answering the questions, apply criteria by considering the meaning of the requested TLD string in the following contexts: a. Literally as described in the application b. Literally in any other language in which the string is a recognized word or phrase. c. Informally in any language or regional variant, where alternative meanings exist. I-2. If the proverbial “reasonable person” who understands the relevant context believes that the question should be answered ‘yes’, then the answer is yes.

AGB Q170. Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Registry Agreement (RA) voluntarily regardless of ICANN’s Safeguard Assessment outcomes?

Select Yes or No. Notes: 1. ICANN will evaluate whether an applied-for gTLD string requires one or more Safeguard Public Interest Commitments (Safeguard PICs) to be included in the Base RA). 2. In addition to the Mandatory Public Interest Commitments (PICs) that must be included in each Base RA, a subset of Base RAs must include Safeguard PICs based on ICANN’s Safeguard Assessment. See Section 7.8.2.3 Safeguard PICs. 3. Applying entities for TLDs that are not found to require Safeguard PICs can elect to add them to the applicable Base RAs voluntarily to, for example, further their business objectives, help address issues or concerns that are raised or could be raised with respect to their applications, or avoid the need for the evaluation and implementation of customized Registry Voluntary Commitment (RVC). See Section 7.8.3 Registry Voluntary Commitments (RVCs).

Section: Registry Voluntary Commitments (RVCs)

This question set collects information related to any Registry Voluntary Commitments (RVCs) that the applying entity is submitting. The decision to submit an RVC is typically voluntary, except for those recognized by ICANN to resolve an objection or to address GAC Consensus Advice. See Section 7.8.3 Registry Voluntary Commitments for more information.

AGB Q172. Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Registry Agreement (RA) that are unique to your applied-for string?

1. Select Yes or No. 2. In addition to Safeguard Public Interest Commitments (PICs), an applying entity will be permitted to propose one or more Registry Voluntary Commitments (RVCs) to provide additional safeguards with regard to the registry operator’s operation of an applied-for gTLD string. See Section 7.8.3 Registry Voluntary Commitments (RVCs). 3. RVCs are separate from Community Registration Policies. See Section 7.8.3 Registry Voluntary Commitments (RVCs) and Section 7.8.4 Community Registration Policies for more information. If you are applying for a Community gTLD, please submit the Community Registration Policies by answering Questions 150-155. However, if you propose to include additional Registry Voluntary Commitments in the RA beyond the Community Registration Policies, you may answer "yes" and proceed to answer the following questions. 4. You are encouraged to consider whether there are other means, separate from including commitment(s) in the Base RA, that could be used to further your business objectives or help resolve any anticipated or actual issue(s) raised regarding the applied-for gTLD string or application. See Section 7.8.3 Registry Voluntary Commitments (RVCs). Notes: If you select “yes” to this question, you are required to pay the conditional Registry Commitments Evaluation fee, and commitments that are approved by ICANN will be included in Specification 11 of the applicable Base RA as specific voluntary public interest commitments as contractual obligations.

Section: Brand & Code of Conduct Exemptions

This question set collects information related to whether the applied-for gTLD string is a .Brand (see Section 7.3) or if the applying entity is seeking a Code of Conduct exemption (see Section 7.4).

AGB Q179. Are you applying for a Brand TLD?

Select Yes or No

Yes

AGB Q180. The applying entity confirms that the applied-for gTLD string meets the Brand TLD criteria as described in Section 9.3 of Specification 13. The applying entity also confirms their understanding of contractual obligation to maintain Brand TLD status and communicate changes in registration policies that could potentially disqualify the TLD as a Brand TLD.

Select Yes or No. Notes: If the applying entity selects “no,” it will be required to provide additional documentation describing which criteria is not met as well as a justification for the TLD to nonetheless qualify as a .Brand TLD.

Yes

AGB Q181. Submit Trademark Certificate

Attach an accurate and complete copy of the applicable trademark registration that forms the basis of the request for .Brand TLD qualification.

Has Documents

AGB Q183. The applying entity confirms that this applied-for string is not a “generic string” as defined in Section 3(d) of Specification 11 of the Base RA, which prohibits generic TLDs from being operated on an exclusive basis.

Confirm statement with a checkbox.

true

AGB Q184. No Specification 11 Conflicts

Explain how the applying entity intends to operate the TLD such that there would not exist any such conflict with Section 3(d) of Specification 11.

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.

Application Details

Application Responses

Section: Applying Entity Information

Section: Applying Entity Background and Organization

Section: Self-Certification

Section: Security Policy and Planning

Section: DNS Abuse

Section: Primary String

Section: Safeguard Identification

Section: Registry Voluntary Commitments (RVCs)

Section: Brand & Code of Conduct Exemptions

Section: Additional Information and Supporting Materials

Section: Bona Fide Intent and Prohibited Communications