Exhibit 10.7

ICANN

Registrar Accreditation
Agreement


This
REGISTRAR ACCREDITATION AGREEMENT ("Agreement") is by and between the Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit
corporation, and Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar"), and shall be deemed made on 22 June 2009 at Los Angeles, California, USA.

1.DEFINITIONS.For purposes of this Agreement, the following
definitions shall apply:

1.1   "Accredit"
means to identify and set minimum standards for the performance of registration functions, to recognize persons or entities meeting those standards, and to
enter into an accreditation agreement that sets forth the rules and procedures applicable to the provision of Registrar Services.

1.2   "DNS"
refers to the Internet domain-name system.

1.3   The
"Effective Date" is 1 July 2009.

1.4   The
"Expiration Date" is 30 June 2014.

1.5   "ICANN"
refers to the Internet Corporation for Assigned Names and Numbers, a party to this Agreement.

1.6   "Personal
Data" refers to data about any identified or identifiable natural person.

1.7   "Registered
Name" refers to a domain name within the domain of a TLD that is the subject of an appendix to this Agreement, whether consisting of two (2) or more
(e.g., john.smith.name) levels, about which a TLD Registry Operator (or an affiliate engaged in providing Registry Services) maintains data in a Registry Database, arranges for such
maintenance, or derives revenue from such maintenance. A name in a Registry Database may be a Registered Name even though it does not appear in a zone file (e.g., a registered but inactive
name).

1.8   "Registered
Name Holder" means the holder of a Registered Name.

1.9   The
word "Registrar," when appearing with an initial capital letter, refers to Tucows Inc., a party to this Agreement.

1.10 The
word "registrar," when appearing without an initial capital letter, refers to a person or entity that contracts with Registered Name Holders and with a Registry
Operator and collects registration data about the Registered Name Holders and submits registration information for entry in the Registry Database.

1.11 "Registrar
Services" means services provided by a registrar in connection with a TLD as to which it has an agreement with the TLD's Registry Operator, and includes
contracting with Registered Name Holders, collecting registration data about the Registered Name Holders, and submitting registration information for entry in the Registry Database.

1.12 "Registry
Data" means all Registry Database data maintained in electronic form, and shall include TLD Zone-File Data, all data used to provide Registry
Services and submitted by registrars in electronic form, and all other data used to provide Registry Services concerning particular domain name registrations or nameservers maintained in electronic
form in a Registry Database.

1.13 "Registry
Database" means a database comprised of data about one or more DNS domain names within the domain of a registry that is used to generate either DNS resource
records that are published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names.

1.14 A
"Registry Operator" is the person or entity then responsible, in accordance with an agreement between ICANN (or its assignee) and that person or entity (those persons
or entities) or, if

---



that
agreement is terminated or expires, in accordance with an agreement between the US Government and that person or entity (those persons or entities), for providing Registry Services for a specific
TLD.

1.15 "Registry
Services," with respect to a particular TLD, shall have the meaning defined in the agreement between ICANN and the Registry Operator for that TLD.

1.16 A
Registered Name is "sponsored" by the registrar that placed the record associated with that registration into the registry. Sponsorship of a registration may be
changed at the express direction of the Registered Name Holder or, in the event a registrar loses accreditation, in accordance with then-current ICANN specifications and policies.

1.17 "Term
of this Agreement" begins on the Effective Date and continues to the earlier of (a) the Expiration Date, or (b) termination of this Agreement.

1.18 A
"TLD" is a top-level domain of the DNS.

1.19 "TLD
Zone-File Data" means all data contained in a DNS zone file for the registry, or for any subdomain for which Registry Services are provided and that
contains Registered Names, as provided to nameservers on the Internet.

1.20 "Affiliated
Registrar" is another ICANN accredited registrar that operates under a common controlling interest.

2.ICANN OBLIGATIONS.

