logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.23.1

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland 🇫🇮

Status

Algorithm v2.23.1

Tool profile

Scanner iScanner

Scanner iScanner appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.

Back to all statistics
Forensic verdict

Mixed signal

Based on 4 appearances across the HTPBE? corpus.

Modification rate
0%-48pp below baseline
Corpus baseline: 48%
Total appearances
4
0.10% of corpus
Modification rate
0%
-48pp below baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How Scanner iScanner shows up in HTPBE? corpus

Scanner iScanner is one of the PDF-handling tools surfaced in the HTPBE? corpus. Scanner iScanner appears predominantly as the original Creator (100% of its occurrences) — i.e. on documents that started life inside Scanner iScanner rather than passing through it as a downstream re-saver.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Scanner iScanner appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

On documents where Scanner iScanner acts as Creator, 0% carry modification markers; on documents where it acts as Producer, 0% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against Scanner iScanner or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Scanner iScanner appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

Role in the workflow

How Scanner iScanner shows up in metadata

Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.

CAs Creator · 100%
As Producer · 0%P
CAs Creator
  • Usage
    4
  • Modification rate
    0%
  • Avg file size
    1.8 MB
PAs Producer
  • Usage
    0
  • Modification rate
    0%

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the bytes — and is the field that gets overwritten when a PDF is opened, edited, and saved by a downstream tool.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Name fingerprints

Also goes by

Different version strings and spellings observed for Scanner iScanner in the wild. All are merged into the same canonical profile.

iScannerFreeApp75.0%
iScannerFree25.0%

Why variants matter

The same tool publishes itself under 2 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.

Most common
iScannerFreeApp
75.0% of appearances
Variant spread
2 distinct strings
Long-tail share: 25.0%
Observed range
24 Feb 2026 → 9 Apr 2026

Related profiles

Tools you’ll see next to Scanner iScanner

Other tools that frequently share metadata with Scanner iScanner in the same documents. Each card links to its own forensic profile.

P100% co-occurrence
iOS Print to PDF
Appearances347
Mod rate68%

Long tail

Notable observations

Smaller cuts of the Scanner iScanner corpus — useful context, but treat each row as a single data point rather than a strong signal.

Pages parsed
4
Oldest observed
24 Feb 2026 — 3 months ago

Secure your workflow

Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.

Start free — close the structural fraud gapSee pricing
Read API docs →