-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Comments
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:
Important Notes
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. |
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.
…On Mon, May 5, 2025 at 3:42 PM Phishing Database ***@***.***> wrote:
*phishing-database-bot* left a comment
(Phishing-Database/Phishing.Database#1306)
<#1306 (comment)>
Verification Required
@Spergeon123 <https://github.com/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 ***@***.*** - 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
<https://mxtoolbox.com/TXTLookup.aspx>.
- 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.*
—
Reply to this email directly, view it on GitHub
<#1306 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BSE262LPOPMQACTRS4EMNOT2442RJAVCNFSM6AAAAAB4OHXOW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJQGUZTCNJXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
…On Mon, May 5, 2025 at 3:42 PM Phishing Database ***@***.***> wrote:
*phishing-database-bot* left a comment
(Phishing-Database/Phishing.Database#1306)
<#1306 (comment)>
Verification Required
@Spergeon123 <https://github.com/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 ***@***.*** - 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
<https://mxtoolbox.com/TXTLookup.aspx>.
- 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.*
—
Reply to this email directly, view it on GitHub
<#1306 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BSE262LPOPMQACTRS4EMNOT2442RJAVCNFSM6AAAAAB4OHXOW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJQGUZTCNJXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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. |
Please reply to this message once you have acknowledged it |
What are the subjects of the false-positive (domains, URLs, or IPs)?
Hello,
Our domain
hostzop.com
has been listed in yourphishing-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:We have also implemented all recommended best practices and security measures to prevent misuse of our domain, including:
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...
The text was updated successfully, but these errors were encountered: