We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am experiencing a problem where... It looks like @smed79 have spotted a bug i Phishing-Database/Phishing.Database#1208 as a record from cdpn.io
cdpn.io
phishing-links-ACTIVE.txt
ALL-phishing-links.lst
phishing-domains-ACTIVE.txt
ALL-phishing-domains.lst
This make both the "Not Present" file unreliable...
To reproduce the problem:
I expected that...
I found a workaround...
I would like to add...
Paste your log file here between the back tics.
The text was updated successfully, but these errors were encountered:
List source are equal, how are the lists distributed??
https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/ = https://raw.githubusercontent.com/Phishing-Database/Phishing.Database/refs/heads/master/ = https://phish.co.za/latest/
https://raw.githubusercontent.com/mitchellkrogza/Phishing.Database/master/
https://raw.githubusercontent.com/Phishing-Database/Phishing.Database/refs/heads/master/
https://phish.co.za/latest/
Which of the sources should we trust?? AND which one is the actual SOURCE?
Sorry, something went wrong.
mitchellkrogza
funilrys
No branches or pull requests
What is the problem you are experiencing?
I am experiencing a problem where...
It looks like @smed79 have spotted a bug i Phishing-Database/Phishing.Database#1208 as a record from
cdpn.io
phishing-links-ACTIVE.txt
ALL-phishing-links.lst
phishing-domains-ACTIVE.txt
ALL-phishing-domains.lst
This make both the "Not Present" file unreliable...
How can we reproduce the problem?
To reproduce the problem:
Do you have a screenshot?
Screenshot
What did you expect to happen?
I expected that...
Is there a workaround?
I found a workaround...
Additional context
I would like to add...
Log information
Click to expand
The text was updated successfully, but these errors were encountered: