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

Designer 6.5

Designer 6.5 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 3 appearances across the HTPBE? corpus.

Modification rate
100%+52pp above baseline
Corpus baseline: 48%
Total appearances
3
0.10% of corpus
Modification rate
100%
+52pp above baseline
Role split
67%C/33%P
Creator vs Producer share of appearances

Corpus profile

How Designer 6.5 shows up in HTPBE? corpus

Designer 6.5 is one of the PDF-handling tools surfaced in the HTPBE? corpus. Designer 6.5 splits its occurrences between Creator (67%) and Producer (33%) roles, meaning it sometimes originates documents and sometimes re-emits them after another tool created them.

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

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Designer 6.5 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 Designer 6.5 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 · 67%
As Producer · 33%P
CAs Creator
  • Usage
    2
  • Modification rate
    100%
  • Avg file size
    663 KB
PAs Producer
  • Usage
    1
  • Modification rate
    100%
  • Avg file size
    1.0 MB

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.

Distributions

What ships alongside Designer 6.5

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

PDF versions written

Most output is PDF 1.7 (100% of files where Designer 6.5 is the Producer).

PDF 1.7100.0%

Related profiles

Tools you’ll see next to Designer 6.5

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

P33% co-occurrence
macOS Print to PDF
Appearances747
Mod rate64%

Long tail

Notable observations

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

Embedded JavaScript
2

Files containing JavaScript code

Digitally signed
2

PDFs carrying at least one digital signature

Embedded files
2

PDFs with attached files inside

Pages parsed
13
Oldest observed
5 Sep 2024 — over 1 year 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 →