False Positive Review – fileroy.com

[newextractor]

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

https://fileroy.com/

Why do you believe this is a false-positive?

Dear G-Data Support Team

I hope you're doing well.

I'm reaching out to request a review of a false positive detection involving my website: https://fileroy.com/. It has been incorrectly flagged as malicious or unsafe, despite being a legitimate and secure site.

Details:

Website: https://fileroy.com/

Issue: False positive detection / Blocked access

Detected by: https://www.virustotal.com/

fileroy.com is a clean and secure platform, and we ensure all content complies with best practices for security and user safety. Please let us know if any specific issues triggered the flag so we can assist in the review process or make any necessary adjustments.

We kindly request that you review and remove the false positive classification at your earliest convenience. If additional information or verification is needed, I’d be happy to provide it.

Thank you for your support.

Best regards,
Admin
Owner, fileroy.com
support@fileroy.com

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

Have you requested a review from other sources?

I have requested a review from...

Do you have a screenshot?

https://i.ibb.co/27kTmvBZ/gd.png

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@newextractor, 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-e46e67082aa710fcb91f804f172beca355e32c02

   Your Verification ID: antiphish-e46e67082aa710fcb91f804f172beca355e32c02

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.

[phishing-database-bot]

Closing.

Domain(s) or IP(s) not found in the Phishing.Database project: fileroy.com, i.ibb.co.

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