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 | fda.bj #1028

Open
r3s0lv3r opened this issue Jan 16, 2025 · 1 comment
Open

False Positive | fda.bj #1028

r3s0lv3r opened this issue Jan 16, 2025 · 1 comment
Assignees

Comments

@r3s0lv3r
Copy link

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

fda.bj

Why do you believe this is a false-positive?

After conducting a thorough analysis, we have not found any evidence of compromise or malicious activity that would justify this categorization as phishing website. As part of our investigation, we reviewed all files hosted on the site and no anomalies were identified. Additionally, we analyzed network logs to detect any suspicious behavior but found nothing unusual. Finally, we submitted the website to external scanners, such as PhishTank which did not detect any threats.

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

Phishtank

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

Screenshot of False Positive

Have you requested a review from other sources?

I have requested a review from...

Do you have a screenshot?

No response

Additional Information or Context

I have also noticed that...

@phishing-database-bot
Copy link
Member

Verification Required

@r3s0lv3r, 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-42a3ef9012824a613b161f08f05ec05d52110b5a

    Your Verification ID: antiphish-42a3ef9012824a613b161f08f05ec05d52110b5a

  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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

6 participants