False Positive | example.com

[Dooeeads]

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

da.jumpinglupata.online

Why do you believe this is a false-positive?

This domain is an internal tracking domain we use for the campaigns we run.

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

VirusTotal

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

In the Oddbytes, redirectcheck tool extension.

Have you requested a review from other sources?

No response

Do you have a screenshot?

Screenshot

Additional Information or Context

Hello,

I hope you are having a good day.
We would really appreciate if we could permanently clear our domain, "da.jumpinglupata.online" is just our internal tracking domain that we use in order to track the result of our programmatic campaigns.

Thank you for your consideration!

[phishing-database-bot]

Verification Required

@Dooeeads, 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-d6623e1c20ec5f70a96224f6aeffcfc555817106

   Your Verification ID: antiphish-d6623e1c20ec5f70a96224f6aeffcfc555817106

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.

[phishing-database-bot]

Verification Required

@Dooeeads, 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-d6623e1c20ec5f70a96224f6aeffcfc555817106

   Your Verification ID: antiphish-d6623e1c20ec5f70a96224f6aeffcfc555817106

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.

[phishing-database-bot]

Closing.

Subject(s) not found in the Phishing.Database project: da.jumpinglupata.online.

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