I will not be paying a dime. -Albert Lane, United States of America 🖕

ICANN New gTLD application · .albertlane · prefilled reference copy

Albert Lane - Founder, COO, AI SI Relator

Reference copy, not a submission This page is a public, prefilled copy of ICANN’s application questions, kept for reference. It has not been filed with ICANN, and nothing on this page submits anything. Real applications are made only through ICANN’s TLD Application Management System (TAMS) portal while an application round is open.

Fee (set by ICANN): the 2026 Round gTLD evaluation fee is USD 227,000 per application (ICANN gTLD Evaluation Fee FAQ; Applicant Guidebook V3-2026.10.07, §1.1.2 and §3.3). A .Brand designation adds a separate USD 500 .Brand TLD Eligibility Evaluation fee (ICANN FAQ). For comparison, the 2012 round fee was USD 185,000 (2012 Applicant Guidebook, §1.5.1).
Timing: the 2026 Round submission window ran 30 April – 12 August 2026 (23:59 UTC) and is closed. ICANN sets the dates and fee of any later round.
Eligibility notes from the Guidebook: the applicant must be a legal entity (“natural persons and sole proprietorships do not qualify”), and a .Brand TLD needs a registered trademark plus Trademark Clearinghouse Signed Mark Data. Those items are marked [Albert to provide] below.

What is prefilled

