Download websites that use CopyPoison

About CopyPoison

By the time a site owner installs copy protection, something has already happened to them. An article, a product description or an entire catalogue was lifted and republished elsewhere, the owner went looking for a remedy, and the conclusion was that the next incident should at least be made worthless to whoever carried it out. CopyPoison hands that conclusion out as a free script.

Our index files CopyPoison under Miscellaneous, records CopyPoison as the vendor, notes JavaScript on the client side and marks the licensing Proprietary. A protection tool that runs in the browser has an obvious ceiling, and no honest vendor pretends otherwise: anything executing on the visitor's machine can be ignored by a scraper that never executes it. What such a tool actually does is spoil the copy itself: on a copy event the script swaps letters for lookalike characters from another alphabet, so a long passage pasted elsewhere reads normally to a person and reads as gibberish to a search engine, and a link back to the source is attached by default. Calling it a lock would overstate what any client-side code can do.

The detection is therefore best read as a statement of posture. As of October 2026 we find CopyPoison on 48 sites, and a site that installs content protection is usually one where the text is the product rather than a wrapper around something else. Publishers, niche blogs, course sellers and agencies whose portfolio copy keeps reappearing under competitors' names all end up in this category, and the common thread is an owner who has decided that unauthorised reuse costs real money.

Detection carries the usual client-side caveat. A script loading on article pages but not on the homepage will be missed by a shallow crawl, and an owner can protect one section of a site and leave the rest open, so absence from the list is weak evidence of anything at all.

Two audiences find the population worth having. The first is anyone studying how the web is reacting to automated harvesting, because content protection, bot blocking, licensing walls and crawler directives are responses to the same pressure and tend to cluster on the same domains. Mapping which sites adopt which defence, and in what combination, is a question about the whole population and cannot be assembled by visiting individual pages. The second audience is commercial: vendors selling anti-piracy monitoring, takedown handling or content syndication want the set of owners who have already decided the problem is real enough to act on. Our export carries the detection alongside the rest of each site's stack, so protection scripts can be crossed against publishing platforms, paywalls and analytics to see what sort of publisher adopts what sort of defence.