False Positive | hoo.be

[Nathaniellaquis]

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

hoo.be creator.hoo.be

Why do you believe this is a false-positive?

hoo.be is a legitimate “link-in-bio” platform used by verified creators, public figures, and global brands.
Examples of safe official pages include:

• hoo.be/jeffbezos
• hoo.be/chrishemsworth
• hoo.be/siswimsuit
• hoo.be/forever21
• creator.hoo.be (creator dashboard)
• hoo.be/_next/static/ (static assets folder)

The platform has been operating for 20+ years without issue, and VirusTotal + all major security vendors now classify hoo.be as clean.

This false positive is actively harming creators, agencies, and brand partners who rely on hoo.be to share content.

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

Phishtank

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

Phishing.Database results and VirusTotal aggregation.

Have you requested a review from other sources?

Yes.

• CRDF Labs: approved
• Certego: approvevd
• Gridinsoft: approved
• CleanBrowsing: request submitted
• Comcast / AT&T: approved

VirusTotal report:
https://www.virustotal.com/gui/url/69d8e13a1ba7e27dfeb3c307ae4a51f436305b8d7312b704fe5f6beec122095c

Do you have a screenshot?

No response

Additional Information or Context

Please prioritize review as this block is urgent — creators and brands are unable to access or share their official pages through hoo.be. The domain is safe, verified, and provides essential services for global partners.

[phishing-database-bot]

Verification Required

@Nathaniellaquis, 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-a891fa55a8e4089593fe57f2ca517ef4e92175c7

   Your Verification ID: antiphish-a891fa55a8e4089593fe57f2ca517ef4e92175c7

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 [email protected] - 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]

Closing.

This issue has been marked as stale. Please don't hesitate to reopen and leave a comment if you believe this is an error.

-- We appreciate your help in refining this. Please let us know if anything seems incorrect.