The LJF Forensics Archive is an offline, independently-verifiable copy of everything the deleted website lilyjayfoundation.com published — preserved so anyone can examine the open questions about the foundation from the primary source, rather than take anyone's word for it.
Why it exists
The Lily Jay Foundation is an Australian humanitarian fundraising project (#TeamGaza / #TeamSudan). Its website began deleting content after ABC News Verify published an investigation on 5 July 2026 reporting AI-generated and manipulated material in the foundation's charity videos and award images. (ABC News Verify, 5 Jul 2026)
This archive captured 1,754 pages and roughly 3,000 media files before they were removed. Every page is traceable to a dated snapshot in the Internet Archive's Wayback Machine, so the record can be independently confirmed.
What you can do here
- Search the deleted posts and site pages by keyword or snapshot date.
- Inspect every archived image and video in the media gallery.
- Add or read community evidence — pin notes, flag names, log reverse-image searches (on a computer), and corroborate others' findings.
What the findings prove — and what they don't
This archive states mechanical facts as facts — that a page existed on a given date, that a file is present, that an image appears on multiple posts — because those are directly verifiable. Everything else is framed as an open question or attributed to its source. The archive does not assert that the foundation committed fraud or that any specific image is fake.
Community evidence is unverified until reviewed. Anyone can add a note; contributions show as unverified until a moderator marks them verified. Corroboration counts how many people agree — it is a signal, not proof.
Reverse-image-search results are a signal, not a verdict. "No matches" or "matches a stock photo" is context for you to weigh, not a conclusion the archive draws for you.
Right of reply & corrections
If you represent the Lily Jay Foundation, or you believe anything here is inaccurate, corrections and a right of reply are welcome. Contact @Helvetic10 on X.
How to verify anything yourself
- Open the Wayback snapshot linked at the bottom of every archived page to confirm the original, dated capture.
- Reverse-image-search any photo (Google Lens, TinEye, Yandex, Bing) from its image page.
- Inspect content credentials — some images carry embedded provenance metadata (C2PA) you can read with public tools.
Content credentials (C2PA)
Some archived images carry an embedded C2PA content credential — a signed record, attached by the software that created or edited the file, describing how it was made. Where the archive detects one, the image page and gallery show a badge.
What a credential proves: if it carries the IPTC trainedAlgorithmicMedia assertion, the file itself declares that it was generated by an AI model. That is a mechanical fact about the file — verifiable in the bytes — not an opinion.
What it does not prove: credentials are easily stripped when an image is re-saved or re-uploaded, so their absence does not mean an image is authentic. A credential could in principle be added by anyone, though an assertion signed by a mainstream generator is authoritative. This archive reports a credential's presence; it does not independently re-verify the cryptographic signature.