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 | s.mkswft.com #1151

Open
alexhwoods opened this issue Feb 17, 2025 · 1 comment
Open

False Positive | s.mkswft.com #1151

alexhwoods opened this issue Feb 17, 2025 · 1 comment
Assignees

Comments

@alexhwoods
Copy link

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

  • s.mkswft.com
  • i.mkswft.com
  • *.mkswft.com

Why do you believe this is a false-positive?

I believe this is a false-positive because...

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

VirusTotal

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

Hello!

My name is Alex, and I work at Makeswift, a website builder. We are a website hosting platform, like Wordpress.

We've noticed a site we own, s.mkswft.com, has been classified as a false positive by your platform.

We'd like to ask you to reconsider this classification.

Have you requested a review from other sources?

CRDF:

Image

Do you have a screenshot?

I don't - this site of ours hosts our users files.

If y'all have a specific instance that was phishing, we'd love to know and we'll take it down ASAP.

Additional Information or Context

@phishing-database-bot
Copy link
Member

Verification Required

@alexhwoods, 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-bbe3c46c3761649143144ad84f67be825d14f59a

    Your Verification ID: antiphish-bbe3c46c3761649143144ad84f67be825d14f59a

  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 contact@phish.co.za - 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