Asset integrity
Compare listed public build assets with their generated manifest using actual byte length, SHA-256 and content-type evidence.
Checking network test availability…
Compare this build’s listed public files
The build generates a manifest of its application bundles, fonts and five fixed public assets. This check reads those files through our signed diagnostic endpoint and compares the actual bytes, SHA-256 digest and reported content type.
No target URL is accepted. Files are not executed, and nothing runs until you press Start.
- Maximum assets
- 32
- Selected body limit
- 4 MiB total
- Per-request deadline
- 5 seconds
- Whole-run deadline
- 30 seconds, plus cleanup
Maximum 2 MiB per file. An 8 MiB admission allowance is reserved, not transferred. Quota charges include conservative manifest and response overhead; these charges are not traffic measurements.
What a matching result establishes
This compares bytes served from the static binding through the diagnostic route against a manifest supplied by the same build. It is not independent release authentication, a vulnerability scan or a guarantee that the serving origin is uncompromised.
It does not inspect your browser’s previously cached files, the ordinary public CDN route, protected admin assets, HTML, source maps, editorial illustrations or third-party resources. A changed build revision stops the run rather than mixing versions. Failures identify observed inconsistencies without guessing their cause.