Microsoft Reporting Services reads as a institutional generator — its modification rate sits at or below the corpus baseline, consistent with single-pass institutional output.
Back to all statisticsForensic verdictBased on 903 appearances across the HTPBE? corpus.
Corpus profile
Microsoft SQL Server Reporting Services (SSRS) is an enterprise reporting platform that emits PDFs server-side from parameterized report templates — common in healthcare, government, and large back-office workflows.
SSRS-produced PDFs are server-rendered institutional output. Low signal for tampering when SSRS is the sole Producer.
Role in the workflow
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.
Name fingerprints
Different version strings and spellings observed for Microsoft Reporting Services in the wild. All are merged into the same canonical profile.
Why variants matter
The same tool publishes itself under 10 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.
Distributions
The PDF versions Microsoft Reporting Services writes when acting as Producer, and the other tools that appear in the same documents.
Most output is PDF 1.7 (99% of files where Microsoft Reporting Services is the Producer).
Long tail
Smaller cuts of the Microsoft Reporting Services corpus — useful context, but treat each row as a single data point rather than a strong signal.
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.