Common use of Technical Feasibility of String Clause in Contracts

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 2156 contracts

Sources: Registry Agreement, Registry Agreement, Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top-level domain strings across the Internet, certain top-­‐level top-level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 117 contracts

Sources: Registry Agreement, Registry Agreement, Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top‐level domain strings across the Internet, certain top-­‐level top‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 18 contracts

Sources: Registry Agreement, Registry Agreement, Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters webhosts and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 3 contracts

Sources: TLD Registry Agreement, Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top-level domain strings across the Internet, certain top-­‐level top- level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 3 contracts

Sources: Registry Agreement, Registry Agreement, Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters webhosterswebhosts and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 2 contracts

Sources: Sponsored TLD Registry Agreement, TLD Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level topLlevel domain strings across the Internet, certain top-­‐level topLlevel domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 1 contract

Sources: Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level topMlevel domain strings across the Internet, certain top-­‐level topMlevel domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 1 contract

Sources: Registry Agreement

Technical Feasibility of String. Certain While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top-level domain strings across the Internet, certain top-­‐level top-level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 1 contract

Sources: New GTLD Registry Agreement

Technical Feasibility of String. While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top-level domain strings across the Internet, certain top-­‐level top-level domain strings may encounter difficulty in acceptance by ISPs and webhosters webhosts and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 1 contract

Sources: Sponsored TLD Registry Agreement

Technical Feasibility of String. While CertainWhile ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level top-level domain strings across the Internet, certain top-­‐level top-level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

Appears in 1 contract

Sources: New GTLD Agreement