Skip to content

Latest commit

Β 

History

History
58 lines (29 loc) Β· 4.18 KB

README.md

File metadata and controls

58 lines (29 loc) Β· 4.18 KB

PhishFort Logo

🚨 Important Notice: Migration to the Public Blocklist API 🚨

PhishFort has always been committed to supporting the abuse-fighting community by providing access to up-to-date threat intelligence. As part of our ongoing efforts to enhance security and privacy, we are retiring the public blocklist on GitHub and transitioning to the Public Blocklist API at lookup.phishfort.com.

πŸ”Ή What’s Changing?

  • The GitHub-hosted list will begin to be deprecated and disabled from May 1, 2025.
  • We are moving to a protected system to better safeguard the privacy of our users, partners, and the broader security community.
  • The Public Blocklist API ensures continued access to our intelligence while maintaining an additional layer of privacy and security.

πŸ”Ή Our Commitment Remains

PhishFort will continue working closely with the abuse-fighting community and our trusted partners to combat phishing and online threats. This transition allows us to provide more effective protection while ensuring responsible data sharing.

πŸ”Ή Action Required

If you rely on this GitHub-hosted list, please migrate to the API before May 1, 2025, to avoid disruptions.

For more details, visit our documentation at https://lookup.phishfort.com/ or contact us at partner-sharing-requests@phishfort.com.

Thank you for your continued support in keeping the internet safer! πŸš€


PhishFort Counter-Phishing Lists

Now protecting over 418 million monthly active users across the globe!

This repository contains a blacklist and whitelist of domains maintained by PhishFort. These lists are used by the PhishFort Protect browser plugin (Chrome, Firefox), as well a number of third-party browser plugins and services to protect their users from crypto phishing attacks and scams.

If you would like to make use of this list commercially or at scale contact us about using our PhishFort List Lookup API. We cannot guarantee the integrity of lists downloaded via a 3rd party content delivery network, as a result we advise to use our lookup API instead.

πŸ”΄ Blacklists

The blacklists directory contains two lists in JSON format:

Teams are invited to openly pull from our full blacklist to ensure maximum coverage. However, in the case where performance or the size of the list is a concern (this list is always growing) we urge developers and/or teams to then consider consuming from our hot list.

The hot list keeps a rolling window of 3 month detections (ie. items in the hotlist will only exist for 3 months). The rolling window period is subject to change. Although this should be ample time for PhishFort to execute a successful takedown on the site mentioned, we cannot guarantee that we will be executing takedowns on every single item in the list.

🟒 Whitelists

The whitelist directory contains a number of lists we maintain for partner projects and internal reasons. We do not recommend consuming or making any assumptions based on this list.

🌐 Use of CDN

Although we recommend loading directly from GitHub to maintain a perfect sync with the most up-to-date version of the PhishFort lists, significant performance improvements can be seen with using a CDN. For example by accessing the blacklist via jsdelivr CDN here.

We cannot guarantee the integrity of lists downloaded via a 3rd party content delivery network. We recommend using the PhishFort Public Blocklist API instead of CDNs.