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.49.0

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · [email protected] · Made in Finland

Status

Algorithm v2.49.0

Back to FAQ
FAQ

Why doesn’t HTPBE? show every signal it found in my file?

Because HTPBE? exists to catch forged documents. When our analysis finds several signals in a file, we do not list all of them. Showing the full set would make it easier for someone preparing a forgery to learn how to bypass the checks, and the integrity of the analysis comes first.

What you see on the result page

  • One named signal. The result shows a single finding by its public name, with a link to what that name means.
  • A count of the rest. A label such as ‘+1 other’ tells you that the file tripped more than one signal. The remaining signals are not named.
  • The verdict. Intact, Modified or Inconclusive, with its confidence level. The verdict is reached from everything the analysis found, not only from the signal that is displayed.

Why a full list would work against the check

A forger can upload the same document again and again, change it a little each time and read the result. If every upload returned the complete list of what the file tripped, the list would work as a set of instructions for what to remove next. Showing one signal and a count still tells an honest reader that the file was changed and gives them something concrete to ask about, without giving a forger a checklist.

The same reasoning is why the public descriptions of our checks say what we catch and never how we detect it.

What this means for you

  • The displayed signal is real. It is a finding on your file, not a sample or an example. Its page explains what it means.
  • An undisplayed signal is not an error. A count above zero does not mean something was hidden from you by mistake, and it does not mean the verdict is uncertain.
  • You can still ask about a result. If you think a result is wrong, open the check in your dashboard and use Report an Incorrect Result. The file is re-analysed and reviewed manually.

What to do with a Modified result

Treat the verdict as a fact about the file: it was changed after it was created. If the document should have come from an institution, ask the issuer for an untouched digital original. How to read each verdict is covered in How should I interpret PDF analysis results? and the usual harmless reasons for a Modified result are listed in Why does my PDF show as modified even though I didn’t edit it?

← Previous

Does HTPBE? verify someone’s identity, or that a document is valid against the issuer?

Next →

What is HTPBE?, and what does it do?

Related questions

Keep reading

3 answers

Basics & scope

HTPBE? (Has This PDF Been Edited?) detects whether a PDF was modified after it was created. Upload a file of up to 10 MB and get a verdict – Intact, Modified or Inconclusive – with the findings behind it.

Read the full answer

HTPBE? stands for ‘Has This PDF Been Edited?’ Pronounce it letter by letter: H-T-P-B-E.

Read the full answer

KYC platforms confirm who a person is. HTPBE? checks whether a specific PDF file was modified after it was generated. An identity can be real while a supporting document has been edited, so the two checks complement each other.

Read the full answer

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 →