Skip to content
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 | beenebrothers.com #1011

Closed
Fourthbean opened this issue Jan 10, 2025 · 3 comments
Closed

False Positive | beenebrothers.com #1011

Fourthbean opened this issue Jan 10, 2025 · 3 comments
Assignees

Comments

@Fourthbean
Copy link

What are the subjects of the false-positive (domains, URLs, or IPs)?

https://beenebrothers.com

Why do you believe this is a false-positive?

I have used multiple tools to look for issues and have found none, it's possible there is some file I've uploaded to the media section that is triggering something but I don't know and haven't been able to get anyone to mention what might the issue be. bitdefender removed me as a false positive and I don't exist in the Phistank or Openphish databases.

How did you discover this false-positive(s)?

Other (Please fill out the next box)

Where did you find this false-positive if not listed above?

Users telling me they couldn't access the site or were getting phish/scam warnings by their computer.

Have you requested a review from other sources?

BitDefender already removed as a false positive.

Do you have a screenshot?

Screenshot

Additional Information or Context

Thank you for reviewing!

@phishing-database-bot
Copy link
Member

Verification Required

@Fourthbean, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:

  1. Set a DNS TXT record for the domain(s) listed in this issue with the following details:

    • Record Name: _phishingdb
    • Record Value: antiphish-e9aa92073e49cc877b4a0680b493967ded1c2010

    Your Verification ID: antiphish-e9aa92073e49cc877b4a0680b493967ded1c2010

  2. Wait for DNS propagation (this may take a few minutes to a few hours).

  3. Reply to this issue once the TXT record has been set.

Important Notes

  • Verification does not guarantee whitelisting. The Phishing.Database team will review your report after verifying ownership, but the decision to whitelist depends on further investigation and analysis.
  • If the record cannot be set or you need alternative methods of verification, please contact us at [email protected] - preferably from the domain's official email address.

How to Check the TXT Record ?

You can verify that the TXT record is properly set using:

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.

@Fourthbean
Copy link
Author

Fourthbean commented Jan 10, 2025 via email

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Phishing Database Backlog Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

6 participants