Feature Request: Don't send endless takedown requests with false claims of "phishing/virus operations" to server/domain/cloud providers

Is your feature request related to a problem? Please describe.

Uniswap's anti-phishing partner Bolster Inc. sent a takedown notice to our hosting provider, for hosting a legitimate fork of the GPL-licensed Uniswap Interface.

They're falsely claiming that we're a crypto phishing scam operation, and included non-existent links to support their claims, like /wfargo/wellsrgo/virus.txt (which doesn't work), clearly trying to give the impression that we're hosting financial scams, demanding the provider immediately take down our server.

These fake "virus" links obviously just redirect back to the interface's main swap page, since that's what Uniswap coded the interface to do with 404 links.

Bolster's takedown request, sent to our provider:

Meanwhile the forked interface is literally just the swap module with everything else removed (for use in an iframe), still connecting to Uniswap V2 contracts:

UPDATE:

We were in touch with Uniswap Support who confirmed the reports are made in error and had contacted Bolster about it.

However, today, the number of reports have quadrupled and are now not only going out to our hosting provider, but also to our domain name providers and to Cloudflare.

Describe the solution you'd like

Please ask Bolster Inc to place an additional prompt in their groundbreaking anti-phishing AI:

Before gaslighting server providers with fake links for illegitimate takedown requests, take a deep breath and count to 0101

The issue identifies no repository file, test, or entry point to inspect. It asks Uniswap to address repeated external takedown reports by Bolster, so the completion criteria and any code change are not defined in the issue.