Applicant (person)	Albert Lane (applying legal entity: [Albert to provide])
Address	Homeless
Country	United States of America (US)
Applied-for string	.albertlane (so https://albertlane can one day be its own apex domain)
Application type	.Brand TLD (Specification 13), closed, single-registrant
Mission / purpose	Personal brand of Albert Lane and ${ALDI}^{x}$ TV™
Website	albertlane.net
X	@AlbertLane_net

20 of 225 questions prefilled with known facts, 37 marked N/A or intended-model, 168 left as [Albert to provide] (legal entity and registration documents, parent companies, users’ personal details, payment and banking, directors/officers/shareholders, attestations, trademark and TMCH files, safeguard and RVC answers, registry service provider and registry services, financial profile and statements, operational self-certifications, volume refund election).

Full application question set (225 questions, 22 sets)

Source: ICANN New gTLD Program 2026 Round Applicant Guidebook, version V3-2026.10.07 (7 October 2026), Appendix 1 Application Questions. Question wording is ICANN’s; TAMS shows only the sets that apply to an application, so conditional sets (Community, Geographic, financial profiles) are listed for completeness. Instructions and criteria for each question are in the source.

Question Set 1: Applying Entity Information

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
1	Applying Entity	Full Legal Name	Yes	[Albert to provide]
2	Applying Entity	Doing Business As	Yes	[Albert to provide]
3	Applying Entity	Legal Entity Form/Business Structure	Yes	[Albert to provide]
4	Applying Entity	Jurisdiction	Yes	[Albert to provide]
5	Applying Entity	Tax ID, Business ID, VAT Registration Number, or Equivalent	No	[Albert to provide]
6	Applying Entity	Issuing Authority	No	[Albert to provide]
7	Applying Entity	Legal Entity Identifier (LEI)	No	[Albert to provide]
8	Applying Entity	Proof of Establishment	No	[Albert to provide]
9	Applying Entity	Proof of Good Standing	No	[Albert to provide]
10	Applying Entity	Website URL	Yes	https://albertlane.net
11	Applying Entity	Is the applying entity an existing registry operator, ICANN accredited registrar, or an Affiliate of either?	Yes	[Albert to provide]
12	Applying Entity	If "Yes", explain.	Yes	[Albert to provide]
13	Applying Entity	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?	Yes	[Albert to provide]
14	Applying Entity	If the applying entity is an Affiliate of any of the entities listed in Question 13, explain.	Yes	[Albert to provide]
15	Stock and Exchange	Stock Symbol	Yes	[Albert to provide]
16	Stock and Exchange	Stock Exchange	Yes	[Albert to provide]
17	Primary Business Phone	Phone Country Code	Yes	[Albert to provide]
18	Primary Business Phone	Primary Business Phone	Yes	[Albert to provide]
19	Primary Business Email Address	Primary Business Email Address	Yes	lane.albert@pm.me (public contact on albertlane.net)
20	Primary Business Address	Address Line 1	Yes	Homeless (ICANN asks for a street address, no PO Box)
21	Primary Business Address	Address Line 2	Yes	[Albert to provide]
22	Primary Business Address	Locality	Yes	[Albert to provide]
23	Primary Business Address	State/Province/Region	Yes	[Albert to provide]
24	Primary Business Address	Postal Code	Yes	[Albert to provide]
25	Primary Business Address	Country Code of Location	Yes	US (United States of America)
26	Direct Parent Company	Full Legal Name	Yes	[Albert to provide]
27	Direct Parent Company	Doing Business As	Yes	[Albert to provide]
28	Direct Parent Company	Legal Entity Form/Business Structure	Yes	[Albert to provide]
29	Direct Parent Company	Jurisdiction	Yes	[Albert to provide]
30	Direct Parent Company	Address Line 1	No	[Albert to provide]
31	Direct Parent Company	Address Line 2	No	[Albert to provide]
32	Direct Parent Company	Locality	No	[Albert to provide]
33	Direct Parent Company	State/Province/Region	No	[Albert to provide]
34	Direct Parent Company	Postal Code	No	[Albert to provide]
35	Direct Parent Company	Country Code of Location	No	[Albert to provide]
36	Ultimate Parent Company	Full Legal Name	Yes	[Albert to provide]
37	Ultimate Parent Company	Doing Business As	Yes	[Albert to provide]
38	Ultimate Parent Company	Legal Entity Form/Business Structure	Yes	[Albert to provide]
39	Ultimate Parent Company	Jurisdiction	Yes	[Albert to provide]
40	Ultimate Parent Company	Address Line 1	No	[Albert to provide]
41	Ultimate Parent Company	Address Line 2	No	[Albert to provide]
42	Ultimate Parent Company	Locality	No	[Albert to provide]
43	Ultimate Parent Company	State/Province/Region	No	[Albert to provide]
44	Ultimate Parent Company	Postal Code	No	[Albert to provide]
45	Ultimate Parent Company	Country Code of Location	No	[Albert to provide]
46	Ultimate Parent Company	Graphical Representation of Ownership	No	[Albert to provide]
47	Applying Entity	After reviewing the Base Registry Agreement, does the applying entity believe there are any unique legal, jurisdictional, or regulatory issues that would prevent the applying entity from executing the agreement as-is? As the Registry Agreement is a product of extensive community consultation, ICANN only considers modification to it in extraordinary circumstances.	No	[Albert to provide]
48	Applying Entity	If the applying entity answered yes to the above Question #47, please briefly explain.	No	[Albert to provide]

Question Set 2: Users

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
49	Primary User	Full Legal Name	No	Albert Lane
50	Primary User	Address Line 1	No	Homeless
51	Primary User	Address Line 2	No	[Albert to provide]
52	Primary User	Locality	No	[Albert to provide]
53	Primary User	State/Province/Region	No	[Albert to provide]
54	Primary User	Postal Code	No	[Albert to provide]
55	Identifying Information	Country Code of Business Location/Address	No	US
56	Identifying Information	Year of Birth	No	[Albert to provide]
57	Identifying Information	Phone Country Code	No	[Albert to provide]
58	Identifying Information	Phone Number	No	[Albert to provide]
59	Identifying Information	Email Address	No	lane.albert@pm.me
60	Identifying Information	Country Code of Residence	No	US
61	Identifying Information	Percentage of Shares	No	[Albert to provide]
62	Identifying Information	Organization Title in the Applying Entity	No	[Albert to provide]
63	Identifying Information	Does this user hold the position of Director, Officer, or some other position of significant influence? If yes, please list the title.	No	[Albert to provide]
64	Identifying Information	Is this user a Signatory Officer of the applying entity?	No	[Albert to provide]

Question Set 3: Payments

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
65	Payor	Full Legal Name	No	[Albert to provide]
66	Payor	Doing Business As (If Applicable)	No	[Albert to provide]
67	Payor	Legal Entity Form/Business Structure (If Applicable)	No	[Albert to provide]
68	Payor	Jurisdiction (If applicable)	No	[Albert to provide]
69	Payor Primary Business Address	Address Line 1	No	[Albert to provide]
70	Payor Primary Business Address	Address Line 2	No	[Albert to provide]
71	Payor Primary Business Address	Locality	No	[Albert to provide]
72	Payor Primary Business Address	State/Province/Region	No	[Albert to provide]
73	Payor Primary Business Address	Postal Code	No	[Albert to provide]
74	Payor Primary Business Address	Country Code of Location	No	[Albert to provide]
75	Financial Institution	Financial Institution Name	No	[Albert to provide]
76	Financial Institution	Beneficiary Name	No	[Albert to provide]
77	Financial Institution	Address Line 1	No	[Albert to provide]
78	Financial Institution	Address Line 2	No	[Albert to provide]
79	Financial Institution	Locality	No	[Albert to provide]
80	Financial Institution	State/Province/Region	No	[Albert to provide]
81	Financial Institution	Postal Code	No	[Albert to provide]
82	Financial Institution	Country Code of Location	No	[Albert to provide]
83	Financial Institution	Legal Entity Form/Business Structure	No	[Albert to provide]
84	Financial Institution	Jurisdiction	No	[Albert to provide]
85	Financial Institution	Transit/Domestic Routing Number	No	[Albert to provide]
86	Financial Institution	IBAN	No	[Albert to provide]
87	Financial Institution	SWIFT Code	No	[Albert to provide]
88	Financial Institution	Account Number	No	[Albert to provide]
89	Financial Institution	Account Type	No	[Albert to provide]
90	Financial Institution	Account Category	No	[Albert to provide]
91	Billing Point of Contact	Full Legal Name	No	[Albert to provide]
92	Billing Point of Contact	Address Line 1	No	[Albert to provide]
93	Billing Point of Contact	Address Line 2	No	[Albert to provide]
94	Billing Point of Contact	Locality	No	[Albert to provide]
95	Billing Point of Contact	State/Province/Region	No	[Albert to provide]
96	Billing Point of Contact	Postal Code	No	[Albert to provide]
97	Billing Point of Contact	Country Code of Business Location/Address	No	[Albert to provide]
98	Billing Point of Contact	Country Code of Residence	No	[Albert to provide]
99	Billing Point of Contact	Year of Birth	No	[Albert to provide]
100	Billing Point of Contact	Phone Country Code	No	[Albert to provide]
101	Billing Point of Contact	Phone Number	No	[Albert to provide]
102	Billing Point of Contact	Email Address	No	[Albert to provide]
103	Billing Point of Contact	Organization Title in the Applying Entity	No	[Albert to provide]

Question Set 4: Applying Entity Background and Organization

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
104	Directors	List all directors of the applying entity.	Partial - Names Only	[Albert to provide]
105	Officers/ Partners	List all officers & partners of the applying entity.	Partial - Names Only	[Albert to provide]
106	Material Shareholders	List all Material Shareholders	Partial - Names Only	[Albert to provide]
107	Executive Responsibility	List Individuals with Executive Responsibility	Partial - Names Only	[Albert to provide]
108	Ultimate Control	Disclose Ultimate Control of applying entity	Yes	[Albert to provide]
109	Attestations	I have read and understood the New gTLD Program Eligibility Criteria in Applicant Guidebook Section 6.1.2.1 and declare that neither the applying entity nor any of the individuals named within the Organizational Account Record are subject to any of the Eligibility Criteria listed in Section 6.1.2.1 .	No	[Albert to provide]
110	Attestations	Confirm that neither the applying entity, nor any individuals or entities named within the Organizational Account in their current capacity or as part of a previous entity over which they had ownership or control, have been subject to any decisions indicating involvement in cybersquatting, as defined in the Uniform Domain Name Dispute Resolution Policy (UDRP), Anti-cybersquatting Consumer Protection Act (ACPA), or equivalent legislation. This includes engagement in reverse domain name hijacking under the UDRP or bad faith or reckless disregard under the ACPA or equivalent legislation within the last ten years.	No	[Albert to provide]
111	Attestations	If "No," please explain.	No	[Albert to provide]
112	Attestations	Confirm that neither the applying entity nor any of the individuals named in the Organizational Account Record – either in their current capacity or as part of a previous entity over which they had ownership or control – has been subject to a final determination by a dispute resolution provider or a court of competent jurisdiction for intellectual property infringement related to registration or use of a domain name within the last ten years.	No	[Albert to provide]
113	Attestations	If "No" please explain.	No	[Albert to provide]
114	Attestations	Confirm that the applying entity and individuals or entities named within the Organizational Account, either in their current capacity or as part of a previous entity over which they had ownership or control, have not been subject to a final determination related to the Uniform Rapid Suspension System (URS) Policy or Post-Delegation Dispute Resolution Procedures (PDDRP).	No	[Albert to provide]
115	Attestations	If "No," please explain.	No	[Albert to provide]

Question Set 5: Applied-for String

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
116	Primary String	Provide the applied-for gTLD string.	Yes	albertlane (.albertlane)
117	Primary String	If the above string is an IDN, provide the U-label and code points for the above string.	Yes	Not an IDN (ASCII only; A-label = U-label = albertlane)
118	Primary String	What is the meaning/definition of the applied-for gTLD string?	Yes	The name of Albert Lane, used as his personal brand (albertlane.net, ${ALDI}^{x}$ TV™, X @AlbertLane_net).
119	Primary String	Script of String	Yes	Latin
120	Primary String	Phonetic Representation	Yes	AL-bert LAYN
121	Primary String	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.	Yes	[Albert to provide]

Question Set 6: Variant String(s) (Optional)

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
122	Variant String(s)	If applicable, provide the string that is the variant of the above gTLD string that the applying entity also wishes to apply for.	Yes	N/A — no variant strings applied for
123	Variant String(s)	If the above string is an IDN, provide the U-label and code points for the above variant string.	Yes	N/A — no variant strings applied for
124	Variant String(s)	Script of Variant String	Yes	N/A — no variant strings applied for
125	Variant String(s)	Is this variant string for an existing gTLD that is already operated by the applying entity or for a newly applied-for string in the 2026 Round?	Yes	N/A — no variant strings applied for
126	Variant String(s)	What is the meaning/definition of the variant string?	Yes	N/A — no variant strings applied for
127	Variant String(s)	Explain how the primary applied-for and variant strings are considered the same, including the meaning, by the relevant user communities.	Yes	N/A — no variant strings applied for
128	Variant String(s)	Explain the benefits and the user communities who will benefit from the introduction of the applied-for variant string(s).	Yes	N/A — no variant strings applied for
129	Variant String(s)	Describe the steps that the applying entity will take to minimize the operational and management complexities of variant gTLDs and variant domain names that impact registrars, resellers and/or registrants.	Yes	N/A — no variant strings applied for
130	Variant String(s)	This applied-for string is not a “generic string” using the definition of "generic string" in Section 3(d) of Specification 11 of the Base RA (as described in Question 121).	Yes	N/A — no variant strings applied for

Question Set 7: Community gTLDs

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
131	Community (General)	Is this application for a Community gTLD?	Yes	No (.Brand application)
132	Community (General)	What community will the applied-for string serve?	Yes	N/A — not a Community gTLD
133	Mission & Purpose ( General, required of all applying entities )	What is the mission and purpose of the applied-for gTLD?	Yes	A closed, single-registrant .Brand (Specification 13) TLD for the personal brand of Albert Lane: the home of ${ALDI}^{x}$ TV™ and albertlane.net. Every second-level name would be registered to and used only by the registry operator (no third-party registrations, no public sale), so that https://albertlane can one day work as its own apex domain.
134	Community (General)	How would you categorize your community?	Yes	N/A — not a Community gTLD
135	Community (Organization)	What is the applying entity’s connection to the community?	Yes	N/A — not a Community gTLD
136	Community (Organization)	How is the community organized? Are there one or multiple organizations (“organizing body”) that represent or administer the community?	Yes	N/A — not a Community gTLD
137	Community (Organization)	Does the community have defined membership requirements, such as registration, licensing, or use of specific communication? Or, do community members self-identify as part of the community?	Yes	N/A — not a Community gTLD
138	Community (Organization)	Where is the community located?	Yes	N/A — not a Community gTLD
139	Community (Organization)	What is the estimated size of the community? This should take into account any regions listed in Question 138.	Yes	N/A — not a Community gTLD
140	Community (Organization)	What portion of the community do any organizing bodies represent or administer to?	Yes	N/A — not a Community gTLD
141	Community (Engagement)	Do the organizing bodies demonstrate active and consistent efforts to engage and connect with the identified community and its members?	Yes	N/A — not a Community gTLD
142	Community (Engagement)	What is the role of the applying entity in the engagement efforts listed in Question 141?	Yes	N/A — not a Community gTLD
143	Community (Awareness)	Are community members aware of the identified community and each other?	Yes	N/A — not a Community gTLD
144	Community (Awareness)	Are community members aware of the applying entity and its intention to apply for a Community gTLD?	Yes	N/A — not a Community gTLD
145	Community (Established Presence)	Was there an established presence of the identified community prior to the opening of the application submission period?	Yes	N/A — not a Community gTLD
146	Community (Established Presence)	Are individuals and groups outside of the identified community aware of the existence of the identified community?	Yes	N/A — not a Community gTLD
147	Community (Longevity)	Are the pursuits of the identified community enduring and sustainable?	Yes	N/A — not a Community gTLD
148	Community (Nexus)	Does the string match the name of the identified community?	Yes	N/A — not a Community gTLD
149	Community (Nexus)	Will the general public instinctively think of the community when thinking of the applied-for string?	Yes	N/A — not a Community gTLD
150	Community (Community Registration Policy - General)	Are you proposing to include one or more Community Registration Policies in the Base RA that are unique to the applying entity’s applied-for Community gTLD?	Yes	N/A — not a Community gTLD
151	Community (Community Registration Policy - Eligibility; RCE Criteria 1, 2 & 3)	Please state a specific Community Registration Policy with respect to registration eligibility for community members.	Yes	N/A — not a Community gTLD
152	Community (Community Registration Policy - Name Selection; RCE Criteria 1, 2 & 3)	State a specific Community Registration Policy with respect to name selection criteria or rules for the applied-for string.	Yes	N/A — not a Community gTLD
153	Community (Community Registration Policy - Other; RCE Criteria 1, 2 & 3)	State a specific Community Registration Policy with respect to an additional commitment besides registration eligibility for community members and naming selection criteria or rules for the applied-for string.	Yes	N/A — not a Community gTLD
154	Community (Community Registration Policy; RCE Criterion 3)	Explain the rationale for any limitations to the Community Registration Policy proposed by the applying entity in Questions 151-153.	Yes	N/A — not a Community gTLD
155	Community (Community Registration Policy; RCE Criteria 4 & 5)	Explain how the proposed Community Registration Policies of the applying entity meet the Registry Commitments Evaluation criteria 4 and 5.	Yes	N/A — not a Community gTLD
156	Community (Community Endorsement)	From where does the applying entity have the support to run the applied-for string on behalf of the identified community?	Yes	N/A — not a Community gTLD
157	Community (Community Endorsement)	Is there any opposition to the applying entity, application, or applied-for string that the applying entity is aware of? If yes, please explain.	Yes	N/A — not a Community gTLD

Question Set 8: Geographic Names

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
158	Geographic Name (Geographic Application)	Is the applied-for string a geographic name as defined by it being any one of the following: a) the capital city name of a country or territory listed in the ISO 3166-1 standard; b) a city name, where it is clear from statements in the application that the applying entity intends to use the gTLD for purposes associated with the city name; c) a sub-national place name listed in the ISO 3166-2 standard; or d) Strings listed as UNESCO regions or appearing on the Geographic Regions section of the “Standard country or area codes for statistical use (M49) ( https://unstats.un.org/unsd/methodology/m49/ )”	Yes	No (a personal name, not a capital, city, region or country name)
159	Geographic Terms (Geographic Application)	Is the applied-for string the name of a city and, if so, is the intention to use the TLD primarily for purposes associated with the city name?	Yes	No
160	Geographic Terms (Geographic Application)	If answered yes to the previous question, how will the applying entity market and/or use the TLD primarily for purposes associated with the city name?	Yes	N/A — not a geographic name
161	Geographic Terms (Support and Non- Objection)	Provide letters of support or non-objection from relevant government entity or public authority.	No	N/A — not a geographic name

Question Set 9: Reserved Names

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
162	Reserved Name (Reserved Name)	Is the applied-for string or any applied-for variant a Reserved Name per Section 7.2.2.2 Reserved Names Identification ?	Yes	[Albert to provide]
163	Reserved Name (Reserved Name)	If the applied-for string or any applied-for variant is a Reserved Name, provide justification and supporting materials as required in Section 7.2.2.2.1 Exception Process to Apply for Reserved Names .	Yes	[Albert to provide]

Question Set 10: Safeguard Assessment/Mission and Purpose

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
164	Safeguard Identification (Group 1)	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.	Yes	[Albert to provide]
165	Safeguard Identification (Group 1)	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.	Yes	[Albert to provide]
166	Safeguard Identification (Group 2)	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.	Yes	[Albert to provide]
167	Safeguard Identification (Group 2)	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.	Yes	[Albert to provide]
168	Safeguard Identification (Group 3)	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.	Yes	[Albert to provide]
169	Safeguard Identification (Group 4)	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.	Yes	[Albert to provide]
170	Registry Voluntary Commitments (Safeguard Voluntary Selection)	Are you proposing to include one or more of the Safeguard Public Interest Commitments (Safeguard PICs) in the Base RA voluntarily regardless of ICANN’s Safeguard Assessment outcomes?	Yes	[Albert to provide]
171	Registry Voluntary Commitments (Safeguard Voluntary Selection)	If Yes, which Safeguard PIC(s) are you proposing to include in the RA?	Yes	[Albert to provide]

Question Set 11: Registry Voluntary Commitments (RVCs)

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
172	Registry Voluntary Commitments (General)	Are you proposing to include one or more Registry Voluntary Commitments (RVCs) in the Base RA that are unique to your applied-for string?	—	[Albert to provide]
173	Registry Voluntary Commitments (RCE Criteria 1, 2 & 3)	State a specific Registry Voluntary Commitment (RVC) that is proposed to be included in the applicable Base RA.	Yes	[Albert to provide]
174	Registry Voluntary Commitments (RCE Criterion 3)	Explain the rationale for any limitations to the commitment proposed by the applying entity in Question 173.	Yes	[Albert to provide]
175	Registry Voluntary Commitments (Background, RCE Criteria 4 & 5)	Why are the commitment(s) being proposed?	Yes	[Albert to provide]

Question Set 12: Registry Services

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
176	Registry Service Providers (RSP Use)	List the selected Registry Service Providers (RSPs)	No	[Albert to provide]
177	Registry Services	List of Registry Services that will be used in the TLD	No	[Albert to provide]
178	Registry Services	Supported IDN Table Identifiers	No	[Albert to provide]

Question Set 13: .Brand TLD and Code of Conduct Exemptions

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
179	.Brand TLD Status	Are you applying for a .Brand TLD?	Yes	Yes (.Brand, Specification 13; separate ICANN fee USD 500)
180	.Brand TLD Status	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 its 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.	Yes	[Albert to provide]
181	.Brand TLD Status	Submit Trademark Certificate.	Yes	[Albert to provide]
182	.Brand TLD Status	Submit Trademark Clearinghouse (TMCH) Signed Mark Data (SMD) files.	No	[Albert to provide]
183	.Brand TLD Status / Code of Conduct Exemptions	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.	Yes	[Albert to provide]
184	.Brand TLD Status / Code of Conduct Exemptions	No Specification 11 Conflicts	Yes	[Albert to provide]
185	Code of Conduct Exemptions	Does the applying entity request a Code of Conduct Exemption?	Yes	No separate request: ICANN states Specification 13 (.Brand) TLDs are exempt from the Code of Conduct and need not apply for a CoC exemption
186	Code of Conduct Exemptions	The applying entity confirms all domain name registrations in the TLD will be registered to, and maintained by, registry operator for the exclusive use of the registry operator or its affiliate (as defined in the Base RA).	Yes	Intended model: closed, single-registrant (registry operator only). [Albert to confirm]
187	Code of Conduct Exemptions	Confirm the registry operator will not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an affiliate of registry operator.	Yes	Intended model: no sale or transfer of names to third parties. [Albert to confirm]
188	Code of Conduct Exemptions	Confirm and specify why the Application of the Code of Conduct to the applied-for string is not necessary to protect the public interest.	Yes	[Albert to provide]

Question Set 14: Financial Evaluation Profile Determination

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
189	Profile Determination	Is the applying entity a governmental entity, an Intergovernmental Organization (IGO), or an International Non-Governmental Organizations (INGO) as defined in ICANN Consensus Policy? 10	No	[Albert to provide]
190	Profile Determination	Is the applying entity a current registry operator with one or more active RAs, or an affiliated entity to an existing registry operator?	No	[Albert to provide]
191	Profile Determination	Is the applying entity a publicly traded company on a Top 25 Public Stock Exchange, as defined by the World Federation of Exchanges and specifically included on ICANN’s list from Market Statistics ( https://focus.world-exchanges.org/issue/december-2025/market-statistics , as of December 2025), or an affiliated entity to the company listed on a Top 25 Public Stock Exchange?	No	[Albert to provide]

Question Set 15: Government Profile

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
192	Financial Evaluation - Government Profile: Self- Certification (Q1.1-1) 11	Q1.1-1 - Provide the applying entity’s self-certification document that commits government support on official letterhead from a proper authority, that the application for the gTLD(s) and its operation by the applying entity is permitted, and that represents and warrants: SC1.1-1.1 - That the applying entity is the recognized government of its jurisdiction and that the government has authorized the application(s) for applied-for gTLD string(s) or is a recognized intergovernmental organization with relevant authorization for its application(s) for applied-for gTLD string(s). SC1.1-1.2 - That the applying entity and/or an affiliate commits to the long-term funding required to operate all of the existing gTLDs (if applicable) and newly applied-for gTLD string(s) of the applying entity.	Yes	[Albert to provide]
193	Financial Evaluation - Government Profile: Operational/ Planning (Q1.2-1) 12	Q1.2-1 - Provide a document with a list of the applying entity’s current gTLDs (if applicable) and a list of all gTLDs for entities affiliated with the applying entity(if applicable). If the applying entity and affiliates have no current gTLDs, submit a document that confirms this.	Yes	[Albert to provide]
194	Financial Evaluation - Government Profile: Operational/ Planning (Q1.2-2)	Q1.2-2 - Provide a document containing a list of the applying entity’s applied-for strings plus a forecast for each string of the number of Domains Under Management (DUMs) for Year 1, Year 2, and Year 3 beginning after delegation.	No	[Albert to provide]

Question Set 16: Registry Operator Profile

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
195	Financial Evaluation - Registry Operator Profile: Financial Statements (Q2.1-1 )	Q2.1-1 - For either the applying entity or a Qualified Parent Entity (QPE) of the applying entity, provide a) complete audited financial statements for the most recently closed fiscal year and, if available, b) financial statements for the most recently ended interim financial period. Where audited statements cannot be provided, provide either the applying entity’s reviewed or compiled financial statements for the most recently closed fiscal year or interim period. All financial statements must be prepared by a third-party accounting firm. QPE statements must be audited.	No	[Albert to provide]
196	Financial Evaluation - Registry Operator Profile: Financial Statements (Q2.1-2)	Q2.1-2 - If a complete set of financial statements is provided by a Qualified Parent Entity (QPE) of the applying entity, the applying entity must provide a statement that clarifies how the QPE meets the definition of a QPE in the Financial Statements Instructions.	No	[Albert to provide]
197	Financial Evaluation - Registry Operator Profile: Financial Statements (Q2.1-3)	Q2.1-3 - Provide a statement clarifying why the financial statements of the applying entity submitted as part of Q2.1-1 were chosen for submission and are the most appropriate set of financial statements to review with respect to the proposed gTLDs.	No	[Albert to provide]
198	Financial Evaluation - Registry Operator Profile: Financial Statements (Q2.1-4)	Q2.1-4 - Provide a statement stating what accounting standards were used to prepare the financial statements of the applying entity provided as part of Q2.1-1 (for example, U.S. Generally Accepted Accounting Principles (GAAP), International Financial Statements Reporting Standards (IFRS), or any nationally recognized accounting standard for the jurisdiction where the entity resides).	No	[Albert to provide]
199	Financial Evaluation - Registry Operator Profile: Self-Certification (Q2.2-1)	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 RAs. 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.	Yes	[Albert to provide]
200	Financial Evaluation - Registry Operator Profile: Operational/Planning (Q2.3-1)	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).	Yes	[Albert to provide]
201	Financial Evaluation - Registry Operator Profile: Operational/Planning (Q2.3-1)	Q2.3-2 - Provide a document containing a list of all of the applying entity’s applied-for strings plus a forecast for each string of the number of Domains Under Management (DUMs) for Year 1, Year 2, and Year 3 beginning after delegation.	No	[Albert to provide]

