Please see below for the full list of policies for gTLD's Lexsynergy has available.
Amazon Registry
https://www.registry.amazon/terms-and-policies.html
CentralNic Registry
https://centralnicregistry.com/policies/terms/
GoDaddy Registry
https://registry.godaddy/legal/
Google Registry
https://policies.google.com/terms
Identity Digital
https://www.identity.digital/policies
Internet Naming Co.
Public Interest Registry
https://pir.org/our-impact/ngo-ong-policy/
Radix
http://radix.website/policies/
Tucows Registry
https://www.tucowsregistry.com/terms-conditions
Verisign
https://www.verisign.com/legal-center/
.abogado
https://domains.registry.godaddy/policiespdf/ABGD-POL-001-Eligibility_Policy-1.0.pdf
.africa
https://registry.africa/our-policies/
.aero
https://information.aero/registration/policies
.amsterdam
https://nic.amsterdam/wp-content/uploads/dotAMSTERDAM-General-Terms-and-Conditions-1.1.pdf
.bank
Registrants and Users who register a domain name in the .BANK TLD agree to accept and be bound by the terms and conditions set out in https://register.bank/policies/
The Registrant and User are required to comply with the .bank Naming Authority security requirements at https://www.ftld.com/security/
The Registry Operator (fTLD) of .bank does not favour one registrar over another providing the same level of access to all .bank accredited registrars. LS therefore does not enjoy access to any other Registry Operator's Registry System that is superior to that of any other accredited for the .bank TLD.
.bar/.rest
https://www.punto2012.com/policies
.barcelona
https://www.domini.barcelona/en/domain-registration-policy/
.bayern
https://domains.bayern/nutzungsbedingungen/
.berlin
https://dot.berlin/registrierungsregeln-policies/
.bible
http://www.nic.bible/uploads/dotBible_Code_of_Conduct_201601.pdf
.blog
https://my.blog/privacy-policy/
01. Registered Name Holder has to comply with the Operational standards, policies, procedures, and practices for the .BLOG TLD established from time to time by Registry Operator, including without limitation all Registry Policies. Any additional or revised Registry Operator operational standards, policies, procedures, and practices for the .BLOG TLD shall be effective thirty (30) days after posting on Registry Website. If there is a discrepancy between the terms required by this Agreement and the terms of the Registrar’s Registration Agreement, the terms of this Agreement shall supersede those of the Registrar’s registration agreement.
02. Notwithstanding anything in this Agreement to the contrary, Knock Knock WHOIS There, LLC, the Registry Operator of the .BLOG TLD, is and shall be an intended third party beneficiary of this Registration Agreement. As such the parties to this agreement acknowledge and agree that the third party beneficiary rights of Knock Knock WHOIS There, LLC have vested and that Knock Knock WHOIS There, LLC has relied on its third party beneficiary rights under this Registration Agreement in agreeing to Registrar becoming a registrar for the .BLOG TLD. Additionally, the third party beneficiary rights of Knock Knock WHOIS There, LLC shall survive any termination of this Registration Agreement.
03. Registered name holder must:
* Consent to the use, copying, distribution, publication, modification and other processing of the Registered Name Holder’s Personal Data by Registry Operator and its designees and agents in a manner consistent with the purposes specified herein, current ICANN policies, and with relevant mandatory local data protection, laws and privacy;
* Abstain from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activities contrary to applicable law;
* Consent to the collection and use of Personal Data by Registry Operator, in conformity with the terms of this Agreement and the Registry Agreement, and applicable law
.box
.brussels/.vlaanderen
https://assets.dnsbelgium.be/attachment/2014.08.27%20Terms%20and%20conditions_1.pdf
.bzh
https://www.pik.bzh/rdap-terms-of-service/
.cam
.capetown/.durban/.joburg
https://zacities.africa/policies/
.cat
https://domini.cat/en/rules-of-the-cat-domain/
.cloud
https://www.get.cloud/policies
.cologne/.koeln
.coop/.creditunion
https://identity.coop/policies-and-agreements/
.corsica
https://puntu.corsica/politiques-de-registre-de-puntu-corsica/
.cpa
https://register.domains.cpa/policies/
.cymru/.wales
.eco
.eu/.ею/.ευ
https://eurid.eu/en/knowledge-centre/rules-for-eu-domains/
.eus
https://puntu.eus/en/eus-domain-policy/
.frl
https://nic.frl/wp-content/uploads/2015/10/puntFRLGeneralTermsandConditions.pdf
.gal
https://dominio.gal/en/how-gal/#policies
.gay
https://domains.registry.godaddy/policiespdf/GAY-POL-001-Community_Protection_Policy-0.pdf
.gdn
http://www.nic.gdn/policy/Domain_Policy_v1.0.pdf
.hamburg
.hiphop
https://get.hiphop/wp-content/uploads/2022/10/DHH-Acceptable-Use-Policy.pdf
.insurance
Registrants and Users who register a domain name in the .INSURANCE TLD agree to accept and be bound by the terms and conditions set out in https://register.insurance/policies/
The Registrant and User are required to comply with the .bank Naming Authority security requirements at https://www.ftld.com/security/
The Registry Operator (fTLD) of .bank does not favour one registrar over another providing the same level of access to all .insurance accredited registrars. LS therefore does not enjoy access to any other Registry Operator's Registry System that is superior to that of any other accredited for the .insurance TLD.
.ist/.istanbul
https://nic.istanbul/page/policies
.jobs
https://secure.jobs/terms-and-conditions/
.kyoto
https://nic.kyoto/en/policies/
.law
https://domains.registry.godaddy/policiespdf/LAW-POL-001-Eligibility_Policy-1.0.pdf
.locker
https://nic.locker/od_registry_policy_statement.pdf
.london
https://register.london/policies/
.love
https://get.love/wp-content/uploads/2020/02/Policies-dotlove-06-Feb-2020.pdf
.madrid
https://dominio.madrid/en/doc/madrid_LaunchPolicy_20190322.pdf
.makeup
https://nic.makeup/registry-policies
.med
https://medistry.med/pages/policies
.melbourne
https://domains.registry.godaddy/policiespdf/MEL-Policies/MEL-POL-001-Registration_Policy-2.3.pdf
.mobile
https://nic.mobile/wp-content/uploads/2025/10/Mobile-Registry-Policy-and-Acceptable-Use.pdf
.moscow/.москва
https://www.faitid.org/en/projects/moscow/documents
.museum
https://welcome.museum/wp-content/uploads/2018/05/20180525-Registration-Policy-MUSEUM-EN_VF-2.pdf
.music
https://registry.music/registry-policy
.nagoya
https://www.gmoregistry.com/en/policy/pdf/Nagoya_Domain_Name_Registration_Policies.pdf
.nrw
https://domains.nrw/nutzungsbedingungen/
.nyc
https://www.ownit.nyc/policies
.okinawa
https://www.brregistry.com/images/Okinawa_Domain_Name_Registration_Policies.pdf
.paris
https://cdn.paris.fr/paris/2021/09/01/d99971a614c63c3c97e99e4976154ccd.pdf
.pharmacy
https://nabp.pharmacy/programs/accreditations/dotpharmacy-registry/terms/
.quebec
https://registry.quebec/legal/
.radio
https://www.nic.radio/policies/dotradio_Registration_Policy.pdf
.realestate
https://www.get.realestate/domain-rules
.ren
.rio
https://nic.rio/english/policies/
.ryukyu
https://www.brregistry.com/images/Ryukyu_Domain_Name_Registration_Policies.pdf
.saarland
https://nic.saarland/en/policies
.scot
.shop
.sport
.sucks
.sydney
https://domains.registry.godaddy/policiespdf/SYD-Policies/SYD-POL-001-Registration_Policy-1.3.pdf
.tel
.tirol
https://www.nic.tirol/ueber-uns/policies/
.tokyo
https://www.gmoregistry.com/en/policy/pdf/Tokyo_Domain_Name_Registration_Policies.pdf
.top
https://www.nic.top/en/Policy.asp
.tube
.vegas
https://www.nic.vegas/registry-policy
.versicherung
https://www.nic.versicherung/media/files/Policy%20EN%20pdf/VERSICHERUNG-Registration-Policy_V1.1.pdf
Eligible registrants to register a second-level name in .versicherung TLD are based in the countries of Austria, Germany, Liechtenstein and Switzerland and are in detail:
a. Governments
b. Governmental organizations regulating the insurance industry
c. Organizations and individuals (sole proprietors) that are recognized and registered members of the insurance industry community:
(i) Primary insurers, reinsurers and social insurers with an authorization within the legal frameworks for the insurance industry in the respective countries.
(ii) Insurance agents and insurance intermediaries with an authorization within the legal framework for the insurance industry in the respective countries
(iii) At an official public register registered associations, educational institutions and service providers of the insurance industry.
Anyone may have the registrant's compliance with the registration guidelines checked via a legal or an extra-judicial dispute resolution process.
On request of the registry, a .VERSICHERUNG Domain Name registrant has to proof its relationship to the Insurance community as defined in the .VERSICHERUNG registration policy.
The .VERSICHERUNG TLD as a Community TLD has both, content and use restrictions:
(i) Content: .VERSICHERUNG domain names must only be used for purposes solely dedicated to insurance topics.
(ii) Use: The registrant must have started the use of a .VERSICHERUNG domain name within six months after the registration in respect to the content and use restrictions of a .VERSICHERUNG domain.
.whoswho
.wien
https://www.nic.wien/en/policies
.yokohama
https://www.gmoregistry.com/en/policy/pdf/Yokohama_Domain_Name_Registration_Policies.pdf
.zuerich
https://nic.zuerich/assets/pdf/zuerich-Domain-Name-Registration-and-Use-Policy.pdf
.بازار
https://dotbazaar.net/registration-policy/
.ストア
Acceptable Use and Anti-Abuse Policy
.食品
Acceptable Use and Anti-Abuse Policy
.書籍
Acceptable Use and Anti-Abuse Policy
.セール
Acceptable Use and Anti-Abuse Policy
.ファッション
Acceptable Use and Anti-Abuse Policy
.家電
Acceptable Use and Anti-Abuse Policy
.クラウド