False Positive | account.docusign.com

[PeterDaveHello]

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

account.docusign.com

Why do you believe this is a false-positive?

You can verify that docusign.com is the primary domain of the famous Docusign, Inc. software company, headquartered in San Francisco. account.docusign.com is the domain of there login and account management related pages, e.g. https://account.docusign.com/oauth/auth

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

Other (Please fill out the next box)

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

By my own?

Have you requested a review from other sources?

I didn't see it been blocked by any others yet.

Do you have a screenshot?

Additional Information or Context

[phishing-database-bot]

Verification Required

@PeterDaveHello, 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-4afe78f4bb029b266148dd56161301a17781053a

   Your Verification ID: antiphish-4afe78f4bb029b266148dd56161301a17781053a

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

@PeterDaveHello, 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-4afe78f4bb029b266148dd56161301a17781053a

   Your Verification ID: antiphish-4afe78f4bb029b266148dd56161301a17781053a

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.

[PeterDaveHello]

I don't own the domain 😅

[phishing-database-bot]

Closing.

Subject(s) not found in the Phishing.Database project: 185.81.100.110, 9.9.9.9, 185.81.100.109, 185.81.101.109, 193.110.81.0, 156.154.70.2, dns0.eu, 64.207.217.76, 94.140.14.140, 195.46.39.39, 193.110.81.254, 9.9.9.10, 185.81.101.110, 64.6.64.6, 95.85.95.85, 64.207.217.77, 94.140.14.14, 192.165.9.157, docusign.com, 185.81.100.108, 76.76.2.1, 101.101.101.101, 1.1.1.2, 8.26.56.26, 1.1.1.1, 64.207.218.77, 8.8.8.8, 188.166.206.224, 64.207.216.77, 64.207.216.75, 185.228.168.9, 208.67.222.222, 77.88.8.1, 77.88.8.2, 76.76.2.2, dnsforge.de, 168.95.1.1, 176.9.93.198, 208.67.222.2.

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