Skip to content

False Positive | dropland.net #1309

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

Open
Vladimir-Polyakov-Dzencode opened this issue May 6, 2025 · 4 comments
Open

False Positive | dropland.net #1309

Vladimir-Polyakov-Dzencode opened this issue May 6, 2025 · 4 comments
Assignees

Comments

@Vladimir-Polyakov-Dzencode

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

Please delete my website. https://dropland.net from the blacklist.

Cloudflare can change IP

  • 188.114.96.11

Why do you believe this is a false-positive?

There is no malware, scripts for catching or spamming on the site.
My site is on the GoDaddy server, the godaddy team conducted a full analysis of the site and did not find any problems with the site files and database.

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...

Have you requested a review from other sources?

We contacted CloudFlare support with the problem. They suggested that we perform a full check of the site code and database. After that, they told us that no viruses or phishing scripts were detected.

Do you have a screenshot?

Image
Image

Additional Information or Context

I have also noticed that...

@phishing-database-bot
Copy link
Member

Verification Required

@Vladimir-Polyakov-Dzencode, 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-40e675ba4c739852b38f8e21c86aee68a15a8576

    Your Verification ID: antiphish-40e675ba4c739852b38f8e21c86aee68a15a8576

  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.

@Vladimir-Polyakov-Dzencode
Copy link
Author

Done!

@Vladimir-Polyakov-Dzencode
Copy link
Author

; <<>> DiG 9.11.36-RedHat-9.11.36-13.el8 <<>> TXT _phishingdb.dropland.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2888
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_phishingdb.dropland.net. IN TXT

;; ANSWER SECTION:
_phishingdb.dropland.net. 300 IN TXT "antiphish-40e675ba4c739852b38f8e21c86aee68a15a8576"

;; Query time: 51 msec
;; SERVER: 10.255.255.1#53(10.255.255.1)
;; WHEN: Tue May 06 23:01:24 MSK 2025
;; MSG SIZE rcvd: 116

@Vladimir-Polyakov-Dzencode
Copy link
Author

Image

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