mitchellkrogza
False Positive | example.com
What are the subjects of the false-positive (domains, URLs, or IPs)?
https://intranet.assalweb.org
Why do you believe this is a false-positive?
Hello team, Please re-evaluate assalweb.org, www.assalweb.org , and all subdomains (e.g., historico.assalweb.org, intranet.assalweb.org). The primary domain was compromised under a previous provider. We have since taken over maintenance, removed malicious/phishing content, and hardened the environment. Actions completed: Updated CMS and plugins Rotated all credentials/keys and enabled 2FA Enabled a web application firewall Enforced security headers Implemented continuous integrity monitoring with daily malware scans
All recent scans are clean, and there’s been no malicious activity since remediation. Note: the subdomains listed above were not infected, but they previously resided on the same server; we have verified them and they are clean. Kindly remove the malware/phishing classification for the domain and all subdomains, and categorize as Organizations/Non-Profit. Thank you.
How did you discover this false-positive(s)?
VirusTotal
Where did you find this false-positive if not listed above?
Listed above.
Have you requested a review from other sources?
AlphaMountain Lionic Vipre ESET
Do you have a screenshot?
Screenshot
Additional Information or Context
No response
Verification Required
@AldoTapiaInnova, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:
-
Set a DNS TXT record for the domain(s) listed in this issue with the following details:
- Record Name:
_phishingdb - Record Value:
antiphish-690491cf697ea90f14305f49e86207be7f6bc520
Your Verification ID:
antiphish-690491cf697ea90f14305f49e86207be7f6bc520 - Record Name:
-
Wait for DNS propagation (this may take a few minutes to a few hours).
-
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.
Verification Required
@AldoTapiaInnova, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps:
-
Set a DNS TXT record for the domain(s) listed in this issue with the following details:
- Record Name:
_phishingdb - Record Value:
antiphish-690491cf697ea90f14305f49e86207be7f6bc520
Your Verification ID:
antiphish-690491cf697ea90f14305f49e86207be7f6bc520 - Record Name:
-
Wait for DNS propagation (this may take a few minutes to a few hours).
-
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.