AirFX, LLC is Free-Falling Without a Parachute
Although we at DefendMyDomain often blog about UDRP domain name decisions. Sometimes, those decisions go another level higher, into the U.S. federal courts. Under action 15 U.S.C. § 1114(D)(v) a domain name registrant can file a civil action asking the Federal Courts to resolve the dispute. This is sometimes referred to as a reverse domain name hijacking case, depending on the specifics of the case. The prior domain name dispute decision AirFX, LLC v. ATTN AIRFX.COM ( Nat. Arb. Forum FA1384655, May 16, 2011)(available here), was decided by a single member Panel. The Complainant convinced the single member Panel that the elements of the UDRP policy had been met. We are not going to spend time rehashing the elements of that decision, because once the dispute is brought in Federal Court, the UDRP decision is essentially irrelevant. This is an important lesson for those who seek to use the UDRP system. 15 U.S.C. § 1114(D)(v) allows an aggrieved party to seek binding federal court intervention.
Marc J. Randazza, of The Randazza Legal Group, filed the complaint on behalf of the Respondent, which follows well established pleading standards and requirements for these types of actions. (available here) However, the Complainant/Defendant AirFX, LLC, has filed a motion to dismiss, alleging among other things a 12(b)(6) allegation, and other unbelievable theories and accusations. (available here). Among the odd and interesting accusations by AirFX, LLC, they complain that the respondent/plaintiff for the first time is alleging reverse domain name hijacking. This is a misunderstanding of cause of action permitted under 15 U.S.C. § 1114(D)(v). Additionally since the decision at the UDRP level has absolutely no precedential or binding effect, this concept is misplaced. A reverse domain name highjacking claim is one which is permissible in order to prove that the domain name registrants registration was not unlawful.
AirFXS also complains about the location, namely Arizona District Court, in which the case was filed. One of the things that is clear, is when you file a UDRP, you affirmatively select and agree to one of two jurisdictions for a Federal Court challenge. (1) the location of the principal office of the concerned registrar or or (2) where the Respondent is located, as shown by the address(es) given for the domain name holder in the Whois Database at the time of the submission of the Complaint. See UDRP Rule 3(b)(xiii). AirFX asks the Court to transfer the case to another district, namely the Southern District of Indiana. This concept is dead on arrival though, since AirFX was the one demanded the jurisdiction for the resolution of all disputes thus waived any challenge to the jurisdiction.
Essentially, the Motion to Dismiss provides no controlling authority of any kind in the dismissal section. When parties seek to take domains to which they are not entitled, the arguments are often weak. We have seen the Randazza Legal Group in action before and know that AirFX will have their work cut out for them.
We will continue to monitor this case and provide updates. We thought it was an important lesson to provide our readers with an understanding of which arguments should not be raised when defending a reverse domain name highjacking case under 15 U.S.C. § 1114(D)(v).