False Positive | apps.wwf.org.hk

[roywwf]

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

Apps.wwf.org.hk

Why do you believe this is a false-positive?

We recently discovered that your database has flagged our domain apps.wwf.org.hk as a suspected phishing site. We want to confirm that our site is legitimate and secure, and we believe this classification is a false positive.

To verify this, we have conducted our own security checks and have also reviewed assessments from other security platforms, all of which have identified our site as clean. Given this, we kindly request that you review our domain's classification and remove it from the phishing list if confirmed to be a false positive.

Please let us know if you require any further details to assist with your review. We appreciate your prompt attention to this matter.

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

VirusTotal

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

I discovered this false-positive on VirusTotal

Have you requested a review from other sources?

by Gridinsoft and Norton.

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@roywwf, 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-ff197bbe2d23d0123fd44d417078fdb97aefe24e

   Your Verification ID: antiphish-ff197bbe2d23d0123fd44d417078fdb97aefe24e

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:

• 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.

[roywwf]

Dear Support Team, The TXT record for our domain _phishingdb.wwf.org.hk has been set and propagated. Kindly verify it at your earliest convenience. Thanks! Warm regards, Roy Senior Manager, IT WWF-Hong Kong 世界自然基金會香港分會 Tel: +852 2864 1430 E-mail: ***@***.******@***.***> ***@***.***?anonymous&isanonymous=true> Book time to meet with ***@***.***?anonymous&isanonymous=true> [cid:efe6edb9-3882-4d5d-9d88-2b7a91df03a8]<https://earthhour.wwf.org.hk/>

…

________________________________ From: Phishing Database ***@***.***> Sent: Tuesday, March 11, 2025 12:37 To: Phishing-Database/Phishing.Database ***@***.***> Cc: Roy Fok (IT) ***@***.***>; Mention ***@***.***> Subject: Re: [Phishing-Database/Phishing.Database] False Positive | example.com (Issue #1233) Verification Required @roywwf<https://github.com/roywwf>, 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-ff197bbe2d23d0123fd44d417078fdb97aefe24e Your Verification ID: antiphish-ff197bbe2d23d0123fd44d417078fdb97aefe24e 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 ***@***.******@***.***> - 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<https://mxtoolbox.com/TXTLookup.aspx>. * 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. — Reply to this email directly, view it on GitHub<#1233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BQKZAQ2WJCAI3VVNHVI5VST2TZSADAVCNFSM6AAAAABYX3JZL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGU4TGNJZHE>. You are receiving this because you were mentioned.Message ID: ***@***.***> [phishing-database-bot]phishing-database-bot left a comment (Phishing-Database/Phishing.Database#1233)<#1233 (comment)> Verification Required @roywwf<https://github.com/roywwf>, 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-ff197bbe2d23d0123fd44d417078fdb97aefe24e Your Verification ID: antiphish-ff197bbe2d23d0123fd44d417078fdb97aefe24e 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 ***@***.******@***.***> - 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<https://mxtoolbox.com/TXTLookup.aspx>. * 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. — Reply to this email directly, view it on GitHub<#1233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BQKZAQ2WJCAI3VVNHVI5VST2TZSADAVCNFSM6AAAAABYX3JZL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGU4TGNJZHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

________________________________ CAUTION: EXTERNAL EMAIL This email originated from OUTSIDE the organization. Kindly exercise caution and abstain from clicking on any links or opening attachments unless you are acquainted with the sender and can verify the safety of the content. Be cautious about providing sensitive information and remain vigilant against scams.

________________________________ Registered Name 註冊名稱: World Wide Fund For Nature Hong Kong 世界自然(香港)基金會 (Incorporated in Hong Kong with limited liability by guarantee於香港註冊成立的擔保有限公司). This email (including any attachments) is intended for the use of the designated recipient(s) only, which may contain confidential, non-public, proprietary information, and/or be protected by the attorney-client or other privilege. Any unauthorized reading, distribution, copying, or other use of this communication is strictly prohibited and may be unlawful. Receipt by anyone other than the intended recipient(s) should not be deemed a waiver of any privilege or protection. If you are not the intended recipient or believe you have received this email in error, please notify the sender immediately and delete this email from your computer system. This email and any attachments are checked for viruses and other malicious software ("malware"). However, the sender does not warrant, represent, or guarantee in any way that this communication is free from malware or potentially damaging defects. The sender disclaims all liability for any errors, omissions, or damages arising out of or in connection with the use or reliance on the information contained in this email.

[spirillen]

Hello there!

Thank you for your message and for bringing this to our attention. It appears we’ve stumbled upon a classic case of “example domain confusion” – a bit like trying to order a proper cup of tea in a coffee shop, isn’t it?

To proceed with the whitelist process, it is required to change the issue topic to reflect the actual situation regarding your domain (and domain name only). Until that’s done, I’m afraid we’ll be stuck in a bit of a holding pattern, much like a plane circling Heathrow on a foggy day.

As a gentle reminder, the RFCs concerning example domains (RFC 2606) clarify that domains like example.com, example.net, and example.org are reserved for documentation and should not be used for actual operational purposes.

Once you’ve made the necessary adjustments, we’ll be more than happy to unlock the issue and continue our merry way. Looking forward to your update!

Cheers!
@spirillen

[roywwf]

Thanks! the issue topic has been updated with the domain name.