Skip to content

False Positive: Request to remove hostzop.com #1306

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
Spergeon123 opened this issue May 5, 2025 · 5 comments
Open

False Positive: Request to remove hostzop.com #1306

Spergeon123 opened this issue May 5, 2025 · 5 comments
Assignees

Comments

@Spergeon123
Copy link

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

Hello,

Our domain hostzop.com has been listed in your phishing-domains-ACTIVE.txt file, but this is a false positive.

We would like to formally request its removal from the database. hostzop.com is a legitimate hosting and IT services provider. The domain has been reviewed and approved as clean by top cybersecurity vendors and antivirus engines including but not limited to:

  • Google Safe Browsing
  • Microsoft Defender
  • Norton Safe Web
  • VirusTotal (0/XX detection rate)

We have also implemented all recommended best practices and security measures to prevent misuse of our domain, including:

  • DNSSEC
  • SPF, DKIM, and DMARC policies
  • Active WAF and server-side protections

Why do you believe this is a false-positive?

I believe this is a false-positive because, Our domain hostzop.com has been mistakenly listed in the phishing-domains-ACTIVE.txt file. It is a legitimate hosting provider and has been verified clean by major security vendors including Google Safe Browsing, Microsoft Defender, Norton, and VirusTotal.

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

Phishtank

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

our team has discovered that our domain has listed

Have you requested a review from other sources?

All top website has marked our website as legimate website

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

@phishing-database-bot
Copy link
Member

Verification Required

@Spergeon123, 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-d5f6eb9fe6ded109f5a1fdb54b7b7599ee7fd455

    Your Verification ID: antiphish-d5f6eb9fe6ded109f5a1fdb54b7b7599ee7fd455

  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.

@Spergeon123
Copy link
Author

Spergeon123 commented May 6, 2025 via email

@Spergeon123
Copy link
Author

Spergeon123 commented May 8, 2025 via email

@Spergeon123
Copy link
Author

We have set up a Txt record as above mentioned, please check and remove our domain from the phishing database immediately, we have attached a screenshot for your reference.

@Spergeon123
Copy link
Author

Please reply to this message once you have acknowledged it

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