Difference between revisions of "Netlynx"
Jump to navigation
Jump to search
m (Reverted edits by Vinaymurarka (talk) to last revision by Netlynx) |
|||
| Line 22: | Line 22: | ||
[[Pankaj Jaiswal]], Chairman | [[Pankaj Jaiswal]], Chairman | ||
}} | }} | ||
| − | '''Netlynx Technologies Pvt. Ltd.''' is | + | '''Netlynx Technologies Pvt. Ltd.''' is a [[NIXI]] accredited registrar<ref>[https://www.registry.in/accredited-registrars Registry.In]</ref> providing domain name registration and hosting services in India. It provides Linux-based and Windows-based web hosting, reseller web hosting, domain names, and Internet security solutions.<ref>[http://www.netlynx.com/index.htm Netlynx Homepage]</ref> |
| − | == | + | ==History== |
| − | + | On July 6, 2005 Netlynx was accredited as a [[.in]] registrar by [[NIXI]]. Subsequently, Netlynx received [[ICANN Accreditation]]. However, it is currently not accredited by [[ICANN]]. | |
| − | |||
| − | |||
| + | ==Breach Action== | ||
| + | On January 9, 2015, ICANN issued a notice of breach to Netlynx, specifying three breaches of its Registrar Accreditation Agreement: | ||
| + | # Netlynx’s failure to take reasonable and prompt steps to investigate and respond appropriately to reports of abuse, as required by Section 3.18.1 of the RAA; | ||
| + | # Netlynx’s failure to maintain and provide records to ICANN that are related to abuse reports, as required by Section 3.18.3 of the RAA; and | ||
| + | # Netlynx’s failure to maintain and make available registration data and records available upon request by ICANN, as required by Sections 3.4.2 and 3.4.3 of the RAA.<ref>[https://www.icann.org/en/system/files/correspondence/serad-to-jaiswal-09jan15-en.pdf Notice of Breach of Registry Accreditation Agreement, January 9, 2015 (PDF)]</ref> | ||
| + | |||
| + | [[John Horton]], CEO of [[LegitScript]], speculated that the breach notice was because "roughly a quarter of the registrar’s business is dependent on rogue Internet pharmacy registrations."<ref>[https://www.legitscript.com/blog/2015/01/story-behind-icanns-breach-notice-netlynx/ LegitScript Blog - "The Story Behind ICANN's Breach Notice to NetLynx"]</ref> After extending the cure period, ICANN reported that the breaches were cured.<ref>[https://www.icann.org/en/system/files/files/compliance-update-mar15-en.pdf ICANN Compliance Report, Q1 2015 (PDF)]</ref> | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
Revision as of 20:19, 23 December 2020
 | |
| Type: | Private |
| Industry: | Registry |
| Founded: | 2005 |
| Founder(s): | Vinay Murarka |
| Headquarters: | 103, Tirupati Udyog Premises Off. Western Express Highway, |
| Country: | India |
| Employees: | 1-10 |
| Website: | Netlynx |
| Facebook: | Netlynx |
| LinkedIn: | Netlynx |
| Twitter: |  @netlynx
|
| Key People | |
| Vinay Murarka, Founder Pankaj Jaiswal, Chairman | |
Netlynx Technologies Pvt. Ltd. is a NIXI accredited registrar[1] providing domain name registration and hosting services in India. It provides Linux-based and Windows-based web hosting, reseller web hosting, domain names, and Internet security solutions.[2]
History
On July 6, 2005 Netlynx was accredited as a .in registrar by NIXI. Subsequently, Netlynx received ICANN Accreditation. However, it is currently not accredited by ICANN.
Breach Action
On January 9, 2015, ICANN issued a notice of breach to Netlynx, specifying three breaches of its Registrar Accreditation Agreement:
- Netlynx’s failure to take reasonable and prompt steps to investigate and respond appropriately to reports of abuse, as required by Section 3.18.1 of the RAA;
- Netlynx’s failure to maintain and provide records to ICANN that are related to abuse reports, as required by Section 3.18.3 of the RAA; and
- Netlynx’s failure to maintain and make available registration data and records available upon request by ICANN, as required by Sections 3.4.2 and 3.4.3 of the RAA.[3]
John Horton, CEO of LegitScript, speculated that the breach notice was because "roughly a quarter of the registrar’s business is dependent on rogue Internet pharmacy registrations."[4] After extending the cure period, ICANN reported that the breaches were cured.[5]