Skip to content

docs: False Positive Abuse Reports - #33073

Draft
shanecloudflare wants to merge 1 commit into
cloudflare:productionfrom
shanecloudflare:remedy/12-100-false-positive-abuse-reports
Draft

docs: False Positive Abuse Reports#33073
shanecloudflare wants to merge 1 commit into
cloudflare:productionfrom
shanecloudflare:remedy/12-100-false-positive-abuse-reports

Conversation

@shanecloudflare

Copy link
Copy Markdown

Auto-Generated Documentation Update

Suggested Change

Add a section on handling false positive abuse reports, including steps to take when a legitimate website is flagged as phishing. This could include information on how to submit a false positive report, how to create a WAF custom rule to allow traffic, and best practices for narrowing the scope of skip rules to prevent potential abuse.


## Handling False Positive Abuse Reports

If your legitimate website is flagged as phishing, it can cause issues with user access and trust. To handle false positive abuse reports, follow these steps:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is in the bots section, but talks about phishing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:bots Related to Bots product size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants