Reporting and warning-review routes
Dated 24 October 2026. This table describes checked sources; it does not scan a URL or tell you whether a site is safe. Unknown fields are preserved.
20 of 20 rows
| Organization | Category | Purpose | Route | Required information | Limit |
|---|---|---|---|---|---|
| Google Search Console | browser warning review | Owner requests review of security issues after correction. | Search Console Security Issues review | Issue, correction and outcome explanation. | Does not establish a verdict from every browser or remove unrelated content. |
| Microsoft Defender SmartScreen | browser warning review | Owner challenges an incorrect SmartScreen site warning. | Warning feedback and review email | Reported site and explanation through the documented warning-feedback route. | A file submission portal is not substituted for a URL review. |
| Mozilla Firefox | browser warning review | Owner requests removal of an erroneous phishing-list entry. | Official help links to Google removal form | Site and explanation requested by the linked provider form; fields not audited. | Not a separate independent blocklist or a universal warning appeal. |
| Gmail | email provider | Recipient reports phishing or corrects a mistaken phishing label. | Message menu | Existing message; choose the applicable reporting action. | Does not review a website for every browser or block every future sender. |
| Outlook | email provider | Recipient reports a phishing message. | Message reporting control | Selected suspicious message. | Reporting does not itself block the sender; blocking is separate. |
| Yahoo Mail | email provider | Recipient flags suspicious mail or Yahoo/AOL-origin abuse. | Spam/report controls and abuse guidance | Selected message and the relevant report control. | Filter feedback is not a browser-warning appeal or guaranteed takedown. |
| Apple | email provider | Report email impersonating Apple. | Forward email to official reporting address | Suspicious Apple-impersonation email. | iCloud junk/abuse has separate handling; this is not a Safari URL appeal. |
| Namecheap | registrar | Report phishing associated with a registered domain or hosted content. | Separate registrar and hosting abuse addresses | Domain, full URL, impersonated target and existing relevant evidence. | Registrar and hosting responsibility differ; one address does not establish both roles. |
| GoDaddy | registrar | Report phishing involving a GoDaddy-associated domain or service. | Phishing abuse form | Contact email, impersonated brand, URL/domain and explanation; context fields also appear. | An intake/status interface does not promise action or browser-list removal. |
| Tucows Domains | registrar | Report phishing/pharming involving the registrar family. | DNS-abuse form linked from guidance | Relevant domain and evidence; downstream form requirements not inspected. | Family coverage includes Ascio, Enom, EPAG and OpenSRS; unrelated hosts remain separate. |
| Porkbun | registrar | Report verifiable DNS abuse. | Abuse intake and report-status route | Definitive, verifiable evidence; retain report ID. | Not a general content, trademark or ownership-dispute arbiter. |
| Amazon Web Services | hosting platform | Report abuse involving AWS resources. | Public form or Trust & Safety email | Specific URL and policy concern for content; technical incident reports require relevant logs and timestamps. | No guaranteed outcome or universal abuse-report API. |
| Cloudflare | hosting platform | Report phishing involving a Cloudflare service. | Public form; entitled dashboard/API routes | Domain and specific phishing URL; use appropriate complaint category. | A CDN/proxy role does not prove Cloudflare hosts the origin content. |
| GitHub | hosting platform | Report abusive repositories, profiles or eligible content. | Repository/user reporting and contact form | Repository/user/content reference and explanation. | Not a general website-warning appeal or a vulnerability-disclosure substitute. |
| WordPress.com | hosting platform | Report abusive content hosted by Automattic services. | Logged-in report control or direct form | Relevant hosted site/content and complaint details. | Does not cover every website running independently hosted WordPress software. |
| DigitalOcean | hosting platform | Report suspected abuse involving DigitalOcean infrastructure. | Security Operations Center abuse form | Select abuse category; remaining required fields were not fully exposed. | Read-only intake discovery does not confirm account requirements, handling time or resolution. |
| Anti-Phishing Working Group | anti phishing | Contribute suspected phishing email to shared threat intelligence. | Email forwarding and linked reporting form | Full phishing email, preferably forwarded as an attachment. | A contribution is not a guaranteed personal response, refund or website takedown. |
| Netcraft | anti phishing | Report suspicious URLs or phishing messages for investigation. | Public reporting entrypoint or forwarded email | URL and existing context; suspicious email can be forwarded. | Provider investigation is not a guaranteed takedown or removal from all browser lists. |
| PhishTank | anti phishing | Submit suspected phishing for community verification and sharing. | Registered website/email reporting routes | Suspected phishing URL and supporting message information. | Community classification does not control every warning system or guarantee removal. |
| UK National Cyber Security Centre | anti phishing | Report a suspicious scam website. | Public report form | URL, how it was received and optional explanatory context. | Not an emergency service or a guarantee of removal; no suspicious link needs opening. |
No rows match. Clear a filter or use Reset.
All rows are present in the HTML. Filtering uses this table only. Provider links open official guidance; no report is submitted here.
JSON · Method · Source ledger