Skip to content
Law & policySecurity

U.S. government gets default against Egypt.com domain name

A U.S. court has entered default against egypt.com, clearing the way for the government to take ownership after no one contested a civil forfeiture claim. The case shows how asset forfeiture applies to domain names and what it means for anyone who buys or holds a name with a tainted history.

The government's action is an in rem forfeiture: it sues the property, not the person. Because no claimant appeared after the required public notice, the court entered default. The domain is treated as an asset that can be seized if it was bought with criminal proceeds.

For domain holders, the important detail is that the government's allegation concerns the origin of the funds used to buy the domain, not the domain's content. That makes the seizure harder to defend against for someone who later acquires the name: the taint attaches to the asset, and a new owner may not wash it away.

The case also illustrates the limits of the secondary market. A buyer who purchases a domain from a seller with a clean record may still face risk if the domain was originally acquired with illicit funds. Due diligence on a domain's history can help, but the chain of title is not always visible or verifiable.

The default is not a ruling on the merits. The government still needs to show probable cause that the domain is forfeitable, but with no claimant, the process moves quickly. For anyone holding a domain that could be connected to criminal activity, the practical takeaway is that silence is not protective; the forfeiture process is designed to proceed without you.

What is unknown is whether a legitimate owner or buyer would have been able to contest the forfeiture successfully. The government published notice, but the alleged owner did not appear. That leaves open the question of how courts would treat a good-faith purchaser in a contested case.

The Sourcedomainnamewire.com

We hope our commentary provided you value, please don't forget to also read the source article at Domain Name Wire.

Discussion