2.1Accreditation.During the Term of this Agreement, Registrar is hereby accredited by ICANN to act as a
registrar (including to insert and renew registration of Registered Names in the Registry Database) for the TLD(s) that are the subject of appendices to this Agreement according to
Subsection 5.5. Notwithstanding the above and except in the case of a good faith disagreement concerning the interpretation of this Agreement, ICANN may, following notice to Registrar, suspend
Registrar's ability to create new Registered Names or initiate inbound transfers of Registered Names for one or more TLDs for up to a twelve (12) month period if (i) ICANN has given
notice to Registrar of a breach that is fundamental and material to this Agreement pursuant to Subsection 5.3.4 and Registrar has not cured the breach within the period for cure prescribed by
Subsection 5.3.4, or (ii) Registrar shall have been repeatedly and willfully in fundamental and material breach of its obligations at least three (3) times within any twelve
(12) month period.

2.2Registrar Use of ICANN Name and Website.ICANN hereby grants to Registrar a non-exclusive,
worldwide, royalty-free license during the Term of this Agreement (a) to state that it is accredited by ICANN as a registrar for each TLD that is the subject of an appendix to this
Agreement and (b) to link to pages and documents within the ICANN web site. No other use of ICANN's name or website is licensed hereby. This license may not be assigned or sublicensed by
Registrar.

2.3General Obligations of ICANN.With respect to all matters that impact the rights, obligations, or role of
Registrar, ICANN shall during the Term of this Agreement:



2.4Use of ICANN Accredited Registrars.In order to promote competition in the registration of domain names, and
in recognition of the value that ICANN-accredited registrars bring to the Internet

---



community,
ICANN has ordinarily required gTLD registries under contract with ICANN to use ICANN-accredited registrars, and ICANN will during the course of this agreement abide by any ICANN adopted
specifications or policies requiring the use of ICANN-accredited registrars by gTLD registries.

3.REGISTRAR OBLIGATIONS.

3.1Obligations to Provide Registrar Services.During the Term of this Agreement, Registrar agrees that it will
operate as a registrar for each TLD for which it is accredited by ICANN in accordance with this Agreement.

3.2Submission of Registered Name Holder Data to Registry.During the Term of this Agreement:



3.3Public Access to Data on Registered Names.During the Term of this Agreement:



---









---





3.4Retention of Registered Name Holder and Registration Data.



---





3.5Rights in Data.Registrar disclaims all rights to exclusive ownership or use of the data elements listed in
Subsections 3.2.1.1 through 3.2.1.3 for all Registered Names submitted by Registrar to the Registry Database for, or sponsored by Registrar in, each TLD for which it is accredited. Registrar
does not disclaim rights in the data elements listed in Subsections 3.2.1.4 through 3.2.1.6 and Subsections 3.3.1.3 through 3.3.1.8 concerning active Registered Names sponsored by it in
each TLD for which it is accredited, and agrees to grant non-exclusive, irrevocable, royalty-free licenses to make use of and disclose the data elements listed in
Subsections 3.2.1.4 through 3.2.1.6 and 3.3.1.3 through 3.3.1.8 for the purpose of providing a service or services (such as a Whois service under Subsection 3.3.4) providing interactive,
query-based public access. Upon a change in sponsorship from Registrar of any Registered Name in a TLD for which it is accredited, Registrar acknowledges that the registrar gaining sponsorship shall
have the rights of an owner to the data elements listed in Subsections 3.2.1.4 through 3.2.1.6 and 3.3.1.3 through 3.3.1.8 concerning that Registered Name, with Registrar also retaining the
rights of an owner in that data. Nothing in this Subsection prohibits Registrar from (1) restricting bulk public access to data elements in a manner consistent with this Agreement and any ICANN
specifications or policies or (2) transferring rights it claims in data elements subject to the provisions of this Subsection.

3.6Data Escrow.During the Term of this Agreement, on a schedule, under the terms, and in the format specified
by ICANN, Registrar shall submit an electronic copy of the database described in Subsection 3.4.1 to ICANN or, at Registrar's election and at its expense, to a reputable escrow agent mutually
approved by Registrar and ICANN, such approval also not to be unreasonably withheld by either party. The data shall be held under an agreement among Registrar, ICANN, and the escrow agent (if any)
providing that (1) the data shall be received and held in escrow, with no use other than verification that the deposited data is complete, consistent, and in proper format, until released to
ICANN; (2) the data shall be released from escrow upon expiration without renewal or termination of this Agreement; and (3) ICANN's rights under the escrow agreement shall be assigned
with any assignment of this Agreement. The escrow shall provide that in the event the escrow is released under this Subsection, ICANN (or its assignee) shall have a non-exclusive,
irrevocable, royalty-free license to exercise (only for transitional purposes) or have exercised all rights necessary to provide Registrar Services.

