False Positive | https://www.beiks.com.pl/

[zannat1239]

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

• example.com
• sub.example.com
• https://example.com/page
• https://sub.example.com/page
• NSFW example.com
• 192.168.0.0/16
• https://www.beiks.com.pl/

Why do you believe this is a false-positive?

I believe this is a false-positive because...
Dear Team,
My website https://www.beiks.com.pl/ was hacked. That's why you put it into the blacklist.
Thanks for bringing the problem to our notice. We take pride in ensuring our visitor's security. Upon thorough review of the situation, we narrowed the cause to be some recent changes in our website. We have deleted all the phishing pages and malware from our website. Moreover, we have installed a Web Application firewall and a regular malware scanning tool for 24x7 security. Please unblock it from your blocklist database.

Best Regards,
The webmaster of "https://www.beiks.com.pl/"

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

VirusTotal

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

I discovered this false-positive by...
Dear Team,
My website https://www.beiks.com.pl/ was hacked. That's why you put it into the blacklist.
Thanks for bringing the problem to our notice. We take pride in ensuring our visitor's security. Upon thorough review of the situation, we narrowed the cause to be some recent changes in our website. We have deleted all the phishing pages and malware from our website. Moreover, we have installed a Web Application firewall and a regular malware scanning tool for 24x7 security. Please unblock it from your blocklist database.

Best Regards,
The webmaster of "https://www.beiks.com.pl/"

Have you requested a review from other sources?

I have requested a review from...

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@zannat1239, 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-ae2148616c6cff0b6d81314c001f1d57d49b3703

   Your Verification ID: antiphish-ae2148616c6cff0b6d81314c001f1d57d49b3703

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.