False Positive | found.ee

[twinchester-foundee]

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

found.ee.com
https://found.ee

Why do you believe this is a false-positive?

Hello! We are developing a marketing and advertising platform Found.ee. As a part of this service we provide a link shortening feature. We have multiple measures in place to prevent from publishing fishing or malicious links through our platform and work closely with such providers as AWS and Google. We would like you to review this because it is apparently considered phishing.
Happy to provide further details/assistance if needed.

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

@twinchester-foundee, 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-6c64c1c378cb1c3df2d623371d2f100d49f07d2c

   Your Verification ID: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c

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.

[twinchester-foundee]

Looping in @oleg Maximchuk ***@***.***> to help on these additional steps for domain verification. *Taylor Winchester* found.ee - A Downtown <http://downtownmusic.com/> Company | The Music Industry Lives Here US based - est time zone The content of this email is confidential and is intended for the recipient specified in the message only. If you have received this message in error, please refrain from distributing or copying this message and delete this message, including all copies and backups of it.

…

On Wed, Mar 12, 2025 at 3:58 PM Phishing Database ***@***.***> wrote: Verification Required @twinchester-foundee <https://github.com/twinchester-foundee>, 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-6c64c1c378cb1c3df2d623371d2f100d49f07d2c *Your Verification ID*: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c 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 <#1242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKV46JJ4KFZJHBZBRTZYKPL2UCGXBAVCNFSM6AAAAABY4PL2QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHE2TSMZZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: phishing-database-bot]*phishing-database-bot* left a comment (Phishing-Database/Phishing.Database#1242) <#1242 (comment)> Verification Required @twinchester-foundee <https://github.com/twinchester-foundee>, 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-6c64c1c378cb1c3df2d623371d2f100d49f07d2c *Your Verification ID*: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c 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 <#1242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKV46JJ4KFZJHBZBRTZYKPL2UCGXBAVCNFSM6AAAAABY4PL2QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHE2TSMZZHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[twinchester-foundee]

Hello! The TXT record has been added.

…

On 12 Mar 2025, at 23:12, Taylor Winchester ***@***.***> wrote: Looping in @oleg Maximchuk ***@***.***> to help on these additional steps for domain verification. Taylor Winchester found.ee <http://found.ee/> - A Downtown <http://downtownmusic.com/> Company | The Music Industry Lives Here US based - est time zone The content of this email is confidential and is intended for the recipient specified in the message only. If you have received this message in error, please refrain from distributing or copying this message and delete this message, including all copies and backups of it. On Wed, Mar 12, 2025 at 3:58 PM Phishing Database ***@***.*** ***@***.***>> wrote: > > phishing-database-bot > left a comment > (Phishing-Database/Phishing.Database#1242) > Verification Required > > @twinchester-foundee, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps: > > Set a DNS TXT record for the domain(s) listed in this issue with the following details: > > Record Name: _phishingdb > Record Value: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c > Your Verification ID: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c > > Wait for DNS propagation (this may take a few minutes to a few hours). > > 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. > 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, or unsubscribe. > You are receiving this because you were mentioned. > > <https://github.com/twinchester-foundee> ***@***.***> <https://mxtoolbox.com/TXTLookup.aspx> <http://phishingdb.example.com/> <#1242 (comment)> <https://github.com/notifications/unsubscribe-auth/BKV46JJ4KFZJHBZBRTZYKPL2UCGXBAVCNFSM6AAAAABY4PL2QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHE2TSMZZHA> > > phishing-database-bot > left a comment > (Phishing-Database/Phishing.Database#1242) > <#1242 (comment)> > Verification Required > > @twinchester-foundee <https://github.com/twinchester-foundee>, thank you for submitting a false positive report! To help us verify your ownership of the affected domain(s), please complete the following steps: > > Set a DNS TXT record for the domain(s) listed in this issue with the following details: > > Record Name: _phishingdb > Record Value: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c > Your Verification ID: antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c > > Wait for DNS propagation (this may take a few minutes to a few hours). > > 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 <http://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 <#1242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKV46JJ4KFZJHBZBRTZYKPL2UCGXBAVCNFSM6AAAAABY4PL2QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYHE2TSMZZHA>. > You are receiving this because you were mentioned. >

[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

[omaximchuk]

Hello! Can you please review again? The TXT record has been added on our domain found.ee

[spirillen]

Comments

I can't seem to find you in the Phishing Database! While I do see you on quite a few other blacklists, you’re not listed in the PD. It appears you’ve been blacklisted by @PeterDaveHello, you are therefor secure a spot on the whitelist here through automation. Quite the twist, isn’t it?

DNS Check

ptcheck found.ee antiphish-6c64c1c378cb1c3df2d623371d2f100d49f07d2c
The test value matches the DNS TXT record.

Thanks for using my tools.
Please consider a sponsor ship at https://www.mypdns.org/donate

Known phishing records

What can you tell me about these records, known to us from the PD project?

N/A

Verdict

Amazon hosted, hot touching this, and can't find any records for the domain in PD. Closing as invalid

Known Issues

• https://kb.mypdns.org/issue/MTX-121155/found.ee MTX-121155
• https://mypdns.youtrack.cloud/issue/MTXB-203680/found.ee MTXB-203680
• found.ee mypdns/matrix#121155
• found.ee AdguardTeam/AdguardFilters#111453

---

Thank you for reaching out. I want to clarify that I am not the owner of this project nor user of it. I assist with the whitelisting of domains to the best of my ability, but I do this as an unpaid volunteer in my free time. Your understanding and patience are greatly appreciated.
Additionally, I would like to share that I occasionally struggle with a mild degree of PTSD, which means I tend to forget even small details, like did I have breakfast this morning. So please bare with me, if I'm loosing the thread sometimes. Your understanding and patience in this matter are greatly appreciated.

If you feel inclined to buy me a cup of coffee, it would certainly help speed up the process, but please know that it will not influence my decisions or verdicts in any way.

Additionally, I want to be very clear: I do not access any Cloudflare, CloudFront, or Google networks. This is a matter of principle for me, as I believe in upholding human rights, the right to online privacy, and network security. These services often intercept traffic to collect personally identifiable information (PII), which I believe compromises our autonomy and makes us all puppets to the big tech puppeteers.

Thank you for your understanding!

Best regards.