3.7Business Dealings, Including with Registered Name Holders.



---





---





---





3.8Domain-Name Dispute Resolution.During the Term of this Agreement, Registrar shall have in place
a policy and procedures for resolution of disputes concerning Registered Names. Until different policies and procedures are established by ICANN under Section 4, Registrar shall comply with the
Uniform Domain Name Dispute Resolution Policy identified on ICANN's website (www.icann.org/general/consensus-policies.htm).

3.9Accreditation Fees.As a condition of accreditation, Registrar shall pay accreditation fees to ICANN. These
fees consist of yearly and variable fees.



---







3.10Insurance.Registrar shall maintain in force commercial general liability insurance with policy limits of
at least US$500,000 covering liabilities arising from Registrar's registrar business during the term of this Agreement.

3.11Obligations of Registrars under common controlling interest.Registrar shall be in breach of this Agreement
if:



3.12Obligations of Third-Party Resellers.If Registrar enters into an agreement with a reseller of Registrar
Services to provide Registrar Services ("Reseller"), such agreement must include at least the following provisions:



---





3.13Registrar Training.Registrar's primary contact as identified in Subsection 5.11 below or designee
(so long as the designee is employed by Registrar or an Affiliated Registrar) shall complete a training course covering registrar obligations under ICANN policies and agreements. The training course
will be developed in consultation with registrars. The course will be provided by ICANN at no expense to Registrar, and shall be available in an online format.

3.14Registrar Audits.Registrar shall, upon no less than fifteen (15) days notice and as part of any
reasonable contractual compliance audit, (1) timely provide the documents and information known by Registrar necessary to demonstrate compliance with the terms of this Agreement; and
(2) permit ICANN to conduct site visits in compliance with all applicable laws to assess compliance with the terms of this Agreement, provided that ICANN, in its notice, states the specific
compliance audit that it intends to conduct. ICANN shall not disclose Registrar confidential information gathered through such audits except as expressly permitted by an ICANN specification or policy.
If such specification or policy permits such disclosure, ICANN will provide Registrar no less than fifteen (15) days notice of its intent to disclose such information. Such notice shall include
to whom and in what manner ICANN plans to disclose such information.

3.15 In
the event that ICANN gives reasonable notice to Registrar that ICANN has published a webpage that identifies available registrant rights and responsibilities, and
the content of such webpage is developed in consultation with registrars, Registrar shall provide a link to the webpage on any website it may operate for domain name registration or renewal clearly
displayed to its Registered Name Holders at least as clearly as its links to policies or notifications required to be displayed under ICANN Consensus Policies.

3.16 Registrar
shall provide on its web site its accurate contact details including a valid email and mailing address.

4.PROCEDURES FOR ESTABLISHMENT OR REVISION OF SPECIFICATIONS AND
POLICIES.

4.1Registrar's Ongoing Obligation to Comply With New or Revised Specifications and Policies.During the Term of
this Agreement, Registrar shall comply with the terms of this Agreement on the schedule set forth in Subsection 4.4, with



4.2Topics for New and Revised Specifications and Policies.New and revised specifications and policies may be
established on the following topics:



---





Nothing
in this Subsection 4.2 shall limit Registrar's obligations as set forth elsewhere in this Agreement.

4.3Manner of Establishment of New and Revised Specifications and Policies.



---





4.4Time Allowed for Compliance.Registrar shall be afforded a reasonable period of time after notice of the
establishment of a specification or policy under Subsection 4.3 is e-mailed to Registrar and posted on the ICANN website at <www.icann.org/general/consensus-policies.htm>
in which to comply with that specification or policy, taking into account any urgency involved.