Question Set 17: Top 25 Profile

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
202	Financial Evaluation - Top 25 Profile: Financial Statements (Q3.1-1)	Q3.1-1 - Provide a complete set of the applying entity’s audited financial statements for the most recently closed fiscal year and, if available, financial statements for the most recently ended interim financial period for the applying entity or a Qualified Parent Entity (QPE) as defined in the Financial Instructions.	No	[Albert to provide]
203	Financial Evaluation - Top 25 Profile: Financial Statements (Q3.1-2)	Q3.1-2 - If a complete set of financial statements is provided by a QPE (Qualified Parent Entity) of the applying entity, the applying entity must provide a statement that clarifies how the QPE meets the definition of a QPE as defined in the Financial Statements Instructions.	No	[Albert to provide]
204	Financial Evaluation - Top 25 Profile: Financial Statements (Q3.1-3)	Q3.1-3 - Provide a statement clarifying why the applying entity’s financial statements submitted as part of Q3.1-1 were chosen for submission and are the most appropriate set of financial statements to review with respect to the proposed gTLDs.	No	[Albert to provide]
205	Financial Evaluation - Top 25 Profile: Financial Statements (Q3.1-4)	Q3.1-4 - Provide a statement stating what accounting standards were used to prepare the applying entity’s financial statements provided as part of Q3.1-1 (for example, U.S. Generally Accepted Accounting Principles (GAAP), International Financial Statements Reporting Standards (IFRS), or any nationally recognized accounting standard for the jurisdiction where the entity resides).	No	[Albert to provide]
206	Financial Evaluation - Top 25 Profile: Self-Certification (Q3.2-1)	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.	Yes	[Albert to provide]
207	Financial Evaluation - Top 25 Profile: Operational/Planning (Q3.3-1)	Q3.3-1 - Provide a document containing a list of all of the applying entity’s applied-for strings plus a forecast for each string of the number of Domains Under Management (DUMs) for Year 1, Year 2, and Year 3 beginning after delegation.	No	[Albert to provide]

