Snapshot of 8 October 2026 · ICANN APS, public fields

Applications / .shopify / STUI2650T-T30996 · published by ICANN 7 October 2026 · snapshot 2026-10-08

.shopify

Brand TLD · Spec 13Active

Shopify Technology (USA) Inc., US Q1·Q25

Ultimately controlled by Shopify Inc. Q108 · ICANN record ↗

§ 1 — Meaning of the string Q118·Q120

"shopify" is a coined term that is the brand name for the global commerce company, Shopify Inc. It has no generic dictionary meaning in English.

/ˈʃɒpɪfaɪ/

§ 2 — Mission and purpose Q133

Shopify Inc. (together with its affiliates, "Shopify") is a leading global commerce company whose mission is to make commerce better for everyone. Headquartered in Ottawa, Canada, Shopify provides merchants of all sizes with the tools to start, run, and grow their businesses—including website creation, payment processing, inventory management, shipping, and financial solutions.

The .shopify TLD will be a dotBrand Top-Level Domain (TLD). Every .shopify domain will eliminate the complexity, brand impersonation and abuse risks related to domains in open TLDs, providing internet users and brands the benefits behind a recognized and secure commerce destination.

All .shopify domain registrations will be provided per our registration policies. The TLD will operate to support Shopify’s business activities, including hosting digital experiences for the users of the Shopify platform. Shopify will be the sole registrant and will control the DNS records of all .shopify domains; only we as the registry operator will enable these domains according to our established onboarding flows. Qualified merchants will experience the TLD as users of the Shopify service and hold no rights of registration, transfer, or independent control of any .shopify domains.

.shopify will exist solely to serve the Shopify platform and its users. The TLD will operate as an extension of Shopify's core commerce platform, a global business with a long-established merchant base and the financial and operational resources to support registry operations indefinitely.

Sustainability is inherent in this model as the TLD will be supported by Shopify’s broader commerce platform and its long-term operational resources. This purpose is reinforced by Shopify’s controls consistent with the Shopify Terms of Service; websites on .shopify domains may be suspended or redirected by Shopify at any time, allowing the TLD to be operated in a restricted, controlled, and reliable manner in the long-term.

§ 3 — Commitments and safeguards Q164–Q188

More trustworthy, consumer risk, regulated sector, government reporting, harm, government function Q164–Q169No to each
Voluntary Safeguard PICs Q170·Q171None · 90 applications in the round offer some
Registry Voluntary Commitments Q172·Q173None · 5 do
Brand TLD criteria confirmed, trademark certificate attached Q180·Q181Yes · certificate not published
Confirms the string is not a “generic string” Q183Yes
Spec 11 §3(d) statement Q184

The applicant, Shopify Technology (USA) Inc., affirms that the applied-for string, .shopify, corresponds to a brand with multiple registered trademarks and thus is not a “Generic String” as defined in Specification 11, Section 3(d).

§ 4 — All other published answers

Every other answer ICANN published for this application, in the order of the form. Contact details (Q17–Q24) are left to the ICANN record.

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.

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

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.

Answered with a document. Attachments are not published by ICANN.

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

Q222If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.

If the applying entity wishes to provide any additional information or supporting materials that the applying entity believes may be of interest to the public or relevant to the application, please include them here.

Clarification on Answers to Question #13 and #14: The answer to #13 is correct in that the applicant company, Shopify Technology (USA) Inc., is not any of the following parties: *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 *a Reseller As the answer was “No” to #13, the Question #14 was not available to answer in TAMS. For transparency, we did want to disclose that Shopify Inc., the Ultimate Parent Company of its affiliate, Shopify Technology (USA) Inc., does resell domains through the registrar Tucows (SRS).

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