# Result Screen and Reports

The Virusis result screen brings several data layers together in one place.

## 1. Meta area

The top of the result page shows core sample information:

* scan type
* submission name or target
* checksum selector
* summary fields such as file size

In file flows, checksums are easy to review and copy from the result interface.

## 2. Score cards

The public result experience highlights score-style summaries such as:

* overall risk
* analysis-based scoring
* AI-assisted context when available

## 3. Engine result cards

Each card typically includes:

* engine name
* detection and category information
* engine image
* rank or ranking impact

This model works well for streaming because cards can update independently.

## 4. Analysis tabs

Two major analysis tabs stand out on the result screen:

* threat intelligence
* static analysis

These tabs sit on top of the primary engine results as a second interpretation layer.

## 5. Reporting and sharing

The application supports these outputs:

* PDF export
* share link
* QR code
* social sharing helpers

PDF is the primary export format described in this help center.

## What is included in the PDF report?

The PDF export experience typically includes:

* submission name
* created timestamp
* checksum details
* size
* engine result rows
* score and summary fields

So the export layer is not just taking a screenshot. It transforms structured scan data into a report format.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.virusis.com/malware-analysis/result-screen-and-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.