-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
False Positive | example.com #1087
Comments
Verification Required@prestaguru, 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. |
DONE
From: Phishing Database ***@***.***>
Sent: Sunday, February 2, 2025 12:50 PM
To: Phishing-Database/Phishing.Database ***@***.***>
Cc: PrestaGuru.pl ***@***.***>; Mention ***@***.***>
Subject: Re: [Phishing-Database/Phishing.Database] False Positive | example.com (Issue #1087)
Verification Required
@prestaguru <https://github.com/prestaguru> , 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-b58139cbc00427768d895182b39e4c3678ec88c5
Your Verification ID: antiphish-b58139cbc00427768d895182b39e4c3678ec88c5
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 <#1087 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AST373INJFZJKVZBTVKC7WL2NYA6XAVCNFSM6AAAAABWKKFLYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGM3DEMZQGE> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AST373ISYSJKXGGOFJIF3D32NYA6XA5CNFSM6AAAAABWKKFLYKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU4XDRH2.gif> Message ID: ***@***.*** ***@***.***> >
|
I doubt this issue is regarding |
What are the subjects of the false-positive (domains, URLs, or IPs)?
https://beiks.com.pl
https://www.beiks.com.pl
Why do you believe this is a false-positive?
I believe this is a false-positive because i clean all malware from site and close SQL Injection posibility
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
Have you requested a review from other sources?
I have requested a review from...
securi
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: