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

IronPdf

IronPdf 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 13 appearances across the HTPBE? corpus.

Modification rate
46%-2pp below baseline
Corpus baseline: 48%
Total appearances
13
0.10% of corpus
Modification rate
46%
-2pp below baseline
Role split
54%C/46%P
Creator vs Producer share of appearances

Corpus profile

How IronPdf shows up in HTPBE? corpus

IronPdf is one of the PDF-handling tools surfaced in the HTPBE? corpus. IronPdf splits its occurrences between Creator (54%) and Producer (46%) 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 IronPdf 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 IronPdf acts as Creator, 43% carry modification markers; on documents where it acts as Producer, 50% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against IronPdf or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when IronPdf 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 IronPdf 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 · 54%
As Producer · 46%P
CAs Creator
  • Usage
    7
  • Modification rate
    43%
  • Avg file size
    903 KB
PAs Producer
  • Usage
    6
  • Modification rate
    50%
  • Avg file size
    39 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 IronPdf in the wild. All are merged into the same canonical profile.

IronPdf.Core (2019.7.0.0)76.9%
IronPdf15.4%
IronPdf v2024.2.27.7%

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
IronPdf.Core (2019.7.0.0)
76.9% of appearances
Variant spread
3 distinct strings
Long-tail share: 23.1%
Observed range
4 Oct 2024 → 23 Mar 2026

Distributions

What ships alongside IronPdf

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

PDF versions written

Most output is PDF 1.4 (100% of files where IronPdf is the Producer).

PDF 1.4100.0%

Related profiles

Tools you’ll see next to IronPdf

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

P8% co-occurrence
PDFium
Appearances962
Mod rate25%

Long tail

Notable observations

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

Pages parsed
13
Oldest observed
4 Oct 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 →