False Positive | brainshare.ng

[adsegzyhub]

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

• brainshare.ng

Why do you believe this is a false-positive?

I believe this is a false-positive because we area reputable organization which have an image and credibility to protect. We are license and in all we do and govern by the government policies.

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?

I discovered this false-positive by
https://www.virustotal.com/gui/url/6c23c5c8fe5c3a6e7159582063ab5a141e0b1e4c555eaeaa86a2b198485bf34d/detection

Have you requested a review from other sources?

I have requested a review from...

• https://quttera.com/detailed_report/brainshare.ng
• https://www.ipqualityscore.com/threat-feeds/malicious-url-scanner/brainshare.ng

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@adsegzyhub, 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-2db5b8c96c579f5854e1112f52b3512904e7cbbf

   Your Verification ID: antiphish-2db5b8c96c579f5854e1112f52b3512904e7cbbf

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:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

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

The Phishing.Database Project Team.

[g0d33p3rsec]

duplicate of #1107

[spirillen]

duplicate of #1107

@g0d33p3rsec Which one are going to be closed?

[g0d33p3rsec]

duplicate of #1107

@g0d33p3rsec Which one are going to be closed?

#1107 has the initial analysis, this one seems less relevant but more properly formatted.