Verify an export
Check that a PDF from isollet Plus is a genuine file made by isollet and that nothing in it has been edited since.
Only the original PDF file can be checked
Printouts, scans, screenshots, photos and PDFs re-saved in another app can't be checked. This page can't tell whether such a copy is genuine, so always ask for the original PDF file from isollet exactly as received (for older documents, also the .isollet-seal.json and .isollet-verify.json files that came with it).
Files never leave this device
Checks happen only inside this browser. Your files aren't sent anywhere.
Drop the files here
Drop the PDF file exactly as you received it. For older documents with a separate seal, also drop the files that came with it (names ending in .isollet-seal.json or .isollet-verify.json).
How to check
- Drop all the files that came with the PDF, and the PDF itself, into the box above.
- Check that the result is 'Passed'.
- Check that the 'Issue number' on the PDF cover matches the one in the result.
- For conversation and child records, check that the file fingerprint (SHA-256) and key ID (key_id) in the result match the values on the PDF cover.
- For monthly settlements and schedule records, check that the summary numbers in the result match the 'Server-checked summary' on the PDF cover.
Reading the results
What 'Passed' means
- Each message's sender signature is valid. If the content or send time changed even slightly, the signature would no longer match.
- Each message has a valid record (receipt) of when the isollet server received it.
- Message numbers run with no gaps and each message is chained to the one before, so no message was added or removed in between.
- Each locked message was opened and matches the text exactly.
What this check cannot tell you
- The cover, headers and footers of a PDF, and the body of child record PDFs, aren't compared automatically. Check those parts against what this page shows.
- In a PDF with manipulated fonts, the text on screen can differ from the real text. If in doubt, rely on what this page shows.
- This file can't show who actually used the device. Whether it can be used as evidence is for the court to decide.
- Go by 'received at' for times. 'Sent at' comes from the sender's device clock and may be inaccurate.
- In child records, 'redacted entries' (messages about another child) are checked only by number, and their content can't be seen. Whether they really are about another child can only be confirmed against the entire conversation.
- Documents made before November 6, 2026 have no seal file, and monthly settlements and schedule records made before November 8 have no summary.
If the result is 'Failed'
- The file may have been edited, messages may be missing, or other data may be mixed in. Each failed item says which message number is affected.
- Ask the person who gave you the file to export it again from the app, or compare it with the entire conversation exported by the other parent.
isollet server receipt keys (published)
Server receipts are checked against the public keys below. If a key not on this list was used, the check fails.
9ec2 1708 43f2 9bc6 6e4a 1d5f 0683 2acb
ed25519 SbRNhxdWNMALm83GZKuM7p69LOVA2FJuMf5RYMk7Gy4
since 2026-10-19 · in use
isollet seal keys (published)
Seals are checked against the public keys below.
Only the original PDF file can be checked. Printouts, scans and PDFs re-saved in another app can't be checked, so ask for the original file. For conversation and child records, you can still compare the file fingerprint (SHA-256) on the cover and the content by eye.
5978 85cb ed35 4411 3c6a 54ae 78a3 748f
ed25519 NK2OGYpJsc-O4u3RPakUqlCQSllrPsKCjUQJDVr14OQ
since 2026-11-07 · in use
Questions about a result: contact@isollet.com