False Positive | go.onelink.me

[xv-carlos-c]

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

• go.onelink.me

Why do you believe this is a false-positive?

We use appsflyer to host a bunch of affiliate urls in our site, for instance we have the following redirection path https://www.expressvpn.com/fumiya -> https://go.onelink.me/yAeP/fumiya -> https://apps.apple.com/US/app/id886492891?mt=8 -> https://apps.apple.com/us/app/expressvpn-secure-fast-vpn/id886492891?mt=8

The affiliate URL won't work as the go.onelink.me subdomain is blocked

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

Other (Please fill out the next box), OpenPhish

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

ExpressVPN Advanced protection

Have you requested a review from other sources?

No response

Do you have a screenshot?

Screenshot

Additional Information or Context

No response

[phishing-database-bot]

Verification Required

@xv-carlos-c, 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-92691ea75fab9823409008abc487e8fb54382eee

   Your Verification ID: antiphish-92691ea75fab9823409008abc487e8fb54382eee

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]

Verification Required

@xv-carlos-c, 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-92691ea75fab9823409008abc487e8fb54382eee

   Your Verification ID: antiphish-92691ea75fab9823409008abc487e8fb54382eee

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.