False Positive | example.com

[hwtechsupport]

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

• 192.236.177.160

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?

IP address listed.

Have you requested a review from other sources?

NA

Do you have a screenshot?

https://hw-screenshots.sea-proxy.windystorage.com/screenshots/2025-02-20_14-14-26_279b68ff-3087-43bb-b523-b0bcd332a6ed.png)

Additional Information or Context

NA

[phishing-database-bot]

Verification Required

@hwtechsupport, 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-a648304f8ab15635f2c5cae5f497f4675ac06bd1

   Your Verification ID: antiphish-a648304f8ab15635f2c5cae5f497f4675ac06bd1

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.

[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