File scanner
Upload almost any file — executables, documents, Android packages, archives, images or unknown formats. Content is identified from its bytes, not its extension.
Upload a file →Analyze files, websites and downloads with multiple security engines. Detect malware, phishing, suspicious behavior and potential threats.
One scan. Multiple layers of protection.
Scan Me runs format-aware inspection before it asks any vendor for an opinion. The report separates what was observed from what an engine concluded, so you can see the evidence behind a verdict.
Every report includes hashes, detected type, engine-by-engine status, static findings, YARA matches and a scan timeline. Export it as JSON or PDF for your own records.
How the analysis worksStart with the mode that matches what you have. All three produce the same report format.
Upload almost any file — executables, documents, Android packages, archives, images or unknown formats. Content is identified from its bytes, not its extension.
Upload a file →Inspect a website for phishing patterns, dangerous redirects, TLS problems, hidden frames and known-bad reputation before you open it.
Check a website →Paste a direct download link. Scan Me fetches it through an isolated, SSRF-protected fetcher, hashes it, then runs the same file analysis pipeline.
Try URL File →Analysis runs in a background worker so the interface never blocks on a slow provider.
Upload a file, paste a URL, or provide a direct download link.
Content-type identification and SHA-256, SHA-1 and MD5 are calculated server-side.
Static inspection, YARA, local antivirus, URL inspection and threat intelligence.
Every engine and check is listed with its real status, detection name and timing.
A detection from one layer is never presented as a result from another. The report names the source of every claim.
Byte signatures, structural rules, entropy scoring and filename deception run in-house and produce their own verdict, independent of any external API.
PE headers and sections, PDF embedded JavaScript and launch actions, APK permissions and certificates, archive contents, SVG scripts, Office macros, entropy and strings.
When VirusTotal or MetaDefender Cloud is connected, their results are mapped onto a catalogue of 70+ named engines. Engines without a result are never reported as clean.
Rule-based matching for webshells, script downloaders, packed binaries, ransomware notes and credential theft patterns, using the bundled rule set.
An independent scan with ClamAV through clamd or the clamscan CLI, separate from any cloud provider.
Redirect chains, TLS certificate validity, DNS records, hidden iframes, cross-origin password forms and obfuscated JavaScript.
Google Safe Browsing, URLhaus, PhishTank, hash reputation and RDAP domain-age checks when those integrations are configured.
The vendor catalogue is fixed; integrations are not. This list is read live from the API, so it reflects the keys and local tools this deployment really has.
Reading provider availability from the API…
See the vendor listIf an engine is not configured, it is listed as not available. If a scan could not run, the report says so and the verdict becomes inconclusive.
Uploads are stored under random keys outside any web root. URL fetching blocks loopback, private, reserved and cloud metadata addresses on every redirect hop.
A clean result only means nothing was detected by the checks that ran. Scan Me states that caveat on every report instead of promising safety.
Local analysis works without any API key. Paid and free-tier providers are optional adapters that can be enabled, disabled or left unconfigured.
Straight answers about coverage, retention and what a result can and cannot tell you.
Run the file, URL or download through Scan Me and read the evidence before you decide.