.bremen

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 US$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 US$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.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

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

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

If answered yes to previous question, how will the applying entity market and/or use the TLD primarily for purposes associated with the city name?

Framework for German geoTLDs

Under the German Telecommunications Act (TKG), the administration of TLDs does not fall within the remit of the Federal Network Agency. The allocation and management of TLDS such as .de and .berlin are therefore carried out independently by private registry operators in Germany. For more than 30 years, registrants and Internet users have been accustomed to this model and would not assume that the registry operator is a public body. They also do not assume that the registry operator carries any greater degree of trustworthiness than other commercial entities, or that the operation of a TLD constitutes a regulated sector activity.

Marketing and Use of .bremen

The .bremen TLD serves as the digital identifier for everything associated with the State of Bremen. The registry operator will ensure that domain registrations will primarily include a connection to Bremen - making the TLD a reliable signal of geographic provenance for users worldwide. Marketing activities will therefore promote .bremen as the digital home of Bremen: its people, businesses, institutions, culture, and government.

The marketing approach would operate on two levels simultaneously. First, supply-side activation: working with anchor institutions and key local stakeholders to populate the namespace with high-profile, recognizable .bremen domains early in the launch phase, creating visible reference points that demonstrate what the TLD stands for. Second, demand-side awareness: campaigns directed at businesses and residents explaining the benefits of a domain that instantly communicates local identity and trustworthiness.

All marketing materials — e. g. print, out of home advertising, digital campaigns, social media, and trade fair appearances — would display .bremen domains prominently alongside the visual identity of Bremen. The message would be consistent: a .bremen domain does not just tell you where a website points — it tells you who it belongs to and where they are rooted. For a city with a distinct, internationally recognised identity as a Hanseatic trading hub, that association carries intrinsic value for any registrant wishing to signal authenticity, local accountability, and community belonging.

Usage examples for .bremen

* Government and Public Administration* senat.bremen — official portal of the Bremen Senate buergerservice.bremen — citizen services platform polizei.bremen — police and public safety

*Tourism and City Promotion* visit.bremen — "Visit Bremen", a tourism landing page stadtmusikanten.bremen — dedicated site for the iconic Town Musicians of Bremen hafen.bremen — the historic harbour and maritime district

*Business and Commerce* handwerk.bremen — a platform for local craftspeople and tradespeople invest.bremen — inward investment and economic development portal messe.bremen — trade fair and exhibition centre

*Education and Research* uni.bremen — University of Bremen student portal jacobs.bremen — Jacobs University Bremen mint.bremen — STEM education initiatives

*Culture, Sport, and Community* kunsthalle.bremen — the city's major art museum theater.bremen — Theater Bremen and performing arts musik.bremen — music venues and festivals

*Personal Identity and Portfolios* mueller-fotografie.bremen — a freelance photographer based in Bremen showcasing their portfolio anna-schmidt.bremen — a personal blog or CV site for a student at the University of Bremen architektin-weber.bremen — a self-employed architect advertising local services

* Community Groups, Clubs, and Associations* kleingartenverein-nord.bremen — a local allotment gardening association nachbarschaftshilfe-huchting.bremen — a neighbourhood mutual aid group in the Huchting district elterninitiative-kita.bremen — a parent-run childcare initiative

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)”

Yes

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

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