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

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

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.44.7

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.44.7

Tool profile

Scanner Lexmark

Scanner Lexmark 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 this tool’s share of the HTPBE? corpus.

Modification rate
33%-16pp below baseline
Corpus baseline: 49%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
33%
-16pp below baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How Scanner Lexmark shows up in HTPBE? corpus

Scanner Lexmark is one of the PDF-handling tools surfaced in the HTPBE? corpus. Scanner Lexmark appears predominantly as the Producer (100% of its occurrences) — i.e. on documents whose original Creator was a different application and that subsequently passed through Scanner Lexmark on the way out.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Scanner Lexmark 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 Lexmark acts as Creator, 0% carry modification markers; on documents where it acts as Producer, 33% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against Scanner Lexmark or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Scanner Lexmark 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 Lexmark 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 · 0%
As Producer · 100%P
CAs Creator
  • Share of appearances
    0%
  • Modification rate
    0%
PAs Producer
  • Share of appearances
    100%
  • Modification rate
    33%
  • Avg file size
    415 KB

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 Lexmark in the wild. All are merged into the same canonical profile.

Lexmark MX511dhe33.3%
Lexmark XC434233.3%
Lexmark XM335033.3%

Why variants matter

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

Most common
Lexmark MX511dhe
33.3% of appearances
Variant spread
3 distinct strings
Long-tail share: 66.7%

Distributions

What ships alongside Scanner Lexmark

The PDF versions Scanner Lexmark writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.5 (100% of files where Scanner Lexmark is the Producer).

PDF 1.5100.0%

Related profiles

Tools you’ll see next to Scanner Lexmark

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

C100% co-occurrence
HardCopy
Corpus share0.02%
Mod rate50%

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.

Start Free – Close the Structural Fraud GapSee Pricing
Read API Docs →