Tearsheet
The short version
The homepage loads. A GET of https://cauldronlabs.io/ returned HTTP 200 in 205 milliseconds on this run. The document title was “Cauldron Labs | AI innovation and events, Kansas City.” The TLS certificate completed a valid handshake, with 71 days remaining and a not-after time of 2 February 2027, 02:37 UTC, which is 8:37 p.m. America/Chicago on 1 February 2027. Issuer: Google Trust Services, WE1. This is not an urgent certificate lapse.
A capped crawl of pages actually linked from the public site requested 13 URLs and did not record failing internal links. A configured list of older paths, though, did return 404, and the homepage plus a capped set of linked assets was about 5.0 MB. Those two points are the concrete issues worth writing down. Backup status, form delivery, and historical uptime were not measured, and are not claimed.
What was actually seen
| Check | Result, from this run only |
|---|---|
| Homepage | HTTP 200 in 205 ms. This is a single probe, not an uptime percentage. |
| TLS | Handshake valid. 71 days remaining as of this run. Not after 2027-02-02T02:37:03Z. |
| Current public pages checked | HTTP 200: /, /contact, /about, /writing, /news, /privacy, and /terms. |
| Paths that returned 404 | /services, /work, /process, and /faq, each confirmed with a direct GET. /day-2-care also returned 404. That last path is expected, because the Day 2 Care landing has not been published on cauldronlabs.io. |
| Navigation, as observed | The header uses homepage anchors for Work and Process (/#work and /#process), plus /news, /writing, /about, and a contact path at /contact. The four 404 paths above were not in that header, and they did not appear in the checker's list of discovered links. They look like retired or unused paths, not broken items in the current nav. Redirects would still help anyone with an old bookmark or an external link. |
| Internal crawl | 13 URLs requested, cap 40. No failing internal URLs recorded. External links were not requested. |
| Form endpoint | https://form.cauldronlabs.io/api/interest answered GET with HTTP 200. No form was submitted, so this cannot say whether a message would arrive in an inbox. |
| Security headers, observation only | Present: x-content-type-options (nosniff), referrer-policy (strict-origin-when-cross-origin). Missing: strict-transport-security, content-security-policy, permissions-policy, x-frame-options. Missing headers are not a proof of a vulnerability. |
| Page weight, cheap signal only | Homepage HTML about 58.2 KB. Homepage HTML plus a capped set of 20 linked assets about 5,152,753 bytes, or about 5.0 MB. This is not a Lighthouse score. The largest files in that cap were /assets/media/cauldron-loop-v5.mp4 (about 1.6 MB) and two Loop poster PNGs, about 647 KB and 683 KB. Mixed content: none recorded. A viewport tag was present. |
| Visible stack | The server header identified Cloudflare. Available updates were not looked up, and nothing was applied. |
What this does not say
- It does not say the site is down. The homepage and the current main pages that were requested returned 200.
- It does not invent an uptime percentage, a performance score, or a client result.
- It does not claim the contact form delivers mail. Only reachability was checked.
- It does not claim backups ran, or that a restore has been tested. Those cannot be seen from the public site.
- It does not treat missing security headers as a confirmed exploit.
Open questions for a human sign-off
- Should /services, /work, /process, and /faq redirect to the current pages or anchors, or stay as 404s on purpose?
- Is the homepage weight, especially the Loop video and poster PNGs, a problem worth fixing, or acceptable for this design?
- Which, if any, of the missing security headers should be set on this stack?
- None of those questions is a production change until Justin marks it.
A draft note, unsent
If this were a sheet for someone else's site, a short draft might go here, in Justin's voice, naming only the observations above. For this sample, there is no outbound letter, because the property is the studio's own site and there is no third party to write to. No email is sent from a Tearsheet until Justin says so.
Sign-off
I have reviewed this sheet against the 22 November 2026 log. It is accurate to the best of my knowledge, and it does not include figures we did not measure.
Signature: (pending) Justin Gardner
Date: