Rollback and recovery
Whether you can put the previous version back, and how long that takes.
Learn
A check runs from the street. It sees the front of the building. These nine items are inside, and no honest scan of a public address can report on them. Every one of them gets a page here that tells you how to check it yourself.
Whether you can put the previous version back, and how long that takes.
Whether a failure in production reaches a human rather than sitting in a log nobody opens.
Whether sign in, password or code reset, and session expiry behave under real use.
Whether a script can hammer your forms, sign up loop, or paid endpoints without being slowed down.
Whether you can replace a leaked key quickly and know everywhere it is used.
Whether payment events are verified, replay safe, and matched to the right customer record.
Whether stored personal details are limited, deletable on request, and out of your logs.
Whether prompts, spend, and model output are bounded so one visitor cannot run up the bill.
Whether the row rules behind the app actually stop one signed in account reading another's rows.
Whether the certificate is close to expiring. A normal request proves the certificate is valid right now, and the runtime this check uses cannot read the expiry date from that request.
Whether a signed in account can reach another account's records by changing an id. ShipReady does not create accounts, sign in, or call your functions, so this cannot be answered from outside.
Run all sixteen groups on your published address and see the evidence behind every result.
ShipReady is not a penetration test or a security certification. No automated check can prove an application is secure.
Last updated September 20, 2026