False Positive | example.com

[pff2025]

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

https://passion-for-fitness.com/

Why do you believe this is a false-positive?

We are reaching out regarding the domain Passion-for-Fitness.com, which currently appears to be listed in your security database/blacklist. We’ve thoroughly investigated and resolved the root issue that may have triggered the listing.
Our website is now verified clean. Attached you will find a screenshot of a recent security scan, confirming that there are no threats or malicious activity associated with the domain.
We kindly request a review of your records and removal of our domain from your blacklist. Passion-for-Fitness.com is a legitimate fitness business and we are committed to maintaining the highest standards of cybersecurity and web hygiene.
Should you require any additional information or evidence, we are happy to provide it.
Thank you for your attention and support in resolving this matter.

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

Website was hacked

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

I discovered this false-positive by...

Have you requested a review from other sources?

I have requested a review from...

Do you have a screenshot?

Screenshot

Additional Information or Context

I have also noticed that...

[phishing-database-bot]

Verification Required

@pff2025, 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-90c344f521bd5d8ddef47969969ddec5d6aa6216

   Your Verification ID: antiphish-90c344f521bd5d8ddef47969969ddec5d6aa6216

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]

DNS Servers

ns-1477.awsdns-56.org.
ns-1600.awsdns-08.co.uk.
ns-601.awsdns-11.net.
ns-77.awsdns-09.com.

Network

HTTP/2 403 
date: Tue, 25 Mar 2025 13:43:58 GMT
content-type: text/html; charset=UTF-8
content-length: 4514
x-frame-options: SAMEORIGIN
referrer-policy: same-origin
cache-control: max-age=15
expires: Tue, 25 Mar 2025 13:44:13 GMT
set-cookie: __cf_bm=LP0hb54e604ln3aPEi2Dx69MNgfPHcc7Afy0opY9R9k_bRk76o; path=/; expires=Tue, 25-Mar-25 14:13:58 GMT; domain=.passion-for-fitness.com; HttpOnly; Secure; SameSite=None
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=2JF3%2FEWD1yocjJbr4LZ2Fx5SKK6Rrdpqsw32eorZdOVG"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 925ed71efde5f015-CDG
alt-svc: h3=":443"; ma=86400

Declined Assistance with Whitelisting Requests

I (@spirillen) regret to inform you that I will not be assisting with whitelisting requests in this matter by me, as you are utilising networks associated with Cloudflare, Google, Amazon, or Microsoft. These entities have a notorious reputation for disregarding individuals' Fundamental Human Rights and Online Privacy (as detailed here: https://kb.mypdns.org/articles/MPDNS-A-2).

As such, you will need to await assistance from a meta sheep who may be willing to help. I cannot support the surveillance of innocent individuals without a court order from a democratic country, which notably excludes, but is not limited to, the USA and Denmark.

Thank you for your understanding.

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