Evidence Best Practice Guidelines

When reporting malicious activity to third-party vendors, they will request particular information related to the activity so that the suspicious site, domain, or similar can be removed. The following sections describe the documentation and information vendors will request to remediate malicious activity.

Evidence required by vendors for remediation

These tables describe the data required by vendors when reporting malicious activity as part of the remediation process. You can find more information about uploading trademarks and letters of authorization (LOA) in Preparing for Remediation. In general, remediations are more successful if you have provided both the company’s Registered Trademark and a signed Letter of Authorization (LOA) in Configurations.

Requirements for Exploitable Data, Data Leakage, Brand Security, or VIP takedown remediation

Vendor NameWhat needs to be taken down?Trademark Needed?LOA Needed?Details
Apple App StoreTrademark - Client's logo or Client's nameThe vendor requires a trademark registration document.
Application StoresTrademark - Client's logo or Client's nameThe vendor may require a trademark registration document and a signed LOA in some cases (depending on the application store).
Email OutlookA phishing email that was sent by the reported email addressThe vendor requires a copy of the abusive message that was sent by the reported email address (including the full message header).
EtsyTrademark - Client's logo or Client's nameThe team doesn’t have enough data on this type of case to determine which documents are needed.
Facebook - Trademark and copyrightTrademark - Client's logo or Client's nameThe trademark registration document is mandatory and the vendor requires a signed LOA in some cases.
Facebook - VIPVIP's name and photoThe VIP's ID is required by the vendor. There are two options:
1. Government ID: Driver's license, national identity card, passport, or birth certificate. The ID must include the VIP's name and date of birth or name and photo.
2. Non-Government IDs: Student card, library card, refugee card, employment verification, diploma, or loyalty card.
All IDs must include the VIP's name, and at least one of the two IDs must include the VIP's date of birth and/or photo.

The vendor requires a signed LOA required in some cases.
FlickrTrademark - Client's logo or client's nameThe team doesn’t have enough data on this type of case to determine which documents are needed.
GitHubSensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets
- Source code
- Documents
Files/repositories that expose:
1. Access credentials, such as user names combined with passwords, access tokens, or other sensitive secrets that can grant access to your organization's server, network, or domain.
2. AWS tokens and other similar access credentials that grant access to a third party on your behalf. You must be able to show that the token does belong to you.
3. Documentation (such as network diagrams or architecture) that poses a specific security risk for an organization.
4. Information related to, and posing a security risk to, you as an individual (such as social security numbers or other government identification numbers).
Google AdsTrademark - Client's logo or client's nameThe vendor requires a trademark registration document and a signed LOA.
Google PlayTrademark - Client's logo or client's nameThe vendor requires a trademark registration document and a signed LOA.
Google PlusTrademark - Client's logo or client's nameThe vendor requires a trademark registration document and a signed LOA.
Instagram - Trademark or CopyrightTrademark - Client's logo or client's nameA trademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
Instagram - VIPVIP's name and photoThe VIP’s ID is required. There are two options:
1. Government ID: Driver's license, national identity card, passport, or birth certificate. The ID must include the VIP's name and date of birth or name and photo.
2. Non-Government IDs: Student card, library card, refugee card, employment verification, diploma, or loyalty card.
All IDs must include the VIP's name, and at least one of the two IDs must include the VIP's date of birth and/or photo.

A signed LOA is required in some cases.
LinkedIn - Trademark or copyrightTrademark - Client's logo or client's nameThe vendor may require a trademark registration document and a signed LOA in some cases.
LinkedIn - VIPVIP's name and photoThe vendor may require a trademark registration document and a signed LOA in some cases.
Paste SitesSensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets
- Source code
- Documents
The vendor may require a trademark registration document and a signed LOA in some cases.
PastebinSensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets, source code, documents
The vendor may require a trademark registration document and a signed LOA in some cases.
PinterestTrademark - Client's logo or client's nameThe vendor may require a trademark registration document and a signed LOA in some cases.
RedditTrademark - Client's logo or client's nameThe vendor may require a trademark registration document and a signed LOA in some cases.
Scribd - AccountTrademark - Client's logo or client's nameThe vendor may require a trademark registration document and a signed LOA in some cases.
Scribd - PostTrademark - Client's logo or client's name
Sensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets
- Source code
- Documents
The vendor may require a trademark registration document and a signed LOA in some cases.
StudylibTrademark - Client's logo or client's name
Sensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets
- Source code
- Documents
The vendor may require a trademark registration document and a signed LOA in some cases.
TelegramTrademark Client's logo AND Client's name

Telegram policy protects the content of messages inside a group or channel, so those are not sufficient proof of abuse.
Global trademarks and a signed LOA are required in some cases
TikTokTrademark - Client's logo or client's nameThe vendor requires a trademark registration document and a signed LOA.
TumblrTrademark - Client's logo or client's nameThe team doesn’t have enough data on this type of case to determine which documents are needed.
Twitter - Trademark or copyrightTrademark - Client's logo or client's name

