# Supported Inputs ## Supported Input Types | Input | Typical use | Notes | | ----- | ----------------------------- | ----------------------------------------------------------------------- | | File | suspicious file review | best when teams need a full report with structure and detection context | | URL | website or link investigation | useful for phishing, destination review, and reputation checks | | IP | infrastructure lookups | useful when teams need quick context on an address or host | Each input type is presented through a consistent product flow so users can move from submission to review without learning a different interface each time. ## How analysis coverage is presented Virusis combines multiple analysis signals behind one result surface. Depending on the input type and environment, a report may include: * detection and verdict signals * risk-oriented score summaries * threat or reputation context * file-level inspection when relevant ## Extra Layer For File Analysis On top of general verdict signals, file submissions can also include: * file inspection details * risk scoring * contextual findings on the same report. --- # 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/supported-inputs-and-integrations.md?ask= ``` 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.