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

Phishing | example.com #1034

Open
QRTIGERS opened this issue Jan 20, 2025 · 1 comment
Open

Phishing | example.com #1034

QRTIGERS opened this issue Jan 20, 2025 · 1 comment
Assignees

Comments

@QRTIGERS
Copy link

What are the subjects of the phishing (domains, URLs or IPs)?

  • qr1.be

What are the impersonated domains?

  • qr1.be

Where or how did you discover this phishing?

I discovered this phising report through virustotal

Do you have a screenshot?

Virus total show a phishing report which affect our customer to access this domain.

Image

Related external source

Additional Information or Context

I am reaching out to request a review of the following URL, which appears to have been flagged as phishing in error: https://qr1.be

The URL is legitimate and our customer use this domain to create dynamic QR. We believe this classification is incorrect and would appreciate your assistance in removing it from any blacklists or warning lists.

Please let me know if additional information or documentation is required to resolve this matter.

Thank you for your attention to this request

@phishing-database-bot
Copy link
Member

Verification Required

@QRTIGERS, 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-c8fe30bb74675a3c48e6427d8258b9c5fba5f496

    Your Verification ID: antiphish-c8fe30bb74675a3c48e6427d8258b9c5fba5f496

  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
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

6 participants