Question Set 18: Standard Profile

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
208	Financial Evaluation - Standard Profile: Financial Statements (Q4.1-1)	Q4.1-1 - For either the applying entity or a Qualified Parent Entity (QPE) of the applying entity, provide: a) the applying entity’s complete audited financial statements for the most recently closed fiscal year and, if available, b) financial statements for the most recently ended interim financial period for the applying entity or a Qualified Parent Entity (QPE) of the applying entity. Where audited statements cannot be provided, provide either the applying entity’s reviewed or compiled financial statements for the most recently closed fiscal year or interim period. All financial statements must be prepared by a third-party accounting firm. QPE statements must be audited.	No	[Albert to provide]
209	Financial Evaluation - Standard Profile: Financial Statements (Q4.1-2)	Q4.1-2 - If a complete set of financial statements is provided by a Qualified Parent Entity (QPE) of the applying entity, the applying entity must provide a statement that clarifies how the QPE meets the definition of a QPE as defined in the Financial Statements Instructions.	No	[Albert to provide]
210	Financial Evaluation - Standard Profile: Financial Statements (Q4.1-3)	Q4.1-3 - Provide a statement clarifying why the applying entity’s financial statements submitted as part of Q4.1-1 were chosen for submission and are the most appropriate set of financial statements to review with respect to the proposed gTLDs.	No	[Albert to provide]
211	Financial Evaluation - Standard Profile: Financial Statements (Q4.1-4)	Q4.1-4 - Provide a statement stating what accounting standards were used to prepare the applying entity’s financial statements provided as part of Q4.1-1 (for example, U.S. Generally Accepted Accounting Principles (GAAP), International Financial Statements Reporting Standards (IFRS), or any nationally recognized accounting standard for the jurisdiction where the entity resides).	No	[Albert to provide]
212	Financial Evaluation - Standard Profile: Self-Certification (Q4.2-1)	Q4.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), 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: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of USD 50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of USD 300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.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.	Yes	[Albert to provide]
213	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.1-1 - Most Likely Scenario Financial Projection)	Q4.3.1-1 - Populate and provide the Financial Evaluation Templates – MLS. The Most Likely Scenario (MLS) Financial Projection will quantify the applying entity’s plans to build, fund, and operate the applied-for gTLD strings on an ongoing basis. The MLS projection focuses on funding and positive cash flow needed for the expected operating plan. Detailed instructions for populating the spreadsheet are in the Financial Evaluation Templates Instructions.	No	[Albert to provide]
214	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.2-1 - Operating Costs)	Q4.3.2-1 - Populate the Financial Evaluation Templates – MLS with the estimated startup and the first three years combined operating costs for all of the applying entity’s applied-for gTLD strings. This cost should include Registry Service Providers (RSP) Services, administration, labor, facilities, marketing, etc. Any major variances (20% or greater) between years in anticipated ranges for expected costs must be briefly explained in the MLS Comments column of the Template.	No	[Albert to provide]
215	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.2-2 - Operating Costs)	Q4.3.2-2 - With the exception of employee agreements, provide all material outsourced Contracts, Letters of Intent (LOIs), and Proposals for the applying entity’s operating costs.	No	[Albert to provide]
216	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.3-1 - Funding and Revenue)	Q4.3.3-1 - For projected revenue, describe the applying entity’s strategy for using various pricing models for projected registration revenue, if applicable, such as auctions, premium naming, multi-year versus single-year registrations, etc. across all applied-for gTLD strings in MLS Comments.	No	[Albert to provide]
217	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.3-2 - Funding and Revenue)	Q4.3.3-2 - Identify and document in MLS Comments any sources of capital funding required to sustain registry operations for the short-term and long-term, ongoing basis.	No	[Albert to provide]
218	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.4-1 - Contingency Planning)	Q4.3.4-1 - Using the Financial Evaluation Templates – Risk Assessment spreadsheet, document and provide the applying entity’s assessment of the predefined and specific gTLD material risks to the successful operation of a combined set of all applied-for gTLD strings.	No	[Albert to provide]
219	Financial Evaluation - Standard Profile: Operational Planning ( Q4.3.5-1 - Worst Case Scenario Financial Projection)	Q4.3.5-1 - Populate and provide the Worst Case Scenario (WCS) projections as defined in the Financial Evaluation Templates – WCS. The projections must demonstrate that the applying entity’s funding is adequate to produce positive cashflow for the startup period and the first three years of operations. Detailed instructions for populating the spreadsheet are in the Financial Evaluation Templates Instructions.	No	[Albert to provide]

Question Set 19: Operational Questions - All financial profiles answer

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
220	Financial Evaluation : Security Policy and Planning (Q5.1-1) 14	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 Base RA. 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.	Yes	[Albert to provide]
221	Financial Evaluation : DNS Abuse (Q5.2-1)	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.	Yes	[Albert to provide]

Question Set 20: Additional Information and Supporting Materials

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
222	Additional Information and Supporting Materials	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.	Yes	Website: https://albertlane.net · X: @AlbertLane_net · ${ALDI}^{x}$ TV™: https://albertlane.net/live

Question Set 21: Bona Fide Intent and Prohibited Communications

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
223	Bona fide intent	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.	Yes	[Albert to provide]
224	Prohibited Communications	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.	Yes	[Albert to provide]

Question Set 22: Volume Refund

#	Sub-section	Question (AGB 2026 Round, Appendix 1)	Public	Prefilled answer
225	Volume Refund	If an Application Volume Refund is available, does the applying entity elect to receive the refund?	No	[Albert to provide]

Sources

Independent page by Albert Lane. Not affiliated with or endorsed by ICANN. Prepared 2026-10-22.