False Positive | example.com

[Patrol-12]

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

https://ccip-55l1mmun0-chainlinklabs.vercel.app

Why do you believe this is a false-positive?

To whom it may concern,

I am writing on behalf of ChainPatrol, the brand protection provider for Chainlink.

We have identified that the domain https://ccip-55l1mmun0-chainlinklabs.vercel.app is currently being blocked by your service. This appears to be a false positive; we are already working with several other providers on VirusTotal to resolve similar misflagging.

Could you please review and unblock this domain? If you require verification or further information, I am happy to connect you directly with the Chainlink team.

Thank you for your assistance.

Chainlink - Power of Attorney.pdf

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

VirusTotal

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

This was raised by our client, Chainlink.

Chainlink - Power of Attorney.pdf

Have you requested a review from other sources?

We’ve sent unflagging request to alphamountain.ai, GData, Bitdefender and more.

Do you have a screenshot?

Screenshot

Additional Information or Context

No response

[phishing-database-bot]

Verification Required

@Patrol-12, 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-f63d748b7a06019048cc0031d7100bfd30b3c48c

   Your Verification ID: antiphish-f63d748b7a06019048cc0031d7100bfd30b3c48c

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

@Patrol-12, 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-f63d748b7a06019048cc0031d7100bfd30b3c48c

   Your Verification ID: antiphish-f63d748b7a06019048cc0031d7100bfd30b3c48c

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.