5.MISCELLANEOUS PROVISIONS.

5.1Specific Performance.While this Agreement is in effect, either party may seek specific performance of any
provision of this Agreement in the manner provided in Section 5.6 below, provided the party seeking such performance is not in material breach of its obligations.

5.2Termination of Agreement by Registrar.This Agreement may be terminated before its expiration by Registrar
by giving ICANN thirty (30) days written notice. Upon such termination by Registrar, Registrar shall not be entitled to any refund of fees paid to ICANN pursuant to this Agreement.

5.3Termination of Agreement by ICANN.This Agreement may be terminated before its expiration by ICANN in any of
the following circumstances:



---





This
Agreement may be terminated in circumstances described in Subsections 5.3.1 - 5.3.6 above only upon fifteen (15) days written notice to Registrar (in the
case of Subsection 5.3.4 occurring after Registrar's failure to cure), with Registrar being given an opportunity during that time to initiate arbitration under Subsection 5.6 to
determine the appropriateness of termination under this Agreement. If Registrar acts in a manner that ICANN reasonably determines endangers the stability or operational integrity of the Internet and
upon notice does not immediately cure, ICANN may suspend this Agreement for five (5) working days pending ICANN's application for more extended specific performance or injunctive relief under
Subsection 5.6. This Agreement may be terminated immediately upon notice to Registrar in circumstance described in Subsection 5.3.7 above.

5.4Term of Agreement; Renewal; Right to Substitute Updated Agreement.This Agreement shall be effective on the
Effective Date and shall have an initial term running until the Expiration Date, unless sooner terminated. Thereafter, if Registrar seeks to continue its accreditation, it may apply for renewed
accreditation, and shall be entitled to renewal provided it meets the ICANN-adopted specification or policy on accreditation criteria then in effect, is in compliance with its obligations under this
Agreement, as it may be amended, and agrees to be bound by terms and conditions of the then-current Registrar accreditation agreement (which may differ from those of this Agreement) that
ICANN adopts in accordance with Subsection 2.3 and Subsection 4.3. In connection with renewed accreditation, Registrar shall confirm its assent to the terms and conditions of the
then-current Registrar accreditation agreement by signing that accreditation agreement. In the event that, during the Term of this Agreement, ICANN posts on its web site an updated form of
registrar accreditation agreement applicable to Accredited registrars, Registrar (provided it has not received (1) a notice of breach that it has not cured or (2) a notice of termination
of this Agreement under Subsection 5.3 above) may elect, by giving ICANN written notice, to enter an agreement in the updated form in place of this Agreement. In the event of such election,
Registrar and ICANN shall promptly sign a new accreditation agreement that contains the provisions of the updated form posted on the web site, with the length of the term of the substituted agreement
as stated in the updated form posted on the web site, calculated as if it commenced on the date this Agreement was made, and this Agreement will be deemed terminated.

---



5.5Addition or Deletion of TLDs for Which Registrar Accredited.On the Effective Date, Registrar shall be
accredited according to Subsection 2.1 for each TLD as to which an appendix executed by both parties is attached to this Agreement. During the Term of this Agreement, Registrar may request
accreditation for any additional TLD(s) by signing an additional appendix for each additional TLD in the form prescribed by ICANN and submitting the appendix to ICANN. In the event ICANN agrees to the
request, ICANN will sign the additional appendix and return a copy of it to Registrar. The mutually signed appendix shall thereafter be an appendix to this Agreement. During the Term of this
Agreement, Registrar may abandon its accreditation for any TLD under this Agreement (provided that Registrar will thereafter remain accredited for at least one (1) TLD under this Agreement) by
giving ICANN written notice specifying the TLD as to which accreditation is being abandoned. The abandonment shall be effective thirty (30) days after the notice is given.

5.6Resolution of Disputes Under this Agreement.Disputes arising under or in connection with this Agreement,
including (1) disputes arising from ICANN's failure to renew Registrar's accreditation and (2) requests for specific performance, shall be resolved in a court of competent jurisdiction
or, at the election of either party, by an arbitration conducted as provided in this Subsection 5.6 pursuant to the International Arbitration Rules of the American Arbitration Association
("AAA"). The arbitration shall be conducted in English and shall occur in Los Angeles County, California, USA. There shall be three (3) arbitrators: each party shall choose one
(1) arbitrator and, if those two (2) arbitrators do not agree on a third arbitrator, the third shall be chosen by the AAA. The parties shall bear the costs of the arbitration in equal
shares, subject to the right of the arbitrators to reallocate the costs in their award as provided in the AAA rules. The parties shall bear their own attorneys' fees in connection with the
arbitration, and the arbitrators may not reallocate the attorneys' fees in conjunction with their award. The arbitrators shall render their decision within ninety (90) days of the conclusion of
the arbitration hearing. In the event Registrar initiates arbitration to contest the appropriateness of termination of this Agreement by ICANN or suspension of Registrar's ability to create new
Registered Names or initiate inbound transfers of Registered Names under Section 2.1 above, Registrar may at the same time request that the arbitration panel stay the termination or suspension
until the arbitration decision is rendered. The arbitration panel shall order a stay: (i) upon showing by Registrar that continued operations would not be harmful to consumers or the public
interest, or (ii) upon appointment by the arbitration panel of a qualified third party to manage the operations of the Registrar until the arbitration decision is rendered. In furtherance of
sub-clause (ii) above, the arbitration panel is hereby granted all necessary authority to appoint a qualified third-party to manage the operations of the Registrar upon the
Registrar's request and if the panel deems it appropriate. In selecting the third-party manager, the arbitration panel shall take into consideration, but shall not be bound by, any expressed
preferences of Registrar. In the event Registrar initiates arbitration to contest an Independent Review Panel's decision under Subsection 4.3.3 sustaining the Board's determination that a
specification or policy is supported by consensus, Registrar may at the same time request that the arbitration panel stay the requirement that it comply with the policy until the arbitration decision
is rendered, and that request shall have the effect of staying the requirement until the decision or until the arbitration panel
has granted an ICANN request for lifting of the stay. In all litigation involving ICANN concerning this Agreement (whether in a case where arbitration has not been elected or to enforce an arbitration
award), jurisdiction and exclusive venue for such litigation shall be in a court located in Los Angeles, California, USA; however, the parties shall also have the right to enforce a judgment of such a
court in any court of competent jurisdiction. For the purpose of aiding the arbitration and/or preserving the rights of the parties during the pendency of an arbitration, the parties shall have the
right to seek temporary or preliminary injunctive relief from the arbitration panel or in a court located in Los Angeles, California, USA, which shall not be a waiver of this arbitration agreement.

5.7Limitations on Monetary Remedies for Violations of this Agreement.ICANN's aggregate monetary liability for
violations of this Agreement shall not exceed the amount of accreditation fees paid by Registrar to ICANN under Subsection 3.9 of this Agreement. Registrar's monetary liability to ICANN for
violations of this Agreement shall be limited to accreditation fees owing to ICANN under this Agreement and, except in the case of a good faith disagreement concerning the interpretation of

---



this
agreement, reasonable payment to ICANN for the reasonable and direct costs including attorney fees, staff time, and other related expenses associated with legitimate efforts to enforce Registrar
compliance with this agreement and costs incurred by ICANN to respond to or mitigate the negative consequences of such behavior for registered name holders and the Internet community. In the event of
repeated willful material breaches of the agreement, Registrar shall be liable for sanctions of up to five (5) times ICANN's enforcement costs, but otherwise in no event shall either party be
liable for special, indirect, incidental, punitive, exemplary, or consequential damages for any violation of this Agreement.

5.8Handling by ICANN of Registrar-Supplied Data.Before receiving any Personal Data from Registrar, ICANN shall
specify to Registrar in writing the purposes for and conditions under which ICANN intends to use the Personal Data. ICANN may from time to time provide Registrar with a revised specification of such
purposes and conditions, which specification shall become effective no fewer than thirty (30) days after it is provided to Registrar. ICANN shall not use Personal Data provided by Registrar for
a purpose or under conditions inconsistent with the specification in effect when the Personal Data was provided. ICANN shall take reasonable steps to avoid uses of the Personal Data by third parties
inconsistent with the specification.

5.9Assignment; Change of Ownership or Management.



5.10No Third-Party Beneficiaries.This Agreement shall not be construed to create any obligation by either
ICANN or Registrar to any non-party to this Agreement, including any Registered Name Holder.

5.11Notices, Designations, and Specifications.Except as provided in Subsection 4.4, all notices to be
given under this Agreement shall be given in writing at the address of the appropriate party as set forth below, unless that party has given a notice of change of address in writing. Each party shall
notify the other party within thirty (30) days of any change to its contact information. Any notice required by this Agreement shall be deemed to have been properly given when delivered in
person, when sent by electronic facsimile with receipt of confirmation of delivery, or when scheduled for delivery by internationally recognized courier service. Designations and specifications by
ICANN under this Agreement shall be effective when written notice of them is deemed given to Registrar.

If
to ICANN, addressed to:



---



If
to Registrar, addressed to:



5.12Dates and Times.All dates and times relevant to this Agreement or its performance shall be computed based
on the date and time observed in Los Angeles, California, USA.

5.13Language.All notices, designations, and specifications made under this Agreement shall be in the English
language.

5.14Amendments and Waivers.No amendment, supplement, or modification of this Agreement or any provision hereof
shall be binding unless executed in writing by both parties. No waiver of any provision of this Agreement shall be binding unless evidenced by a writing signed by the party waiving compliance with
such provision. No waiver of any of the provisions of this Agreement shall be deemed or shall constitute a waiver of any other provision hereof, nor shall any such waiver constitute a continuing
waiver unless otherwise expressly provided.

5.15Counterparts.This Agreement may be executed in one or more counterparts, each of which shall be deemed an
original, but all of which together shall constitute one and the same instrument.

5.16Entire Agreement.Except to the extent (a) expressly provided in a written agreement executed by
both parties concurrently herewith or (b) of written assurances provided by Registrar to ICANN in connection with its Accreditation, this Agreement (including the appendices, which form part of
it) constitutes the entire agreement of the parties pertaining to the accreditation of Registrar and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or
written, between the parties on that subject.

IN
WITNESS WHEREOF, the parties hereto have caused this Agreement to be executed in duplicate by their duly authorized representatives.

ICANNBy:

/s/ KURT J. PRITZ Kurt J. Pritz Senior Vice President, ServicesTUCOWS INC.By:

/s/ ADAM EISNERName:

Adam EisnerTitle:

Director, Domain Services


---





.ASIA APPENDIX

ICANN and Tucows Inc. have entered into a Registrar Accreditation Agreement ("RAA"), of which this .ASIA Appendix ("Appendix")
is a part. Pursuant to and subject to the RAA, Registrar and ICANN hereby agree as follows:

1.Registrar Election.    Registrar hereby elects and agrees to become accredited by ICANN to provide Registrar
Services in the .ASIA TLD.

2.ICANN's Acceptance.    ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registrar Services in the .ASIA TLD.

3.Need for Agreement with Registry.    Registrar's obligation under RAA Subsection 3.1 to operate as a
registrar for the .ASIA TLD is conditioned upon the .ASIA Registry selecting Registrar as one authorized to act as a .ASIA registrar, and upon Registrar and the .ASIA Registry having an Authorizing
Agreement in effect.

4.Sponsored TLD Delegated Authority.    Registrar acknowledges that the .ASIA TLD is a sponsored TLD, over which
the .ASIA Registry has been delegated policy-formulation authority under its Sponsored TLD Registry Agreement with ICANN. The scope of delegation is currently stated in Appendix S to the .ASIA
agreement, available on the ICANN website, and includes topics that will affect the manner in which Registrar conducts its business of registering domain names in the .ASIA TLD. Registrar agrees to
comply with the requirements established by the .ASIA Registry within its delegated scope of policy-formulation authority.

5.Deviations from Obligations of this Agreement Due to Delegation.    The .ASIA Registry may develop and implement
a policy within the scope of its authority granted by its Sponsored TLD Registry Agreement with ICANN that requires Registrar to deviate from one or more obligations of this RAA. In that
event, the .ASIA Registry will notify ICANN in writing of the policy and the manner in which the .ASIA Registry believes that Registrar's obligation(s) under this RAA should be modified. Within thirty
days after this notification, ICANN will either:



IN
WITNESS WHEREOF, the parties hereto have caused this .ASIA Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesRegistrar IANA ID: 69Dated:

June 26, 2009


---



.BIZ APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".biz
Appendix") is a part.

Registrar
wishes to be accredited in the .biz TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .biz TLD. Pursuant to and
subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.    All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.    Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .biz TLD.

3.ICANN's Acceptance.    ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .biz TLD.

IN
WITNESS WHEREOF, the parties hereto have caused this .biz Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



.COM APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".com
Appendix") is a part.

Registrar
wishes to be accredited in the .com TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .com TLD. Pursuant to and
subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .com TLD.

3.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .com TLD.

IN
WITNESS WHEREOF, the parties hereto have caused this .com Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



.INFO APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".info
Appendix") is a part.

Registrar
wishes to be accredited in the .info TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .info TLD. Pursuant to
and subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .info TLD.

3.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .info TLD.

IN
WITNESS WHEREOF, the parties hereto have caused this .info Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---





.MOBI APPENDIX

ICANN and Tucows Inc. have entered into a Registrar Accreditation Agreement ("RAA"), of which this .MOBI Appendix ("Appendix")
is a part. Pursuant to and subject to the RAA, Registrar and ICANN hereby agree as follows:

1.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registrar
Services in the .MOBI TLD.

2.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registrar Services in the .MOBI TLD.

3.Need for Agreement with Registry.Registrar's obligation under RAA Subsection 3.1 to operate as a
registrar for the .MOBI TLD is conditioned upon the .MOBI Registry selecting Registrar as one authorized to act as a .MOBI registrar, and upon Registrar and the .MOBI Registry having an Authorizing
Agreement in effect.

4.Sponsored TLD Delegated Authority.Registrar acknowledges that the .MOBI TLD is a sponsored TLD, over which
the .MOBI Registry has been delegated policy-formulation authority under its Sponsored TLD Registry Agreement with ICANN. The scope of delegation is currently stated in Appendix S to the .MOBI
agreement, available on the ICANN website, and includes topics that will affect the manner in which Registrar conducts its business of registering domain names in the .MOBI TLD. Registrar
agrees to comply with the requirements established by the .MOBI Registry within its delegated scope of policy-formulation authority.

5.Deviations from Obligations of this Agreement Due to Delegation.The .MOBI Registry may develop and implement
a policy within the scope of its authority granted by its Sponsored TLD Registry Agreement with ICANN that requires Registrar to deviate from one or more obligations of this RAA. In that
event, the .MOBI Registry will notify ICANN in writing of the policy and the manner in which the .MOBI Registry believes that Registrar's obligation(s) under this RAA should be modified. Within thirty
days after this notification, ICANN will either:



IN
WITNESS WHEREOF, the parties hereto have caused this .MOBI Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



.NAME APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".name
Appendix") is a part.

Registrar
wishes to be accredited in the .name TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .name TLD. Pursuant to
and subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .name TLD.

3.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .name TLD.

4.Data Submission.Pursuant to Subsection 3.2.1, as part of its registration for SLD E-mail
forwarding, the NameWatch Service, and Defensive Registrations, Registrar shall submit to, or shall place in the Registry Database operated by, the Registry Operator for the TLD that Registry
Operator, consistent with Appendix C to its Registry Agreement with ICANN, data elements Registry Operator requires be submitted to it.

IN
WITNESS WHEREOF, the parties hereto have caused this .name Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



.NET APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".net
Appendix") is a part.

Registrar
wishes to be accredited in the .net TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .net TLD. Pursuant to and
subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .net TLD.

3.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .net TLD.

IN
WITNESS WHEREOF, the parties hereto have caused this .net Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



.ORG APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix (".org
Appendix") is a part.

Registrar
wishes to be accredited in the .org TLD pursuant to and subject to the Registrar Accreditation Agreement and ICANN wishes to accredit Registrar in the .org TLD. Pursuant to and
subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1.Definitions.All initially capitalized terms not otherwise defined herein shall have the definitions assigned
to such terms in the Registrar Accreditation Agreement.

2.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registration
Services in the .org TLD.

3.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registration Services in the .org TLD.

IN
WITNESS WHEREOF, the parties hereto have caused this .org Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---





.TEL APPENDIX

ICANN and Tucows Inc. have entered into a Registrar Accreditation Agreement ("RAA"), of which this .TEL Appendix ("Appendix") is
a part. Pursuant to and subject to the RAA, Registrar and ICANN hereby agree as follows:

1.Registrar Election.Registrar hereby elects and agrees to become accredited by ICANN to provide Registrar
Services in the .TEL TLD.

2.ICANN's Acceptance.ICANN hereby accepts Registrar's election to become accredited by ICANN to provide
Registrar Services in the .TEL TLD.

3.Need for Agreement with Registry.Registrar's obligation under RAA Subsection 3.1 to operate as a
registrar for the .TEL TLD is conditioned upon the .TEL Registry selecting Registrar as one authorized to act as a .TEL registrar, and upon Registrar and the .TEL Registry having an Authorizing
Agreement in effect.

4.Sponsored TLD Delegated Authority.Registrar acknowledges that the .TEL TLD is a sponsored TLD, over which
the .TEL Registry has been delegated policy-formulation authority under its Sponsored TLD Registry Agreement with ICANN. The scope of delegation is currently stated in Appendix S to the .TEL
agreement, available on the ICANN website, and includes topics that will affect the manner in which Registrar conducts its business of registering domain names in the .TEL TLD. Registrar agrees to
comply with the requirements established by the .TEL Registry within its delegated scope of policy-formulation authority.

5.Deviations from Obligations of this Agreement Due to Delegation.The .TEL Registry may develop and implement
a policy within the scope of its authority granted by its Sponsored TLD Registry Agreement with ICANN that requires Registrar to deviate from one or more obligations of this RAA. In that
event, the .TEL Registry will notify ICANN in writing of the policy and the manner in which the .TEL Registry believes that Registrar's obligation(s) under this RAA should be modified. Within thirty
days after this notification, ICANN will either:



IN
WITNESS WHEREOF, the parties hereto have caused this .TEL Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


---



LOGO LICENSE APPENDIX

The Internet Corporation for Assigned Names and Numbers, a California non-profit, public benefit corporation ("ICANN"), and
Tucows Inc., a Nova Scotia (Canada) Corporation ("Registrar") have entered into a Registrar Accreditation Agreement ("Registrar Accreditation Agreement"), of which this appendix ("Logo License
Appendix") is a part. Definitions in the Registrar Accreditation Agreement apply in this Logo License Appendix.

Registrar
wishes to acquire from ICANN, and ICANN wishes to grant to Registrar, a license to use the trademarks listed below the signature block of this Logo License Appendix
("Trademarks") in connection with Registrar's role as an ICANN-accredited registrar. Pursuant to and subject to the Registrar Accreditation Agreement, Registrar and ICANN hereby agree as follows:

1LICENSE



2REGISTRATION AND ENFORCEMENT



3TERM AND TERMINATION

This
Logo License Appendix shall be effective from the date it is signed below by both parties until the Expiration Date, unless this appendix or the Registrar Accreditation Agreement is
earlier terminated. Each party shall have the right to terminate this appendix at any time by giving the other party written notice. Upon expiration or termination of this appendix, Registrar shall
immediately discontinue all use of the Trademarks.

---



IN
WITNESS WHEREOF, the parties have caused this Logo License Appendix to be executed by their duly authorized representatives.

ICANN

Tucows Inc.By:

/s/ KURT J. PRITZ

By:

/s/ ADAM EISERName:

Kurt J. Pritz

Name:

Adam EisnerTitle:

Senior Vice President, Services

Title:

Director, Domain ServicesDated:

June 26, 2009


TRADEMARKS:

1.     ICANN
Accredited Registrar

---



QuickLinks