In the fall of 2006, the founder of a Korean game company sent a domain name owner in California what he hoped was a closing offer: $40,000 for gopets.com. His company had spent two years trying to get the name, first for $750, then with a threat to file a dispute, then by actually filing one and losing. The owner's reply came as a four-page letter addressed to the company's investors. It warned of confused users and "competitive Meta Tagging" and named a new price of $5 million. Two days later the owner moved the name to a corporation he and his brother controlled.
That sequence ended in a Ninth Circuit opinion that still divides the federal courts, and it contains most of what can go wrong on the buy side of the domain market. The offer was evidence. The failed dispute was a stated reason for the offer. The change of registrant, a clerical act that takes minutes, became the question the appeal turned on.
Most people who want a taken domain name are not cybersquatting victims and have no case against anyone. They are buyers. A founder sees a parked page with a "make an offer" link and a stranger's $40,000 price tag, and the questions are ordinary commercial ones. What am I buying? How do I know the seller owns it? How does it actually move? What did I just walk into? The corpus of domain law was written mostly for disputes, so those questions tend to get answered in passing. This article answers them directly.
The short answer
- You are buying a registrant's position, not a thing. A domain name is a contract with a registrar, recorded in a registry's database. Many courts treat that position as intangible property. Virginia, home of the .com registry, has treated it as a contract for services in at least one context.
- A purchase is a new event for bad faith purposes under the UDRP. Panels look at the date the current registrant acquired the name, whatever its creation date says. A 1998 registration date does not protect a 2026 buyer who bought with a 2010 trademark in view.
- Federal courts are split on the same question under the ACPA. The Third, Fourth, and Eleventh Circuits treat a re-registration as a registration. The Ninth Circuit does not, and Arizona district courts have applied its rule to arm's-length buyers. The rest of the country is open, and at least one district court in the Seventh Circuit has rejected the Ninth Circuit's view.
- Good faith is still the buyer's main protection. Under every version of the rule, a buyer with a real business reason, no eye on someone else's mark, and dated proof of both is in a strong position. Buyers lose when they park the name on an ad page, offer no credible story, and hold a portfolio of other people's brands.
- A stolen name can be taken back from an innocent buyer. The Ninth Circuit's CRS Recovery decision turns on whether the original owner lost the name by theft (void title) or fraud (voidable title). Checking WIPO for prior disputes, as that buyer did, was not enough to end the case.
- The transfer mechanics create real traps. Under the Transfer Policy still in force, a change of registrant can lock the name against moving registrars for 60 days. ICANN's Board adopted reforms on 7 June 2026 that remove that lock and standardize other periods at 30 days, but they await implementation.
- Offers are evidence. Panels treat purchase talks as admissible and courts have relied on broker emails. Filing a UDRP complaint after a failed purchase, without a plausible legal basis, is a listed ground for a finding of reverse domain name hijacking (bad faith misuse of the process by the complainant).
- Used domains carry baggage. Mail addressed to the old owner still arrives, old TLS certificates may still be valid, and the name may be on blocklists. Those are closing tasks and diligence items, and they are cheap if you do them in order.
What you are actually buying
Three actors matter. A registry runs the authoritative database for a top-level domain; Verisign does this for .com. A registrar is an accredited retailer that writes records to that database for its customers. A registrant is the customer. The Ninth Circuit's short description, quoted in GoPets Ltd. v. Hise, 657 F.3d 1024 (9th Cir. 2011), from Office Depot Inc. v. Zuccarini, 596 F.3d 696 (9th Cir. 2010), is the one most courts now use. For the structure of the top-level domain system, see Top-Level Domain Names: An Overview.
The registrant has a registration agreement with the registrar for a fixed term, renewable on the registrar's then-current terms. The agreement incorporates ICANN consensus policies, including the Uniform Domain-Name Dispute-Resolution Policy (UDRP) and the Transfer Policy. So when you buy a name, you step into a contract chain that has an arbitration-like remedy baked into it, and you accept that chain at the moment you become registrant.
Whether the result is "property" depends on where you ask and why. Kremen v. Cohen, 337 F.3d 1024 (9th Cir. 2003) applied California's three-part test and held that a domain name is an interest capable of precise definition, capable of exclusive control, and one in which the registrant has a legitimate claim to exclusivity, so it can be converted. Like a share of stock or a plot of land, the panel wrote, it is a well-defined interest. Network Solutions, Inc. v. Umbro International, Inc., 529 S.E.2d 80 (Va. 2000) went the other way in a garnishment case, holding that a registration is the product of a contract for services and that the contractual right is "inextricably bound" to the registrar's services. The Ninth Circuit later read Umbro narrowly in CRS Recovery, noting that the Virginia court had declined to decide whether a domain name is a form of intellectual property, and observed that a majority of states to reach the question recognize a property interest. Treatise writers remain uneasy. Norton Bankruptcy Law and Practice § 177:50 says it remains unclear whether a registration is merely a contract right or a broader general intangible held subject to the contract.
Congress hedged too, and helpfully. The in rem provision of the ACPA gives a domain name a statutory situs where its registrar or registry sits, 15 U.S.C. § 1125(d), and the Fourth Circuit took that as a sign that Congress saw registrants as holding "a property-like interest." Office Depot used the same provision to support treating names as personal property that a receiver could reach.
For a buyer, the taxonomy matters in three ways. It affects whether you can sue in conversion if the name is taken from you. It affects which creditor remedies might already reach the name in the seller's hands. And it explains why a purchase agreement has to do two jobs: assign whatever rights the seller has, and require the seller to perform the acts in the registrar's system that make the assignment real. Paper alone moves nothing.
Who is on the other end of the parked page
The seller is usually one of five people, and each one negotiates differently.
A domain investor holds names as inventory, prices them with reference to comparable sales, and expects a broker's inquiry. Many list on marketplaces such as Sedo or the GoDaddy family of aftermarket services, and many will take a "buy it now" price without conversation. Investing as such is lawful, and the UDRP says so through its panels: registering a name for resale, even for profit, does not by itself show bad faith (WIPO Overview 3.1, section 3.1.1).
A dormant business or hobbyist registered the name long ago and has forgotten it. These sellers may be cheap, slow, and hard to find, and they often have the worst records. The account may be tied to a dead email address, which is both a closing problem and a theft signal.
An operating business uses the name and would have to migrate. The price reflects its switching cost, and the deal looks like a small asset purchase with transition services.
A cybersquatter holds the name because it matches someone's brand. If that brand is yours, you may have a remedy, which changes the math discussed below. If the brand belongs to someone else, you should not be buying.
A thief or front holds a name that belongs to someone else. This seller looks like the others, except for a few signs we will get to.
Between buyer and seller sit brokers and marketplaces. A marketplace lists inventory, runs a landing page on the name itself, and takes a commission. A buy-side broker represents you, approaches the holder without naming you, and is paid by percentage or flat fee. Percentages vary by channel and are negotiable; figures in a range of roughly 10 to 25 percent are commonly quoted, so get the number and who pays it in writing. A marketplace or a broker who merely connects the parties does not itself traffic in the name under the ACPA. In Bird v. Parsons, 289 F.3d 865 (6th Cir. 2002), the Sixth Circuit held that an auction site was not liable for trafficking merely because its services might be used for it, and that a registrar collecting its fees was not trafficking either.
Why you cannot simply look up the owner
For most of the internet's history, anyone could run a WHOIS query and read the registrant's name and address. That changed with the European General Data Protection Regulation in 2018. ICANN responded with a temporary specification, and the permanent replacement, the Registration Data Policy, took effect on 21 August 2025. For most generic top-level domains, a public lookup now shows the registrar, key dates, status codes, and name servers, while the registrant's identity is usually redacted.
The protocol changed as well. RDAP (Registration Data Access Protocol) is the structured successor to WHOIS, and according to ICANN, registries and registrars have not been required to offer WHOIS since 28 January 2025, with exceptions including the .com registry. A buyer should learn to read an RDAP response, because the public fields do useful work even with the name blanked:
| Field | What it tells a buyer |
|---|---|
| Creation date | When the current unbroken registration began. A name that lapsed and was re-created shows the later date, which is a cheap test for a prior drop. |
| Updated date | When the record last changed. A very recent change on an old name is a question to ask. |
| Expiration date | How much term you are buying, and whether the name is about to enter a grace period. |
| Registrar and IANA ID | Who sponsors the name, and who would act on a transfer. |
| Status codes | Whether locks or holds apply: clientTransferProhibited, serverTransferProhibited, redemptionPeriod, pendingDelete, and others. |
| Name servers | Where DNS is hosted, which often reveals a parking provider or marketplace. |
To reach an anonymous holder, buyers use the marketplace's inquiry form, the registrar's contact-the-registrant relay, a broker, or the link on the parked page. ICANN's Registration Data Request Service, which the Board in October 2025 extended for up to two years after the pilot ended in November 2025, routes disclosure requests to participating registrars, but it is designed for parties with a legitimate need such as law enforcement or rights enforcement, and a registrar has no obligation to give a curious shopper the data. A UDRP complaint will unmask the holder, as Prudential learned when the provider relayed the registrant's data days after filing, but that is a strange way to start a purchase. For the disputes side of unmasking, see Beyond the UDRP: Uniform Rapid Suspension, Country-Code Domain Disputes, In Rem ACPA Actions, and Reverse Domain Name Hijacking.
How a name dies and gets caught
Some names reach the market because the holder stopped paying. The sequence differs by registry and registrar, but the gTLD outline is this.
Under ICANN's Expired Registration Recovery Policy, the registrar must send at least two notices before expiration, approximately one month and one week out, plus one more within five days after. It must also interrupt the DNS path for a period after expiration so the holder notices. Most registrars then keep the name in a post-expiration period set by contract, and many auction it during that window through expired-name marketplaces. If the holder never returns, the name is deleted and enters a 30-day Redemption Grace Period, where available, during which the former holder can still restore it at a price. Then comes a short pending-delete stage, and then the name drops back into the pool.
Drop catching is the business of being first when it does. Specialized registrars hold many connections to the registry and fire create commands at the moment of release. Backorder services take a fee and auction the result when several customers want the same name.
Two legal points follow. First, an auction bidder during the post-expiration period is buying subject to whatever the registrar's agreement says and to the former holder's remaining recovery rights. Read those terms; a winning bid may be refunded if the old registrant renews. Second, a dropped name is a fresh registration in every sense that matters. The creation date resets, the UDRP clock runs from your acquisition, and even the Ninth Circuit's favorable rule may be unavailable. In JFXD TRX ACQ LLC v. trx.com, No. 2:23-cv-02330 (D. Ariz. May 8, 2024), the court drew the line itself, stating that purchasing a name through a brokerage and registering a lapsed name with a registrar "are very different events." In that fee order, the court was explaining why it had dismissed a plaintiff who had not alleged facts showing that a lapse had occurred, so the remark is not a holding on the lapse scenario. A cautious buyer should still assume a drop gets none of the prior holder's history.
What happens in the machinery at closing
Understanding the plumbing explains most of the closing risk. A domain name "moves" in one of two ways, and they are different events with different consequences.
Inter-registrar transfer
The name goes from the seller's registrar to the buyer's. The technical steps under EPP (Extensible Provisioning Protocol, the language registrars use to talk to registries) are these. The seller removes the clientTransferProhibited status, usually called the registrar lock, and obtains an authorization code, which the current policy calls an AuthInfo code. The seller gives the code to the buyer. The buyer starts a transfer at the gaining registrar and enters the code. The registry validates it, sets the name to pendingTransfer, and notifies the losing registrar. The losing registrar then has five calendar days to approve or reject, and silence counts as approval (Transfer Policy § I.A.3.5). On completion, the registrar of record changes. For most gTLDs the registry adds a year of term, which the buyer pays for through the gaining registrar.
Note what did not change. The transfer alone does not rewrite the registrant data. The seller's details may still sit on the record until the new registrar's account holder updates them.
Change of registrant
This is a change in who holds the name, with or without a change of registrar. Marketplaces often do it as an account "push," moving the name between two customers of the same registrar in minutes. The Transfer Policy treats a Material Change to the registrant's name, organization, or email address as a Change of Registrant under Part II. The registrar must obtain confirmation from both the prior and the new registrant, or a Designated Agent authorized by either, and must notify both.
Here is the trap. Section II.C.2 requires the registrar to impose a 60-day inter-registrar transfer lock after a Change of Registrant, although the registrar may let the holder opt out before the request. The policy itself warns the prior registrant to do any inter-registrar transfer first. So the sequence matters. A buyer who takes a push at the seller's registrar, updates the data, and then tries to move to a corporate registrar may find the name stuck for two months, sitting in an account structure nobody planned for. Separately, a registrar may deny a transfer within 60 days of the name's creation or of a prior transfer, which is why a recently moved name can stall a closing and why it is worth asking about.
What ICANN changed in 2026, and what has not changed yet
ICANN's Transfer Policy Review Working Group reached full consensus on 47 recommendations on 31 January 2025. The GNSO Council approved them on 12 March 2025, and on 7 June 2026 the ICANN Board adopted them in Resolution 2026.06.07.04, directing implementation "subject to prioritization." For a buyer, the changes that matter are these:
| Topic | Policy now in force | Adopted recommendation (not yet in effect) |
|---|---|---|
| Name of the code | AuthInfo code | Transfer Authorization Code (TAC), Rec. 4 |
| Code life | Set by practice | Valid for 336 hours (14 days), then expires, enforced at the registry, Rec. 9 |
| Code reuse | Not addressed in these terms | One-time use, Rec. 13 |
| Restriction after creation | Registrar may deny within 60 days (§ I.A.3.7.5); some registry agreements require it | 720 hours (30 days) across gTLDs, Rec. 3 |
| Restriction after a transfer | Up to 60 days | Mandatory 720 hours (30 days), early removal only on stated conditions, Rec. 18 |
| Change-of-registrant lock | 60 days unless opted out | Eliminated, Rec. 26.4 |
| Confirmation by both parties to a registrant change | Required | Eliminated in a new standalone Change of Registrant Data Policy, Rec. 26.3 |
| Notice after a registrant data change | Notice to both | Notice to the holder, including at the prior email, within 24 hours, subject to an opt-out, Recs. 27 and 28 |
We could not confirm an effective date as of this document's last modified date. Registrars will implement on the schedule ICANN sets, and individual registrars may already behave differently. Write the closing run sheet against the current rule, confirm with the actual registrars in the deal, and treat a 14-day code life as coming.
The reforms cut both ways. A buyer closing a deal in the future should have fewer stranded names. A victim of account takeover will have less friction between the thief and a resale, which makes the provenance questions below more important.
Escrow
Domain escrow solves a simple problem: the buyer will not wire before the name moves, and the seller will not move the name before the wire. A licensed escrow agent takes the money, tells the seller to start the transfer, gives the buyer an inspection period after the name arrives, and releases the funds. In California, escrow agents are licensed under the Escrow Law, Cal. Fin. Code § 17000 and following, and buyers should confirm the agent's status wherever it operates.
An escrow agent checks money and instructions. It does not check title in any legal sense, and it does not resolve whether the seller stole the name. Escrow reduces performance risk and does nothing about provenance risk. The MC Law pieces on Escrows, Holdbacks, and Purchase Price Security: Who Holds the Money and Who Gets It Back and Setting Up and Administering a Deal Escrow: A Practical Guide address the deal-escrow form. Large or complicated domain deals borrow from that practice, with holdbacks and survival periods.
DNS is the last step and the easy one to botch
A registrar transfer does not itself point your name anywhere. DNS (the Domain Name System) answers queries according to name server records at the registry and zone files on those servers, and resolvers cache answers according to their time-to-live values. If the seller's zone was DNSSEC-signed, stale delegation-signer records can make the name fail validation for security-aware resolvers until they are removed or replaced. So the operational order is roughly this: stand up the new zone, lower the old TTLs where you can, deal with DNSSEC, change name servers, watch, and only then announce.
The hazard no seller can cure: the bad faith clock restarts
The UDRP is a contract term. A complainant must prove three things under paragraph 4(a): the name is identical or confusingly similar to a mark in which it has rights; the respondent has no rights or legitimate interests; and the name "has been registered and is being used in bad faith." The remedies are limited to cancellation or transfer. Panels generally apply these by paper, without discovery, in about two months.
The word that matters to a buyer sits in paragraph 4(b)(i), which lists as evidence of bad faith that you "have registered or you have acquired" the name primarily to sell it to the mark owner or its competitor. Acquisition counts. And WIPO's consensus view, in Overview 3.1 (published 17 February 2026, superseding 3.0), says it plainly at section 3.9:
"[T]he transfer of a domain name registration from a third party to the respondent is not a renewal and the date on which the current registrant acquired the domain name is the date a panel will consider in assessing bad faith. This holds true for single domain name acquisitions as well as for portfolio acquisitions."
Section 3.8.1 adds that when a respondent acquires a name after the complainant's rights accrue, "the panel will look to the circumstances at the date the UDRP respondent itself acquired the domain name." The logic is simple. The prior holder's innocence was personal. A panel asks what you knew and intended when you decided to take the name. Mere renewal by the same registrant does not count, and panels typically will not treat formal contact updates with an unbroken chain of possession as new registrations, but a real sale does.
A related rule catches privacy services. If the record is masked and the complainant credibly alleges a change of hands, section 3.9 says the respondent must show an unbroken chain, and failure may support an inference of concealment.
What this means in a worked example
Suppose a Boise software company, Orrinfield Systems, pays $18,000 in 2026 for orrinfield.com. A genealogy hobbyist registered the name in 2004 and parked it. In 2015, a Scottish outdoor-clothing maker began selling under ORRINFIELD and now holds U.S. and U.K. registrations.
The hobbyist could never have lost a UDRP case: in 2004 there was no mark to target. Orrinfield Systems stands in a different place. It bought in 2026, when the clothing mark existed, so panels will test its 2026 intent. Its defense is on the merits, and it is a good one on these assumptions. It has a business under the name, it has no interest in outdoor clothing, it did not buy to sell to the Scots or to divert their customers, and it has dated formation papers and a launch plan. UDRP paragraph 4(c)(i) protects use or demonstrable preparations to use the name for a bona fide offering before notice of the dispute. Overview 3.1 section 2.2 lists what counts, including business formation, investment in development and promotional materials, and a genuine business plan, and it wants "clear contemporaneous (and ideally, dated) evidence."
Change one fact. Orrinfield Systems parks the name for two years on a registrar page full of links to hiking jackets, while the launch slips. Now the complaint writes itself. Overview 3.1 section 3.1.1 lists website content targeting the mark, "e.g., through links to the complainant's competitors," among the circumstances indicating bad faith, and paragraph 4(b)(iv) reaches attempts to attract users for commercial gain by creating confusion. The buyer's good story is now competing with its own landing page.
Being a dictionary word helps but is no safe harbor. Section 2.10 explains that a dictionary term does not automatically confer a legitimate interest, and that a respondent's site aimed at the mark's field is not protected. Section 3.2.3 says that domain investors in particular may have an affirmative duty to screen their acquisitions for trademark conflicts. Paragraph 2 of the policy itself says it is the registrant's responsibility to determine whether a registration infringes someone else's rights.
The ACPA split, read closely
The federal statute is 15 U.S.C. § 1125(d). A mark owner can sue a person who "has a bad faith intent to profit" from the mark and who "registers, traffics in, or uses" a domain name that, "in the case of a mark that is distinctive at the time of registration of the domain name," is identical or confusingly similar. Remedies include transfer and, under 15 U.S.C. § 1117, statutory damages between $1,000 and $100,000 per domain name, plus fees in exceptional cases.
Congress wrote the statute in 1999 to stop what the Fourth Circuit called the Internet version of a land grab, with the holding of names for ransom as its paradigm (Southern Grouts collects the descriptions). A statute aimed at ransom was bound to catch some honest resale at the edges, and nearly every hard case since has been about keeping those two apart.
Two features of that text matter to a buyer. "Traffics in" is defined in § 1125(d)(1)(E) to include "sales, purchases, loans, pledges, licenses, exchanges of currency, and any other transfer for consideration." So the act of buying is itself a covered act, if done with the required intent. And the statute fixes distinctiveness at "the time of registration" without defining registration. Everything else in this section flows from that omission.
Schmidheiny: the Third Circuit starts it
Steven Weber registered schmidheiny.com in February 1999, before the ACPA existed. In June 2000 a corporation he ran became the new registrant, at a new registrar, for a new one-year term. In November 2000, he emailed the billionaire's assistant offering to sell. The claim arose under what is now 15 U.S.C. § 8131, the provision on living persons' names. The district court held the 1999 creation date controlled.
The Third Circuit reversed in a short opinion. "The words 'initial' and 'creation' appear nowhere" in the section. Schmidheiny v. Weber, 319 F.3d 581 (3d Cir. 2003) held that "the word 'registration' includes a new contract at a different registrar and to a different registrant," and it worried that the contrary view would allow names to be "sold and purchased without the living persons' consent, ad infinitum."
GoPets: the Ninth Circuit goes the other way
The facts opened this article. Edward Hise registered gopets.com in 1999, five years before the game company existed. After the failed dispute and the $5 million letter, he transferred the name to Digital Overture, the corporation he owned with his brother. The district court held that transfer a registration and granted summary judgment for the mark owner.
GoPets Ltd. v. Hise, 657 F.3d 1024 (9th Cir. 2011) reversed as to gopets.com. The court began by listing what could conceivably count as registration: updating contacts, switching to private registration, changing registrars, changing the registrant, transferring the domain and the payment duties, renewing. Then it turned to property. Hise could have kept all his rights forever by keeping the name in his own name. "We see no basis in ACPA to conclude that a right that belongs to an initial registrant of a currently registered domain name is lost when that name is transferred to another owner." The rule the mark owner wanted "would make rights to many domain names effectively inalienable." It disagreed with Schmidheiny, reasoning that the Third Circuit's worry about pre-ACPA names disappears once one follows Sporty's Farm L.L.C. v. Sportsman's Market, Inc., 202 F.3d 489 (2d Cir. 2000) and applies the statute to pre-enactment registrations.
Two things are easy to miss. First, the winners were not sympathetic, and they did not win everything. The panel upheld the bad faith finding on the eighteen additional names, such as gopets.mobi and mygopets.com, that the Hises registered after the mark was distinctive, concluding that they were meant to divert consumers. Second, the transfer at issue was to an affiliate. Later courts have divided over how much weight that deserves. The Fourth Circuit described it as a "minor, nominal change in ownership." Arizona courts have applied GoPets to arm's-length buyers anyway.
Jysk and Prudential: the majority forms
Jysk Bed'N Linen v. Dutta-Roy, 810 F.3d 767 (11th Cir. 2015) involved a contractor who had listed himself as owner of his client's domain. When the registration expired in 2012, he refused to re-register it for the client, re-registered it himself, added three variants, and offered to give them up for payment for his work. The Eleventh Circuit read "register" by its dictionary meaning: "a re-registration is, by definition, a registration." It added that exempting bad faith re-registrations "would be nonsensical." Those were an insider's facts and a preliminary injunction, and the same registrant was involved on both sides of the line, yet the holding is general.
Prudential Insurance Co. of America v. Shenzhen Stone Network Information Ltd., 58 F.4th 785 (4th Cir. 2023) is the case a buyer should read first, because its defendant was a buyer. Frank Zhang, CEO of a Chinese financial information company, bought pru.com through Sedo in October 2017, from an unidentified Texas company, for what he said was $100,000. Prudential had registered PRU in 2002. In March 2020, an anonymous offer reached the holder through a GoDaddy broker. It came from Prudential's investigator. The holder turned down a five-figure bid and mentioned a six-figure offer. A week later Prudential filed a UDRP complaint, learned the registrant's identity from the provider, offered $50,000, was refused, and sued in the Eastern District of Virginia, where the .com registry sits, then ended the WIPO case. The court dismissed Zhang for lack of personal jurisdiction, and the suit went forward in rem against the name.
The Fourth Circuit joined the Third and Eleventh, holding that "registers" and its derivatives "extend to each registration of a domain name, including the initial registration and any subsequent re-registrations." Its answer to the Ninth Circuit's alienability point was that the bad faith element does that work. A person renewing because the system requires it does not act with bad faith intent to profit. The Act "does not take away the initial registrant's right to sell or transfer all of her rights in a domain name to any other party." It simply prohibits registering in bad faith, "[t]hus, where there is no bad faith, there is no liability for cybersquatting." The court then affirmed summary judgment and the transfer.
The district courts fill in the map
Courts outside these circuits are free to choose, and the trend favors the majority's text-first reading. Workforce Software, LLC v. Workforce.com, Inc., No. 1:20-cv-07365 (N.D. Ill. Oct. 26, 2021) is the best example, because its facts are a pure aftermarket story. The name workforce.com was registered in 1994; the plaintiff started in 1999; the defendants acquired the name and, as alleged, changed its use from a magazine to a direct competitor. The Seventh Circuit had not spoken. The court sided with the Third and Eleventh, denied the motion to dismiss, and gave buyers a line worth keeping: "For new registrants who continue to use a domain as it has always been used, there can be no serious allegation of bad faith."
Inside the Ninth Circuit, GoPets has real teeth. In AIRFX.com v. AirFX LLC, 2012 WL 3638721 (D. Ariz. 2012), as described in the Dent opinion below, a buyer who purchased from an unrelated third party and parked the name won summary judgment on the owner's cybersquatting counterclaim. In Dent v. Lotto Sport Italia S.p.A., No. 2:17-cv-00651 (D. Ariz. Mar. 11, 2020), David Dent bought lottostore.com and lottoworks.com in 2016 for a lottery business. The names dated from 2011 and 1998. A WIPO panelist ordered transfer to an Italian sportswear company. Dent sued, and the court held that the purchases were not registrations under GoPets and that his registration and use were lawful, and ordered the names unlocked. A later order awarded him $236,752.50 in fees. JFXD TRX ACQ LLC v. trx.com, No. 2:23-cv-02330 (D. Ariz. May 8, 2024) ended with a $41,098.77 fee award against a plaintiff that pressed a claim over trx.com, first registered in 1999, against a buyer who had paid $138,000. GoPets controlled, and the court found the case exceptional in part because the plaintiff never offered a plausible way around it. The Ninth Circuit affirmed both the dismissal and the fee award in an unpublished memorandum, JFXD TRX ACQ LLC v. trx.com, No. 24-1661 (9th Cir. Apr. 4, 2025), holding that the plaintiff had to plead rights in TRX before the name's initial registration.
GoPets is not a charm, though. Mira Holdings Inc. v. UHS of Delaware Inc., No. 2:23-cv-00169 (D. Ariz. Aug. 18, 2023) applied it, rejecting the argument that it covers only "registers" and leaving "traffics in or uses" open, but the buyer there had failed to plead the name's original 2014 registration date, and the court dismissed its misrepresentation claim under § 1114(2)(D)(iv) while allowing an amended pleading. The opinion also says that bona fide purchaser status "is not the relevant legal test." And DSPT International, Inc. v. Nahum, 624 F.3d 1213 (9th Cir. 2010) holds, in a case where the marks were already in play when the name was registered, that "use alone is enough" and that a later bad faith use can support liability even with an innocent registration.
The Eastern District of Virginia is now where many of these cases land. A recent report and recommendation in LimeWR Fyre OU v. fyrefestival.com, No. 1:25-cv-1629 (E.D. Va. Mar. 11, 2026) shows the pattern in a default setting: the complaint alleged that the name was "most recently re-registered" in July 2025, and the magistrate judge recommended default judgment and transfer. A report on default is modest authority, but it shows how plaintiffs now plead.
Where that leaves a buyer
| Your situation at purchase | UDRP | ACPA in 3d, 4th, 11th Cir. | ACPA in 9th Cir. | Elsewhere |
|---|---|---|---|---|
| Mark exists; you buy with intent to exploit it | Exposed | Exposed | Protected only if the initial registration predates the mark | Open, likely exposed |
| Mark exists; you buy for an unrelated real business | Good defense, on proof | Good defense on bad faith, on proof | Strong; no registration violation if initial registration predates the mark | Good defense |
| Mark did not exist at your purchase | Generally safe, subject to the anticipation cases in section 3.8.2 | Safe on this claim | Safe | Safe |
| You bought a dropped name | Your date controls | Your date controls | Your date likely controls; see JFXD | Your date controls |
Forum is not purely in your hands. A mark owner can usually choose among your home court, the registrar's district, and, for an in rem case against a holder not reachable in the United States, the registry's district. A .com buyer abroad should assume the Fourth Circuit. The reverse also happens: JFXD was filed in Virginia, transferred to Arizona for want of personal jurisdiction, and decided under Ninth Circuit law, because a transferee court applies its own circuit's precedent on federal questions. Prudential's in rem theory worked precisely because SSN could not be reached anywhere in the United States when the case was filed. For more on the forum question, see Domain Name Dispute Forum Selection Checklist: A Practical Checklist, and on why a federal court has these cases at all, Federal Subject-Matter Jurisdiction: Arising Under, Diversity, Supplemental Claims, and the Defect That Never Waives.
As of this document's date, the Supreme Court has not taken up the split. It denied certiorari on 15 December 2025 in JFXD (No. 25-188), a petition that asked it to resolve exactly this question, and we found no later circuit decision that changes the count.
Prudential as an autopsy of a bad purchase
The most useful pages of Prudential are the factor-by-factor bad faith analysis under § 1125(d)(1)(B)(i), because each factor reads like a mistake a buyer can avoid.
No plan anyone could see. SSN never put content on pru.com. Its documents included a mock-up reachable only from an address created after the UDRP filing, thumbnail sketches, and a contract that nobody authenticated. Quoting Harrods Ltd. v. Sixty Internet Domain Names, 302 F.3d 214 (4th Cir. 2002), the court repeated that Congress did not list proposed future use as a factor, "presumably because it would be too easy for cybersquatters to claim an intent to use a disputed name to provide goods or services in the future."
A story that did not fit the name. SSN said PRU abbreviated a Chinese phrase for a Prussian news agency, which it said suited a foreign exchange news product. The court was unimpressed. Its explanation amounted to wanting an easy three-letter name, and the court noted that any three letters would serve.
The parked page. Visitors in the United States saw pay-per-click links with Prudential's marks and competitors' marks, plus an offer to buy the domain. SSN argued GoDaddy chose the links. The court held that an experienced customer knew parking was the default, knew it showed ads, and could have turned it off. The Ninth Circuit made a similar point in Lahoti v. Vericheck, Inc., 636 F.3d 501 (9th Cir. 2011), where the holder protested that he "had no ability to control the search results." The court said that was "of little import."
Concealment and shifting records. SSN used a privacy service until the UDRP filing, listed a related company as registrant organization, and then changed the registrant name twice after it had notice. Privacy alone was not the problem. The court read the concealment plus the later changes as suggesting an intent to conceal SSN's true identity. Compare UDRP paragraph 8, which bars transfers during a pending proceeding, and the Rules' definition of "Lock."
The portfolio. SSN held more than 100 names, including ones matching Yelp, Quora, and Chrome. Factor VIII speaks of "registration or acquisition" of multiple names that the person knows match the marks of others. A serious buyer who also holds a drawer of brand-like names will have to explain it.
Offers, and a correction that helps sellers. The district court had said factor VI, on offers to sell, clearly favored Prudential. The Fourth Circuit said that was error, though inconsequential. Citing Virtual Works, Inc. v. Volkswagen of America, Inc., 238 F.3d 264 (4th Cir. 2001), it repeated that "a mere offer to sell a domain name is not itself evidence of unlawful trafficking," and found a genuine dispute about whether SSN had actually offered anything or had only rejected offers. Virtual Works itself is the contrast case: the holder there told Volkswagen it had 24 hours to buy vw.net before the name went to the highest bidder, and the court said this was "much more than a plain vanilla offer." It also held that a defendant who acts "even partially in bad faith" cannot use the safe harbor for those who reasonably believed their use was lawful, § 1125(d)(1)(B)(ii).
Contrast Southern Grouts & Mortars, Inc. v. 3M Co., 575 F.3d 1235 (11th Cir. 2009). 3M kept renewing diamondbrite.com after its own mark lapsed and displayed nothing there, explaining that it wanted to keep a competitor of another product line from using the name to sow confusion. The Eleventh Circuit held that passive defensive holding without a profit motive was not a bad faith intent to profit. The statute is about profiting from a mark, and holding is not enough.
Ordinary trademark law does not care when you bought
Everything above concerns cybersquatting. A buyer can win that fight and still lose under infringement or unfair competition law, 15 U.S.C. § 1114(1) and § 1125(a), if its actual use of the name is likely to confuse. A domain's age gives no priority for the mark you will use, because priority comes from use in commerce or a filing basis, 15 U.S.C. § 1051 and 15 U.S.C. § 1127. The separation shows up in the Arizona lambo.com case discussed below, which read the reverse hijacking provision to resolve only lawfulness under the ACPA, so the registrant needed a separate declaratory claim to reach the rest of the Lanham Act.
So clearance belongs before the offer, not after closing. A buyer should run a search for the second-level term in its field and adjacent ones, at the USPTO and the states and online, using MC Law's How to Conduct a Comprehensive Trademark Clearance Search or a tool such as marksy.us as a start, and then treat the results as a decision input. If clearance shows the name is effectively someone else's, the right response may be to walk away, however good the price. The role of a documented search in rebutting willfulness is covered in The Shield of Good Faith: How Trademark Clearance Searches, Attorney Opinions, and USPTO Approval Protect Against Willful Infringement Claims.
There is a chance to buy something more than the name. If the seller actually used the name as a brand, it may have common-law rights, and the buyer may want them for priority. The trap is the assignment in gross, a transfer of a mark without the goodwill it represents. 15 U.S.C. § 1060 requires the good will of the business, and Sugar Busters LLC v. Brennan, 177 F.3d 258 (5th Cir. 1999) voided an assignment of a registered mark on that basis and vacated an injunction that rested on it. If the mark matters, buy it properly with its goodwill and record it, as described in Recording a Trademark Assignment: A Practical Checklist. If you plan to use the name as a mark and file an application, remember that the declaration you sign carries its own risks, discussed in Fraud on the USPTO: How a False Declaration Can Cost You a Trademark Registration. Two more wrinkles: a term ending in .com is not automatically generic, since USPTO v. Booking.com B.V., 591 U.S. 549 (2020) held that the question depends on how consumers perceive the term as a whole, so a descriptive name may still become a protectable brand with proof; and a seller that keeps a similar business after the sale can create exactly the confusion you paid to avoid, so the agreement should deal with that.
Stolen names and the limits of good faith
The most sobering case on title is CRS Recovery, Inc. v. Laxton, 600 F.3d 1138 (9th Cir. 2010). Dale Mayberry registered rl.com in 1995. He controlled it through an email address at mat.net, another name he owned. In 2003, a man named Li Qiang acquired mat.net in circumstances the record left unclear, took over the email address, and used it to move rl.com to himself. Qiang passed it to Barnali Kalita, who in 2005 sold it to John Laxton, a Californian, for $15,000. Before buying, Laxton says, he checked with WIPO to make sure there were no disputes. He then spent thousands of dollars successfully defending the name against Ralph Lauren at WIPO. Then Mayberry's assignee sued him for conversion.
The panel held California law applied and described the human predicament: "We are faced with two parties, neither of which apparently knew anything they did was wrong until it was too late, and a third-party wrongdoer from whom it is unlikely anyone can ever collect judgment." It then applied the old distinction between a thief and a swindler, drawn from commercial-code logic. An involuntary transfer leaves void title, and no later buyer takes anything. A voluntary transfer induced by fraud leaves voidable title, and an innocent purchaser for value without notice takes free. Whether Mayberry was robbed or duped, or abandoned the name, was disputed, so the court affirmed the choice of California law, reversed summary judgment against Laxton, and remanded.
For buyers, four lessons follow. First, ordinary diligence does not cure void title. Second, the choice of law can matter, and the Ninth Circuit was unimpressed by a California buyer invoking Virginia law for his own protection, warning against "a race to the bottom." Third, you might have to litigate a question whose facts sit in someone else's past. Fourth, a reversal risk exists at the registrar level too. The Transfer Policy provides for reversal of a transfer through the Transfer Dispute Resolution Policy and registrar cooperation, and that can reach a name after a chain of sales. Kremen v. Cohen, 337 F.3d 1024 (9th Cir. 2003) shows where the loss can settle otherwise: there, a registrar faced conversion liability for acting on an obviously forged letter. See Stolen Domain Names: How Domain Hijacking Happens and the Legal Paths to Getting One Back and Recovering a Hijacked Domain Name: A Practical Guide for the victim's perspective, which is the same fact pattern seen from the other side.
Here is how the warning signs look in practice. Suppose a fund's analyst finds brennickvault.com offered at $9,000, a fifth of what comparable names fetch. RDAP shows the updated date as three weeks old, the registrar recently changed, and the seller writes from a free webmail account, wants a wire to a foreign account, and refuses escrow "for tax reasons." Archived pages show an operating business at that address until last month. Nothing here proves theft. All of it should stop the deal until the seller proves authority, including a signed statement of how it acquired the name and a look at archived records of prior holders. If the old business answers an email and says "that was our domain," you have saved a good deal more than $9,000.
The baggage that comes with a used name
A secondhand domain has a past, and the internet remembers it in ways people forget to check.
Email keeps coming. Mail servers and people still send to old addresses at that name: customers, banks, password resets, perhaps medical or legal messages. A buyer who sets up a catch-all mailbox will receive it. The buyer's position is unusual and little litigated: mail is reaching the domain's lawful holder, but it was not meant for the buyer. Reading it, or using a password reset meant for the old owner's account, invites trouble under the Wiretap Act, 18 U.S.C. § 2511, the Stored Communications Act, 18 U.S.C. § 2701, and the Computer Fraud and Abuse Act, 18 U.S.C. § 1030, the last especially if you use a reset to enter someone else's account (see The Computer Fraud and Abuse Act After Van Buren: Gates, Insiders, Scrapers, and the Loss Requirement). The prudent practice is no catch-all, defined mailboxes only, and rejection or quiet discard of anything else unless the contract sets up a forwarding arrangement. Sellers have the mirror-image concern: their old accounts at third-party services may still recover through the old address, so a seller who does not clean up is handing a stranger the keys. This is one reason a seller should change those recovery addresses before closing, and why the agreement should say so.
Certificates can outlive ownership. A seller who obtained a TLS certificate for the name before closing may hold a valid private key for some time afterward. Certificate lifetimes have been shrinking under a CA/Browser Forum schedule, but a certificate issued shortly before closing can remain valid for months. Public certificate transparency logs show what has been issued. Check them and ask the issuing authority to revoke anything you did not obtain.
The name may be blacklisted. Spam and malware blocklists, browser safe-browsing lists, and search-engine penalties may follow a name. Archived pages and historical DNS and WHOIS services show what it was used for. A name with a history of malware or adult content may send your first marketing mail to the junk folder. Those checks cost little and belong in diligence, and a poor result can justify a lower price.
Other domains may depend on it. If the name served as a name server host, or a third party's records still point at it, you may inherit dangling dependencies or find other parties' systems still trusting it. Single sign-on tenants at cloud providers and software-as-a-service verification records are common leftovers. Ask, and search.
Buy, fight, or walk
Mark owners often arrive at the purchase question believing they have a claim. The decision turns on four dates and a realistic reading of the seller's conduct: when the name was first registered, when the current holder acquired it, when your mark became distinctive, and when your rights arose relative to all of those.
Fight if the holder targeted you. A holder who acquired the name after your mark was well known and uses it for competitor ads or offers it to your competitors is a UDRP respondent worth filing against. Filing fees at WIPO are $1,500 for one to five names before a single panelist and $4,000 before three as of this writing, plus counsel. Cases usually end in about two months. For how to run one, see How to File a UDRP Complaint for Domain Name Disputes and Choosing the Right Domain Name Dispute Procedure: A Practical Guide. An ACPA suit adds damages and costs far more; Prudential took years.
Buy if you came second. If the holder took the name before your rights existed and has done nothing to target you, you have no UDRP claim. GoPets' arbitrator said so in 2006, and Overview 3.1 section 3.8.1 says so now. You are a buyer. Accept it and negotiate.
Walk if the price exceeds the name's value to the business. A brand can launch on a modified name, a different extension, or a new coinage. Founders overestimate how much the exact .com matters and underestimate what an expensive purchase crowds out. The discipline is to set a walk-away number before contact.
How offers come back to bite
Purchase talks do not sit in a privileged envelope. Overview 3.1 section 3.10 says panels "tend to view settlement discussions between the parties as 'admissible,' particularly insofar as such discussions may be relevant to assessing the parties' respective motivations," and adds that negotiations "can serve a legitimate useful purpose, and are not necessarily indicative of bad faith." In court, Fed. R. Evid. 408 bars compromise evidence only as to a disputed claim, and an anonymous pre-dispute inquiry about price has no dispute to compromise. The Prudential court relied on broker emails produced from the anonymous approach. GoPets recounts every offer. Lahoti recounts a $72,500 asking price, reduced to $48,000, in Lahoti v. VeriCheck, Inc., 586 F.3d 1190 (9th Cir. 2009), which affirmed a bad faith finding against a holder with no interest in the term and a record of similar conduct, while vacating on distinctiveness.
The lessons run in each direction.
A buyer's offer can undercut its later claim. Asking "what would it take?" concedes nothing formally, but a long history of offers, followed by a complaint the moment the price disappoints, is a recognizable pattern. Overview 3.1 section 4.16 lists "filing the complaint after an unsuccessful attempt to acquire the disputed domain name from the respondent without a plausible legal basis" as a reason for a finding of reverse domain name hijacking. Practitioners call this a "Plan B" filing. The finding carries no damages at WIPO, but it is public and embarrassing, and section 4.16 warns that some courts may impose monetary consequences where the equivalent is found. It also holds represented complainants to a higher standard in some panels' view. See Advanced Domain Dispute Toolkit: URS Complaints, In Rem Pleadings, and Reverse Hijacking Defenses for defensive work on these claims.
A seller's reply can prove bad faith or dispel it. A demand that exceeds out-of-pocket costs is evidence under paragraph 4(b)(i) only if the seller registered or acquired the name primarily to sell it to the mark owner or its competitor. Section 3.1.1 says that where the registrant has an independent right or legitimate interest, an offer to sell is not by itself evidence of bad faith, whichever side solicited the sale, and that this includes generalized offers on a third-party platform. Offers above cost must target a trademark owner to matter under paragraph 4(b)(i).
An anonymous approach is a double-edged tool. It finds the true market price, and a mark owner's investigator may elicit useful statements. But the conversation may just as easily show a seller who did not know the buyer's identity and so cannot have been targeting it. Prudential's investigator produced a refusal and a dispute of fact, which is why the Fourth Circuit discounted factor VI.
A second worked example
Suppose Marlowe Tessaly runs Tessaly Bakes, a Savannah bakery with a state registration from 2019. She wants tessaly.com. A travel blogger registered it in 2011 to write about a region of Greece, and has held it since. It now shows a "for sale" lander with a $25,000 price.
Her lawyer tells her she has no UDRP case. The blogger registered eight years before her mark, there is no sign of targeting, and a dictionary-adjacent place name has obvious other uses. A filing would risk a hijacking finding, particularly after her two rejected offers. An ACPA claim has the same gap under GoPets in the Ninth Circuit and on the bad faith element everywhere. So Tessaly has three real choices: pay something near the price; keep tessalybakes.com, which she already owns, and spend the money on the business; or ask for a lease-to-own arrangement, reading the default terms closely, since the seller keeps the registration until the final payment.
Now assume she buys it and later faces a dispute. Her purchase date is 2026. A third party holding an older mark in TESSALY for bakery goods could test her 2026 intent, and the blogger's innocence would not help her, so she should run clearance first. A buyer is always asking two questions at once: is the seller's position clean, and will mine be?
If you buy and lose a UDRP: the ten-day window
A buyer's right to go to court matters most at the worst moment. Paragraph 4(k) tells the registrar to wait ten business days after a transfer decision and to hold implementation if it receives a file-stamped complaint against the complainant in the agreed "Mutual Jurisdiction" (generally the registrar's location or the holder's). Miss the window and the name moves.
The vehicle is 15 U.S.C. § 1114(2)(D), whose clause (v) lets a "domain name registrant" whose name was suspended, disabled, or transferred under a policy sue to establish that its registration or use "is not unlawful." Sallen v. Corinthians Licenciamentos LTDA, 273 F.3d 14 (1st Cir. 2001) recognized that as an affirmative cause of action for a declaration and for return of the name. Storey v. Cello Holdings, L.L.C., 347 F.3d 370 (2d Cir. 2003) added that the action is not review of the panel decision at all. Barcelona.com, Inc. v. Excelentisimo Ayuntamiento de Barcelona, 330 F.3d 617 (4th Cir. 2003) held that the question is one of U.S. law and reversed a judgment that had rested on Spanish trademark law. The Dent court decided the merits on its own summary judgment record under U.S. law and reached the opposite result from the WIPO panelist. Hawes v. Network Solutions, Inc., 337 F.3d 377 (4th Cir. 2003) allowed a registrant to pursue that action after a registrar deposited control of the name with a French court.
Is a buyer a "registrant" for this purpose? Blair v. Automobili Lamborghini S.p.A., No. 2:22-cv-01439 (D. Ariz. July 14, 2023) answered yes. Lamborghini, relying on GoPets, argued that only the initial registrant can use clause (v). The court rejected the argument, reasoning that the alienability rationale of GoPets itself cut the other way. Blair had purchased lambo.com in 2018; a three-member panel had split 2 to 1 for transfer; and his suit, filed before the decision took effect, held the transfer. The current registrant may sue. Clause (iv) is a separate, narrower route, requiring a knowing and material misrepresentation, and Mira shows it fails on thin allegations. For procedure on the declaratory side, see Filing or Defending a Declaratory Judgment Action: A Practical Guide, and add a declaratory count under 28 U.S.C. § 2201 if you want rulings beyond the ACPA.
Taxes, briefly
The IRS's most direct statement is Chief Counsel Advice 201543014 (released 23 October 2015). It concludes that the cost of buying a name on the secondary market for use in a trade or business must be capitalized, not deducted, whether the name is generic or not. A non-generic name that is registered as or functions as a trademark is a § 197 intangible, amortized ratably over 15 years under 26 U.S.C. § 197. So is a non-generic name that does not qualify as a trademark but will serve an already built website the buyer will maintain, and a generic name that fits that same website pattern and is bought to earn advertising revenue or increase market share. Advice of this kind may not be used or cited as precedent, 26 U.S.C. § 6110(k)(3). It does not settle the treatment of a name that sits idle, or a name bought for resale, where 26 U.S.C. § 167 and inventory or capital-gain questions arise. Ask a tax adviser before you close, because the allocation, the form of the seller's paperwork, and any foreign-seller withholding question are easiest to address beforehand.
Anonymous buying and honesty
Buying through an agent or a new entity is old practice and lawful. An agent who contracts for an undisclosed principal makes a binding contract that the principal may generally enforce (Restatement (Third) of Agency § 6.03), subject to the terms. ABA Model Rule 4.1 comment 2 says that under generally accepted negotiation conventions, the existence of an undisclosed principal is ordinarily not a statement of material fact, except where nondisclosure would constitute fraud. FinCEN's August 2026 final rule, effective 14 August 2026, confirms that entities formed in the United States are not reporting companies under the Corporate Transparency Act, so a domestic stealth LLC does not itself trigger federal beneficial ownership filing, though state rules and bank onboarding may ask.
Silence and lying are different things. "My client prefers not to be named" is fine. "This is for a small nonprofit" when it is for a public company is a misrepresentation that can support rescission or a fraud claim if material and relied upon. A seller who asks "are you acting for X?" should get a refusal to answer or the truth. Lawyers have a separate duty under their state's version of Rule 4.1 and Rule 8.4(c). The mechanics, including how to pick an entity without creating a false contact record under factor VII, are in the companion guide, Acquiring a Domain Name Anonymously and Safely: A Practical Guide.
Country-code names are different
Everything above about the UDRP and Transfer Policy applies to gTLDs and to those country-code registries that have adopted them. Many country codes have their own policies, registries, local-presence requirements, and transfer procedures, and a name under .io or .ai or .de may follow different rules. Check the registry's published rules before you make an offer, since a buyer who cannot meet a nexus requirement may not be able to hold the name at all. The MC Law overview of Beyond the UDRP: Uniform Rapid Suspension, Country-Code Domain Disputes, In Rem ACPA Actions, and Reverse Domain Name Hijacking covers country-code dispute procedures.
What remains unsettled
The circuit split itself. Three circuits against one, with most circuits silent. A buyer outside those circuits is working with district court opinions.
How far GoPets reaches. Its facts involved an affiliate transfer. District courts have extended it to arm's-length sales, and an unpublished 2025 Ninth Circuit memorandum in JFXD applied it to one without discussion, but no published Ninth Circuit opinion has revisited it in a purchase by a stranger. How it interacts with DSPT's "use alone" reasoning when the mark postdates the first registration is also not fully resolved, though Mira treated the distinctiveness language as controlling.
Lapsed names. The JFXD order suggests a lapse and re-registration could be a new initial registration even in the Ninth Circuit. No published circuit decision settles that.
What "Act" or "chapter" means in clause (v). Courts have disagreed whether a clause (v) declaration resolves only the ACPA or the whole Lanham Act. Blair and Dent take the narrower view, relying on Ricks v. BMEzine.com, LLC, 727 F. Supp. 2d 936 (D. Nev. 2010).
The theft-versus-fraud line for digital assets. CRS Recovery imported a distinction made for goods. Account takeovers using stolen credentials resemble theft, but they often look like fraud on the registrar. Few courts have sorted the cases, and state law may differ.
The new Transfer Policy. Implementation details, including how registrars handle early removal of the 30-day restriction and how disputes over TAC issuance play out, remain to be written.
This article is general information and not legal advice for a specific situation. If you are about to wire money for a name, or about to file a complaint over one you could not buy, it is worth an hour with someone who has seen how these end.
Related Documents
Related Articles
- Domain Name Disputes: Cybersquatting, the ACPA, and the UDRP: the broader body of cybersquatting law and how a complaint is won.
- Beyond the UDRP: Uniform Rapid Suspension, Country-Code Domain Disputes, In Rem ACPA Actions, and Reverse Domain Name Hijacking: URS, country-code disputes, in rem actions, and hijacking findings beyond the standard UDRP path.
- Stolen Domain Names: How Domain Hijacking Happens and the Legal Paths to Getting One Back: the theft scenario from the victim's side, including recovery paths after a chain of sales.
- Top-Level Domain Names: An Overview: how the namespace is structured and who runs which registry.
- How to Conduct a Comprehensive Trademark Clearance Search: the search to run before any offer.
- The Shield of Good Faith: How Trademark Clearance Searches, Attorney Opinions, and USPTO Approval Protect Against Willful Infringement Claims: how a documented clearance effort protects against willfulness claims.
- Escrows, Holdbacks, and Purchase Price Security: Who Holds the Money and Who Gets It Back: general deal-escrow concepts useful in larger domain purchases.
- Rebranding Without Regret: Clearance, Transition, and Protecting the Old Mark While Launching the New One: what to do when the new name means retiring an old brand.
- Fraud on the USPTO: How a False Declaration Can Cost You a Trademark Registration: the declaration risk if you file a trademark application for your new name.
- The Computer Fraud and Abuse Act After Van Buren: Gates, Insiders, Scrapers, and the Loss Requirement: why you should not use a password reset that arrives at your new domain.
- Federal Subject-Matter Jurisdiction: Arising Under, Diversity, Supplemental Claims, and the Defect That Never Waives: why these cases are in federal court and how jurisdiction is established.
Related Guides
- Acquiring a Domain Name Anonymously and Safely: A Practical Guide: the sibling step-by-step guide to buying a name without announcing who you are.
- Choosing the Right Domain Name Dispute Procedure: A Practical Guide: choosing among UDRP, URS, and federal court if the purchase route fails.
- Recovering a Hijacked Domain Name: A Practical Guide: what to do if the name you bought, or your own, is taken.
- Filing or Defending a Declaratory Judgment Action: A Practical Guide: the procedure behind the declaratory count that often accompanies a clause (v) suit.
Related Checklists
- Domain Name Acquisition Checklist: A Practical Checklist: the sibling desk checklist for buy-side phases, from clearance through post-closing.
- Domain Name Dispute Forum Selection Checklist: A Practical Checklist: sorting out where a name dispute can and should be heard.
- Domain Name Security and Recovery Checklist: A Practical Checklist: hardening the name after closing.
Related Toolkits
- Domain Acquisition Toolkit: Outreach Scripts, Purchase Agreements, and Post-Closing Records: the sibling working papers, including outreach scripts, a purchase agreement, escrow instructions, and a closing run sheet.
- Domain Name Toolkit: UDRP Complaints, ACPA Pleadings, and Portfolio Management: UDRP and ACPA papers if a dispute follows.
- Advanced Domain Dispute Toolkit: URS Complaints, In Rem Pleadings, and Reverse Hijacking Defenses: defending against or pursuing reverse hijacking findings.
