Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
ICANN’s public notices document compliance problems involving Xin Net Technology Corporation in 2012 and 2018, but the records reviewed do not establish whether Xin Net is accredited or operating today. Nor do they prove that Xin Net is objectively the “worst” registrar: no comparative ranking or dataset supports that label. Here is what the dated notices say, what remains unknown, and how to protect a domain if you are considering a transfer.
What ICANN’s notices say about Xin Net
The strongest available evidence is a pair of dated ICANN records. They document specific historical compliance issues; they are not a current status report or a measure of every customer’s experience.
2012: fees and AuthInfo codes
In correspondence dated July 31, 2012, ICANN stated that Xin Net owed $2,000 in past-due accreditation fees. The correspondence also described earlier compliance exchanges and stated that Xin Net had failed to provide AuthInfo codes within five calendar days in cases involving three named domain names. The figure and code findings belong to that historical record, not to Xin Net’s current balance or every registrant’s experience. Read ICANN’s 2012 correspondence.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2018: multiple compliance areas
ICANN’s January 17, 2018 breach notice listed problems involving past-due accreditation fees, Whois response formatting, disclosure of auto-renewal policy and renewal and post-expiration fees, current documentation of legal establishment and good standing, and publication of the registrar’s correspondence address and officers’ names and positions. The materials cited here do not establish the final disposition of the notice or whether every issue was later corrected. Read ICANN’s January 2018 breach notice.
#1 Best Overall
Does that make Xin Net the “worst” registrar?
Not on the evidence available here. “Worst” is an opinionated framing, not a measured result: no cross-registrar dataset or comparative study in these records establishes that Xin Net ranks last. The notices support saying that ICANN documented compliance problems in particular years. They do not quantify complaint volume, affected registrants, or performance relative to other registrars.
For a meaningful comparison, check each registrar’s current accreditation and enforcement notices, the clarity of its initial, renewal, post-expiration, and restore fees, its auto-renewal and deletion policies, transfer-out rules and AuthInfo/EPP-code access, account and registration-data security, and escalation channels. The 2018 notice makes fee and policy disclosure sensible areas to scrutinize; it says nothing by itself about the current quality of other registrars.
Is Xin Net accredited and operating now?
The historical notices alone cannot answer that. The evidence cited here does not establish Xin Net’s present accreditation, whether it is accepting registrations, or whether it is accepting inbound transfers. Do not infer current suspension, termination, or normal operation from notices dated 2012 and 2018. ICANN’s public notices index is a place to check enforcement developments, but confirm present accreditation in a current ICANN registrar profile and look for any applicable current notice.
Recommended Free Tools
ICANN explains that suspension may temporarily prevent a registrar from sponsoring new domains or initiating inbound transfers while it has an opportunity to address accreditation obligations. Suspension is distinct from termination. That general explanation describes possible effects, not Xin Net’s status today. See ICANN’s explanation of registrar suspension.
How to prepare to transfer a domain away
The following is general registrar-transfer guidance, not a verified Xin Net-specific procedure. Check your TLD’s rules and the current instructions from both registrars before starting.
- Check the domain record and expiry date. Confirm the domain’s current registration and expiration details. Leave enough time to handle any lock, renewal, or eligibility issue.
- Secure account access and contact details. Make sure you can sign in to the current registrar account and access the email address used for domain-related approvals.
- Review transfer requirements. Check the current registrar’s transfer-out process, whether a transfer lock applies, and any expiry-related constraints. Request the AuthInfo or EPP code through the registrar’s verified channel.
- Confirm the receiving registrar supports the TLD. A provider’s general transfer service does not guarantee it accepts every domain extension.
- Start the transfer with the receiving registrar and monitor messages. Follow its instructions and watch the domain contact email for approval or verification requests.
ICANN says a registrar suspension can affect inbound transfers. Check current notices and the domain’s own status before relying on a transfer as an immediate workaround. ICANN’s suspension guidance explains the general limitation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Where to complain about a registrar
Use ICANN’s registrar complaint guidance to select the form for the issue—for example, a complaint about registration-data accuracy or certain suspension or deletion situations. ICANN’s remit is limited to obligations under its agreements and consensus policies. It may not handle a service-quality or customer-service dispute outside that scope, and filing a complaint does not mean ICANN will resolve an individual dispute or restore a domain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
