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
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.34.4

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.34.4

Tool profile

Edge

Edge 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
47%on baseline
Corpus baseline: 48%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
47%
on baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How Edge shows up in HTPBE? corpus

Edge is one of the PDF-handling tools surfaced in the HTPBE? corpus. Edge appears predominantly as the original Creator (100% of its occurrences) — i.e. on documents that started life inside Edge 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 Edge 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 Edge acts as Creator, 47% 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 Edge or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Edge 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 Edge 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
  • Share of appearances
    100%
  • Modification rate
    47%
  • Avg file size
    290 KB
PAs Producer
  • Share of appearances
    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 Edge in the wild. All are merged into the same canonical profile.

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.035.3%
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.023.5%
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 Edg/148.0.0.017.6%
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.011.8%
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 Edg/149.0.0.05.9%
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 Edg/146.0.0.05.9%

Why variants matter

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

Most common
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0
35.3% of appearances
Variant spread
6 distinct strings
Long-tail share: 64.7%
Observed range
29.07.2025 → 22.06.2026

Distributions

What ships alongside Edge

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

Common Producers when Edge is the Creator

Skia/PDF writes 76% of these files — that pairing is the Adobe-stack default for many institutional pipelines.

Skia/PDF76.5%
airSlate17.6%
macOS Print to PDF5.9%

Related profiles

Tools you’ll see next to Edge

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

P18% co-occurrence
airSlate
Corpus share0.6%
Mod rate13%
P6% co-occurrence
macOS Print to PDF
Corpus share3.5%
Mod rate64%

Long tail

Notable observations

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

Avg pages per document
1.8
Oldest observed
29.07.2025 — 12 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 →