Registrar reg.ru IMPOTENT response to my fraud report
https://www.reg.ruQuote
Отдел рассмотрения жалоб
Dear Sir/Madam,
"Registrar of the domain names REG.RU" LLC. is an Accredited Registrar of the domain names acting on the basis of effective legislation and regulatory documents.
The REG.RU Company is not authorized to make any conclusions about intellectual property rights violation. Only the law enforcement agencies are authorized to take any decisions about intellectual property rights violation as it should be appropriate facts and judgment for each case.
In your turn you have to apply to the appropriate authorized law agencies to commence legal proceedings about intellectual property rights violation.
"Registrar of the domain names REG.RU" LLC. is an Accredited Registrar of the domain names acting on the basis of Registration rules and Regulations where it is said that the domain name Administrator is fully responsible for the web site content.
Based on Regulations the Registrar may not independently decide on satisfying the third parties’ claims for the domain name. Based on Regulations the Registrar may not independently decide on satisfying the third parties’ claims for the domain name.
Extract from the Rules:
2.9. “The Registrar may not independently decide on satisfying the third parties’ claims for the domain name.
A person suggesting that administration of the domain name by his/her Administrator abuses his/her rights (specifically, those of trade mark, brand name, other object of intellectual property, the name of a nonprofit organization or government body) may file a corresponding legal statement”.
In such way the REG.RU Registrar is acting on the basis of Regulations and can not violate it.
Delivered-To: xxxxxx
Received: by 10.31.139.209 with SMTP id n200csp360078vkd;
Sat, 27 Feb 2016 05:33:22 -0800 (PST)
X-Received: by 10.112.198.162 with SMTP id jd2mr1991223lbc.53.1456580002397;
Sat, 27 Feb 2016 05:33:22 -0800 (PST)
Return-Path: <
[email protected]>
Received: from otrs.reg.ru (support.reg.ru. [31.31.205.141])
by mx.google.com with ESMTPS id bb6si8290373lbc.32.2016.02.27.05.33.22
for <xxxxx>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sat, 27 Feb 2016 05:33:22 -0800 (PST)
Received-SPF: pass (google.com: domain of
[email protected] designates 31.31.205.141 as permitted sender) client-ip=31.31.205.141;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of
[email protected] designates 31.31.205.141 as permitted sender)
[email protected];
dmarc=pass (p=NONE dis=NONE) header.from=reg.ru
Received: from otrs.reg.ru (localhost [127.0.0.1])
by otrs.reg.ru (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id u1RDXQRN021331
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
for <txxxxxx>; Sat, 27 Feb 2016 16:33:26 +0300
Received: (from www-data@localhost)
by otrs.reg.ru (8.14.4/8.14.4/Submit) id u1RDXQff021330
for <xxxxxx>; Sat, 27 Feb 2016 16:33:26 +0300
X-Authentication-Warning: otrs.reg.ru: www-data set sender to
[email protected] using -f
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Ticket#2016022610068104] FYI. Fake/Spoof of afterdawn.com
X-Powered-BY: OTRS - Open Ticket Request System (
http://otrs.org/)
X-Mailer: OTRS Mail Service (3.0.10)
Date: Sat, 27 Feb 2016 16:33:25 +0300
Precedence: bulk
Message-ID: <
[email protected]>
To: xxxxxx
From: =?UTF-8?Q?=D0=9E=D1=82=D0=B4=D0=B5=D0=BB=20?=
=?UTF-8?Q?=D1=80=D0=B0=D1=81=D1=81=D0=BC=D0=BE=D1=82=D1=80=D0=B5=D0=BD=D0=B8=D1=8F=20?= =?UTF-8?Q?=D0=B6=D0=B0=D0=BB=D0=BE=D0=B1=20?=<
[email protected]>
In-Reply-To: <CACrP1nLYED1vx6ZM+ziMopdLq13SPF=g9JoJU57+Eddzy1Zi6A@mail.gmail.com>
References: <CACrP1nLYED1vx6ZM+ziMopdLq13SPF=g9JoJU57+Eddzy1Zi6A@mail.gmail.com>