Skip to content
Free security analysis

Is it safe? Let's find out.

Analyze files, websites and downloads with multiple security engines. Detect malware, phishing, suspicious behavior and potential threats.

300 MB Maximum file size, enforced server-side
70+ engines Vendor catalogue with honest status per engine
4 layers Static, YARA, antivirus and threat intelligence

One scan. Multiple layers of protection.

Start a scan Max 300 MB
Drop a file here, or browse
Any file type up to 300 MB · executables, documents, archives, images

Files are stored in an isolated object store, never served back to browsers, and removed after the configured retention window.

What you get

A technical answer, not just a green tick

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 works
  • File signatures and type-versus-extension mismatches
  • SHA-256, SHA-1 and MD5 with hash reputation lookup
  • PE sections, imports, entropy and signature status
  • PDF JavaScript, launch actions and appended payloads
  • APK permissions, trackers, certificates and native libraries
  • Redirects, TLS, DNS, phishing forms and hidden frames
Scanning modes

Three ways to check something

Start with the mode that matches what you have. All three produce the same report format.

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 →

URL scanner

Inspect a website for phishing patterns, dangerous redirects, TLS problems, hidden frames and known-bad reputation before you open it.

Check a website →

URL File Experimental

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 →
Process

From submission to report

Analysis runs in a background worker so the interface never blocks on a slow provider.

Submit

Upload a file, paste a URL, or provide a direct download link.

Identify and hash

Content-type identification and SHA-256, SHA-1 and MD5 are calculated server-side.

Analyse in layers

Static inspection, YARA, local antivirus, URL inspection and threat intelligence.

Read the report

Every engine and check is listed with its real status, detection name and timing.

Detection layers

Independent checks, reported separately

A detection from one layer is never presented as a result from another. The report names the source of every claim.

Scan Me detection engine

Byte signatures, structural rules, entropy scoring and filename deception run in-house and produce their own verdict, independent of any external API.

Static analysis

PE headers and sections, PDF embedded JavaScript and launch actions, APK permissions and certificates, archive contents, SVG scripts, Office macros, entropy and strings.

Multi-engine antivirus

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.

YARA rules

Rule-based matching for webshells, script downloaders, packed binaries, ransomware notes and credential theft patterns, using the bundled rule set.

Local ClamAV

An independent scan with ClamAV through clamd or the clamscan CLI, separate from any cloud provider.

URL inspection

Redirect chains, TLS certificate validity, DNS records, hidden iframes, cross-origin password forms and obfuscated JavaScript.

Threat intelligence

Google Safe Browsing, URLhaus, PhishTank, hash reputation and RDAP domain-age checks when those integrations are configured.

Engine coverage

What is actually running here

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.

— Named engines in the catalogue
— Integrations configured right now

Reading provider availability from the API…

See the vendor list
Loading provider status…
How Scan Me behaves

Principles that shape every report

No invented results

If 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.

Isolation by default

Uploads are stored under random keys outside any web root. URL fetching blocks loopback, private, reserved and cloud metadata addresses on every redirect hop.

Honest limits

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.

Free-first architecture

Local analysis works without any API key. Paid and free-tier providers are optional adapters that can be enabled, disabled or left unconfigured.

Questions

Frequently asked

Straight answers about coverage, retention and what a result can and cannot tell you.

Is Scan Me really free to use?
Yes. Static analysis, YARA matching and ClamAV run on your own infrastructure at no cost. Multi-engine and reputation integrations depend on the API keys the operator configures, and free tiers have quotas. Nothing is charged by Scan Me itself.
Why do some engines say 'not available'?
A vendor name in the catalogue does not mean the engine is wired up in every deployment. If no multi-engine API key is configured, those vendors are shown as not available and are excluded from the detection ratio — they are never counted as undetected.
Does a clean report mean the file is safe?
No. A scan can only report what its engines and checks found. Zero detections narrows the risk but cannot prove safety, which is why every clean report carries that caveat.
How long are files kept?
Samples are stored in isolated object storage and removed by the retention job after the configured window (48 hours by default). Files are never served back to browsers. Reports retain hashes and analysis results, not the sample itself.
What exactly is URL File?
An experimental mode where you give Scan Me a direct download URL instead of uploading a file. The fetcher validates every resolved address and redirect, enforces the 300 MB cap while streaming, hashes the download, and then runs the normal file pipeline.
What is the maximum file size?
300 MB by default, enforced while streaming on the server — not only in the browser. URL File downloads have the same cap.

You don't have to open it to find out.

Run the file, URL or download through Scan Me and read the evidence before you decide.

Start a scan