Reference Source

35 Technology Co., Ltd.

What is the icann enforcement action for 35 Technology Co., Ltd.?

For 35 Technology Co., Ltd., registrar is 35 Technology Co., Ltd; icann enforcement action is Notice of Breach; notice date is 9 November 2015; notice document is https://www.icann.org/en/system/files/correspondence/serad-to-yu-09nov15-en.pdf, verified against its source on 2026-09-07.

9 November 2015: <https://www.icann.org/en/system/files/correspondence/serad-to-yu-09nov15-en.pdf> ICANN Sends Notice of Breach to Registrar (35 Technology Co., Ltd.) Data and Documents Under Review by ICANN; Cure Period Extended Until 30 December 2015; Breaches Cured

icann.org, retrieved 2026-08-06

Registrar
35 Technology Co., Ltd. verified
ICANN enforcement action
Notice of Breach verified
Notice date
9 November 2015 verified
Notice document
https://www.icann.org/en/system/files/correspondence/serad-to-yu-09nov15-en.pdf verified
Sourceicann.org
Verified
Review by
DatasetDomain registrar accreditation status and ICANN enforcement history, by IANA ID

The same source also states

22 August 2014: <https://www.icann.org/en/system/files/correspondence/serad-to-yu-22aug14-en.pdf> ICANN Sends Notice of Breach to Registrar (35 Technology Co., Ltd.) Data and Documents Under Review by ICANN; Cure Period Extended to 24 September 2014; Data and Documents Under Review by ICANN; Cure Period Extended to 14 October 2014; Cure Period Extended Until 27 October 2014; Breaches Cured

icann.org, retrieved 2026-09-07

Source

Last verified against source: . Due for re-check by . This page as Markdown · OKF bundle · full dataset as JSON.

This one changes, and we watch it.Domain registrar accreditation status and ICANN enforcement history, by IANA ID is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.