Skip to content

False Positive | storage.googleapis.com #1050

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

Open
smed79 opened this issue Jan 23, 2025 · 2 comments
Open

False Positive | storage.googleapis.com #1050

smed79 opened this issue Jan 23, 2025 · 2 comments
Assignees
Labels
bug Something isn't working false positive Should not be listed

Comments

@smed79
Copy link

smed79 commented Jan 23, 2025

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

  • storage.googleapis.com

Why do you believe this is a false-positive?

I believe this is a false-positive because storage.googleapis.com is a subdomain of Google Cloud Storage.

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

Other (Please fill out the next box)

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

I discovered this false-positive by visiting google community support

  • https://support.google.com/chromebook/thread/317456891/

Have you requested a review from other sources?

_

Do you have a screenshot?

_

Additional Information or Context

@phishing-database-bot
Copy link
Member

Verification Required

@smed79, 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-15100e5ac3b44369c30734fb2e899c7d79af21af

    Your Verification ID: antiphish-15100e5ac3b44369c30734fb2e899c7d79af21af

  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.

@phishing-database-bot
Copy link
Member

Closing.

Domain(s) or IP(s) not found in issue message or title.

-- We appreciate your help in refining this. Please let us know if anything seems incorrect.

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Phishing Database Backlog Apr 10, 2025
@github-project-automation github-project-automation bot moved this from ✅ Done to 📋 Backlog in Phishing Database Backlog Apr 11, 2025
@spirillen spirillen added the bug Something isn't working label Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working false positive Should not be listed
Projects
Status: 📋 Backlog
Development

No branches or pull requests

6 participants