False Positive | https://dropland.net

[Vladimir-Polyakov-Dzencode]

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

• dropland.net
• dev.dropland.net
• https://dropland.net/*
• NSFW dropland.net
• 176.99.11.44

Why do you believe this is a false-positive?

There is no malware, scripts for catching or spamming on the site.
Our site is currently hosted on the Reg.ru server.
However, earlier (a month ago), when we used the GoDaddy server. We asked the Godaddy team to conduct a full analysis of the site code and database. As a result of the check, no phishing scripts were found.

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?

I have requested a review from:

• Socradar
• GoDaddy - We contacted GoDaddy 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?

Additional Information or Context

We have opened a similar request before, but there is still no answer to it.
#1309

[phishing-database-bot]

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

   Your Verification ID: antiphish-e5ed6700937301a8dc8c9a4e7a6b541e94594545

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 contact@phish.co.za - 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.

[Vladimir-Polyakov-Dzencode]

root@176-99-11-44:~# dig TXT _phishingdb.dropland.net

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> TXT _phishingdb.dropland.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28160
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

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

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

;; Query time: 68 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu May 15 10:01:17 UTC 2025
;; MSG SIZE rcvd: 179

[phishing-database-bot]

Closing.

Domain(s) or IP(s) not found in the Phishing.Database project: dev.dropland.net, 176.99.11.44, dropland.net.

-- We appreciate your help in refining this. Please let us know if anything seems incorrect.