False Positive | example.com

[ndawe-oss]

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

We recently identified that our domain (cfnl.ca) was being flagged by some security engines as potentially malicious.

Why do you believe this is a false-positive?

We have completed a full review and remediation, including:

Correcting DMARC configuration (now enforced with quarantine policy)
Removing duplicate DNS records
Verifying no malware or compromised content on the website
Confirming proper email authentication via Google Workspace
Our domain is now fully compliant with modern email security and DNS best practices.

We kindly request a re-evaluation and reclassification of cfnl.ca.

Please let us know if any additional information is required.

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?

A vendors internal IT scan

Have you requested a review from other sources?

Yes

Do you have a screenshot?

Screenshot

Additional Information or Context

No response

[phishing-database-bot]

Verification Required

@ndawe-oss, 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-1eec3e7133fb43748d83f7d736e320ea2a0c4d8a

   Your Verification ID: antiphish-1eec3e7133fb43748d83f7d736e320ea2a0c4d8a

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 support@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:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.

[phishing-database-bot]

Verification Required

@ndawe-oss, 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-1eec3e7133fb43748d83f7d736e320ea2a0c4d8a

   Your Verification ID: antiphish-1eec3e7133fb43748d83f7d736e320ea2a0c4d8a

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 support@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:

• Online tools like MXToolBox TXT Lookup.
• The command line:

  dig TXT _phishingdb.example.com
  

Thank you for your cooperation! We will address your issue as soon as possible after verification.

The Phishing.Database Project Team.