Specific Tweets are not supported according to Twitter policy.
The vendor requires a trademark registration document and a signed LOA.
Twitter - VIPVIP's name and photoThe vendor requires the VIP's valid government-issued photo ID (driver’s license/passport) and a signed LOA.
VKTrademark - Client's logo or client's nameA trademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
VeohTrademark - Client's logo or client's nameA trademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
VimeoTrademark - Client's logo or client's nameTrademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
VirusTotalTrademark - Client's logo or client's name
Sensitive information about the client:
- Access credentials (passwords, emails, BIN number, etc.)
- Leaked secrets
- Source code
- Documents
Trademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
WeiboTrademark - Client's logo or client's nameTrademark registration document is mandatory. A signed LOA may be required by the vendor in some cases.
YouTubeTrademark - Client's logo or client's nameThe vendor requires a trademark registration document and a signed LOA.

Requirements for Phishing (website and domain) takedown remediation

Takedown TypeVendor NameEvidence Needed?Trademark Needed?LOA Needed?Details
Phishing WebsiteAWSOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing WebsiteCloudflareOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing WebsiteDigital OceanOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing WebsiteGoDaddyThe vendor may require a signed LOA in some cases
Phishing DomainGoDaddyA phishing email that was sent by the reported email address.The full email headers and email content that sent by the reported domain.
The vendor may require a signed LOA in some cases.
Phishing WebsiteGoogleThe vendor requires a trademark registration document and a signed LOA.
Phishing DomainGoogleA phishing email was sent by the reported email address.The full email headers and email content sent from the reported domain.
The vendor requires a signed LOA.
Phishing WebsiteHostingerOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing WebsiteMicrosoftThe vendor requires a trademark registration document and a signed LOA.
Phishing WebsiteNamecheapOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing DomainNamecheapA phishing email that was sent by the reported email address.The full email headers and email content sent from the reported domain.
The vendor may require a signed LOA in some cases.
Phishing WebsiteName.comOptionalThe vendor may require a trademark registration document and a signed LOA in some cases.
Phishing WebsiteNamesiloThe vendor may require a trademark registration document and a signed LOA in some cases.

Request removal of a suspicious domain

To take down a domain, the registrars demand very specific evidence of malicious activity. This section shows you how!

Evidence can be uploaded in TXT, MSG, EML, or MBOX formats. Virus scans can be uploaded in PDF or TXT formats.

To request a takedown of a suspicious domain, the user must supply the original phishing email, sent from the suspicious domain, complete with the email headers (not simply a screenshot).

The header information provides the digital trail of the email and describes how the email passed from its origin to the user's mailbox. This serves the following purposes:

  • Validate the legitimacy of the email (headers are very difficult to falsify).
  • Provide some insight into if the email came from the domain listed or if it was spoofed.

Follow the instructions in the following sections to prepare evidence for uploading to the remediation request.

If proper evidence cannot be produced, see what other options are available at Additional Monitoring and Protection Steps.

To extract email headers from Gmail:

  1. In Gmail, open the email message for which you want to extract the header.
  2. In the top-right of the message, click More, then select Show original.
    temporary placeholder
    A page with the email headers is displayed in a new tab or window:
    temporary placeholder
  3. Click Copy to clipboard (or highlight and copy everything), then paste into a searchable text editor.
  4. Search (Ctrl-F) to ensure that the phishing domain is located in the pasted content.
  5. Attach the pasted content to the takedown request as TXT, MSG, EML, or MBOX.
    Alternatively, click Download Original, and upload the downloaded EML file.

To extract email headers from Outlook:

  1. Double-click the email message so it displays in a full window.

  2. Display the Properties dialog in either of these ways:

    • From the email window, choose File > Properties.
    • From the email window, from the Tags section, click the small down-arrow:
      temporary placeholder

    The Properties dialog is displayed:
    temporary placeholder

  3. Highlight, copy and, paste everything from the Internet headers section into a searchable text editor.

  4. Search (Ctrl-F) to ensure that the phishing domain is located in the pasted content.

  5. Attach the pasted content to the takedown request as TXT, MSG, EML, or MBOX.

To extract email headers from Apple Mail:

  1. Open the email message in the macOS or OS X Mail reading pane or its window.
  2. Choose View > Message > All Headers.
    The email header is displayed:
    C:\a9cf9f93a8ce6c439648dd4b6b362401
  3. Highlight, copy and, paste everything from the Internet headers section into a searchable text editor.
  4. Search to ensure that the phishing domain is located in the pasted content.
  5. Attach the pasted content to the takedown request as TXT, MSG, EML, or MBOX.

To create a malware scan with VirusTotal:

  1. Copy the domain name that you want to scan.

  2. Visit https://www.virustotal.com/

  3. Select the Search tab and paste the domain name: Graphical user interface, application, Teams  Description automatically generated
    The domain scan is displayed, in which  you can verify if there is malicious activity:

    Graphical user interface, application, Teams  Description automatically generated

  4. Copy and paste the URL of the page, then upload that URL as evidence as a PDF or TXT file.

    Graphical user interface, application, Teams  Description automatically generated

To create a malware scan with URLscan.io:

  1. Copy the domain name you want to scan.

  2. Visit https://urlscan.io/

  3. Click Search and paste the domain name:

    Graphical user interface, text, application, website  Description automatically generated

The domain scan is displayed, in which  you can verify if there is malicious activity:

1
![urlscan.io on Twitter: "Taking a first stab at creating a versatile API for returning maliciousness-verdicts for scanned pages. This probably won't be the final form, so maybe don't rush to using the](/threat-command/images/Imported/tutorial-domain-malware-scan-img0005.png)
  1. Copy and paste the URL of the page, then upload that URL as evidence as a PDF or TXT file.

Graphical user interface, text  Description automatically generated