-
-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
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
False Positive | hopp.bio #754
Comments
Hmm in Phishing-Database/Phishing.Database#786 I can see you are references to
hopp.bioFor Do to the number of urls, you would have to drag the long hall of testing these before I spent more time on this issue, and please return a detail list of your believes in the records. You shall also ensure the domain is public, so we can test and verify your feedback on these urls, this includes and not limited to the safe and secure network of Tor
|
@funilrys where is the DNS TXT message from the @phishing-database-bot in this project, from where all whitelist issues should be handled? |
@spirillen thanks for the response. We changed it so a blocked page will return a 403. Is there anything else that I should do? |
Hi @shaulgo, Thank you for your response and for making the adjustments to your systems. I appreciate it! However, I would like to suggest a change regarding the response codes. From my perspective, using a 403 status code can be quite challenging for establishing default trust, as it essentially communicates, "I don't like how you asked," or indicates that access is completely denied. This can create confusion for test results. I would kindly encourage you to consider using a 410 status code for links that are no longer available, or alternatively, a 404 status code. Personally, I find 404 less preferable, as it merely states that the request cannot be fulfilled at the moment. As a list maintainer, I have a strong preference for the 410 status code. While I respect your choice based on the project's approach, I kindly request that you consider this change for better alignment on a global scale. Thank you! |
Ralated to #754, Phishing-Database/Phishing.Database#464 Previously whitelisted in Phishing-Database/Phishing.Database#786 |
What are the subjects of the false-positive (domains, URLs, or IPs)?
https://phish.co.za/latest/phishing-links-ACTIVE.txt - (I can see that these are all already blocked. They were likely phishing accounts)
http://hopp.bio/cavenewadminset
http://hopp.bio/chasnfaay
http://hopp.bio/facture
http://hopp.bio/homeofdepartureaccount
http://hopp.bio/latakoinono
http://hopp.bio/lawhomeactsetin
http://hopp.bio/lineuniversecentreactive
http://hopp.bio/motasosanniyarobana
http://hopp.bio/security0147
http://hopp.bio/security20041
http://hopp.bio/timernowbinerft
http://hopp.bio/unvefreeniyrunberty
Why do you believe this is a false-positive?
hopp.bio
, a link-in-bio service bywix.com
. We are committed to maintaining a safe platform by actively detecting and blocking all malicious content.How did you discover this false-positive(s)?
VirusTotal
Where did you find this false-positive if not listed above?
N/A
Have you requested a review from other sources?
This is the only entity that I'm aware of that is flagging us.
Phishing-Database/Phishing.Database#786
Do you have a screenshot?
N/A
Additional Information or Context
hopp.bio
has a large community of legitimate users, and it’s disheartening to see them blocked by their ISPs due to this.The text was updated successfully, but these errors were encountered: