You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is a false-positive. We (my partner Saskia the Wit and I) run an online webshop for second hand analogue photo equipment. We have security plugins installed on our Wordpress site (Jetpack protect + Security Optimizer by SiteGround, our host + Wordfence Security), ran scans on our website to detect possible problems and are sure nothing malicious is running, if there ever was. Sites like Phishtank and OpenPhish and dosens of site alike have not found anything wrong with our site and thus have not listed us. And those few sites that have listed us agreed it was a false positive.
Please, remove the false positive of our site from your database.
Thank you a bunch!
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 on a list of Scanning Engines by urlvoid.com
None (including Phishtank, OpenPhish - sites you recommended - but almost all other have NOT found anything wrong with our site, except for CRDF and your database. We are in the process of setting things straight with CRDF as well.
Do you have a screenshot?
Additional Information or Context
The text was updated successfully, but these errors were encountered:
@RoelantHollander, 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-3670d23f23bbc42f1e1ed597524655512a3d3752
Your Verification ID: antiphish-3670d23f23bbc42f1e1ed597524655512a3d3752
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:
What are the subjects of the false-positive (domains, URLs, or IPs)?
https://dewitcameras.com
Why do you believe this is a false-positive?
I believe this is a false-positive. We (my partner Saskia the Wit and I) run an online webshop for second hand analogue photo equipment. We have security plugins installed on our Wordpress site (Jetpack protect + Security Optimizer by SiteGround, our host + Wordfence Security), ran scans on our website to detect possible problems and are sure nothing malicious is running, if there ever was. Sites like Phishtank and OpenPhish and dosens of site alike have not found anything wrong with our site and thus have not listed us. And those few sites that have listed us agreed it was a false positive.
Please, remove the false positive of our site from your database.
Thank you a bunch!
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 on a list of Scanning Engines by urlvoid.com
Have you requested a review from other sources?
That same site urlvoid.com has a list of Scanning Engines and if dewitcameras.com has been marked or not. https://www.urlvoid.com/scan/dewitcameras.com/
None (including Phishtank, OpenPhish - sites you recommended - but almost all other have NOT found anything wrong with our site, except for CRDF and your database. We are in the process of setting things straight with CRDF as well.
Do you have a screenshot?
Additional Information or Context
The text was updated successfully, but these errors were encountered: