Skip to content
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 | lueriawinery.com #998

Open
dorjet1 opened this issue Jan 7, 2025 · 6 comments
Open

False Positive | lueriawinery.com #998

dorjet1 opened this issue Jan 7, 2025 · 6 comments
Assignees
Labels
false positive Should not be listed WIP

Comments

@dorjet1
Copy link

dorjet1 commented Jan 7, 2025

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

Hi,
I am writing to request the removal of our website, https://lueriawinery.com, from your blacklist.
Our website was previously flagged and listed, but we have since taken all necessary actions to resolve the issue. We thoroughly reviewed and secured the website, ensuring it is no longer compromised or poses any risks.

We kindly ask you to reevaluate our site and remove it from the blacklist. Please let us know if any further steps or information are required to assist in this process.

Thank you for your attention and support.

62.219.58.210

Why do you believe this is a false-positive?

Our website was previously flagged and listed, but we have since taken all necessary actions to resolve the issue

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

VirusTotal

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

VirusTotal

Have you requested a review from other sources?

I have requested a review from...

Do you have a screenshot?

No response

Additional Information or Context

I have also noticed that...

@spirillen
Copy link
Contributor

I don't see example.com in the database or any other blacklists!!

Search results

Lookup provided by My Privacy DNS

Hosts-Sources

External Hosts-Sources can be found here

pglYoyo.csv:pgl.example.com

Sorted result

pgl.example.com

EasyList

Matrix blacklist project

Did not find any matching RPZ records

Known Issues

DNS lookup

example.com.    41618   IN      NS      a.iana-servers.net.
example.com.    41618   IN      NS      b.iana-servers.net.

HTTP header

log, click to expand
HTTP/2 200 
content-encoding: gzip
accept-ranges: bytes
age: 407718
cache-control: max-age=604800
content-type: text/html; charset=UTF-8
date: Tue, 07 Jan 2025 12:14:03 GMT
etag: "3147526947"
expires: Tue, 14 Jan 2025 12:14:03 GMT
last-modified: Thu, 17 Oct 2019 07:18:26 GMT
server: ECAcc (bsb/27B8)
x-cache: HIT
content-length: 648

@dorjet1
Copy link
Author

dorjet1 commented Jan 7, 2025 via email

@spirillen
Copy link
Contributor

I find these records in the DB, which leads to http code 404. @g0d33p3rsec do you find any thing that indicates, this should not be removed from the project?

wget -qO- 'https://phish.co.za/latest/ALL-phishing-links.lst' | grep -i 'lueriawinery\.com'
https://lueriawinery.com/wp-admin/js/widgets/sbcglobal.net.htm
https://lueriawinery.com/wp-admin/js/widgets/sbcglobal.net.htm...
https://lueriawinery.com/wp-admin/js/widgets/sbcglobal.net.htm......

@spirillen spirillen moved this from 🆕 New to 👀 In review in Phishing Database Backlog Jan 7, 2025
spirillen added a commit to Phishing-Database/phishing that referenced this issue Jan 7, 2025
@spirillen spirillen added the WIP label Jan 7, 2025
@spirillen
Copy link
Contributor

i made a mistake on the subject, its lueriawinery.com

Could you please log in and change it, as it is disturbing my eyes 😒

I do not have sufficient power to do so for you.

spirillen added a commit to Phishing-Database/phishing that referenced this issue Jan 7, 2025
@dorjet1 dorjet1 changed the title False Positive | example.com False Positive | lueriawinery.com Jan 9, 2025
@dorjet1
Copy link
Author

dorjet1 commented Jan 9, 2025 via email

@spirillen spirillen added the false positive Should not be listed label Jan 9, 2025
@phishing-database-bot
Copy link
Member

Verification Required

@dorjet1, 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-aff72429e4317033b7eec662503562468f0c66f7

    Your Verification ID: antiphish-aff72429e4317033b7eec662503562468f0c66f7

  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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
false positive Should not be listed WIP
Projects
Status: 👀 In review
Development

No branches or pull requests

6 participants