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] azbybrokerage.com #1043

Open
cmorrow1-sucuri opened this issue Jan 21, 2025 · 1 comment
Open

[FALSE-POSITIVE] azbybrokerage.com #1043

cmorrow1-sucuri opened this issue Jan 21, 2025 · 1 comment

Comments

@cmorrow1-sucuri
Copy link

The site has been cleaned.

@phishing-database-bot
Copy link
Member

Verification Required

@cmorrow1-sucuri, 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-4fe8eceeefee8f8d94c5646168943f56e7a228a5

    Your Verification ID: antiphish-4fe8eceeefee8f8d94c5646168943f56e7a228a5

  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

2 participants