SealedShipHome

Ship it sealed.

Is your vibe-coded app leaking?

Paste your URL. We’ll tell you what actually matters, skip the noise, and write a fix prompt your coding agent can paste straight in.

Built for people shipping with

LovableCursorBoltv0VercelReplit

How it works

Four steps. Then you ship it sealed.

You stay in the tools you already use. We write the brief. Your coding agent does the editing.

  1. 1

    Show it’s yours

    Tick a box, then add a DNS record or a tiny file. That’s how we know we’re allowed to look. We won’t scan a site you don’t control.

  2. 2

    We take a careful look

    Headers, DNS, email settings, and public files. The ordinary checks that catch real leaks. No exploit theatre, and we don’t try to break the site.

  3. 3

    You get a short list

    What matters, what doesn’t, and a prompt you can paste into Lovable, Cursor, Bolt, or whichever agent you already build with.

  4. 4

    We look again

    After your agent ships the fix, a re-scan shows the seam is actually closed. You get proof, not a hopeful shrug.

Sample report

A report that sounds like a person

This is the kind of site we see: built fast, a couple of things that actually matter, and a few that don’t. The free view unlocks one prompt. The rest wait behind the Fix Pack.

https://kindredkit.app

Sample
41out of 100

Sample scan · 12 Nov 2026

Needs a proper look

2 serious, 6 minor

A realistic sample, drawn from issues found on a real founder site. The domain and names here are fictional.

2 serious6 minor1 prompt unlocked
Fix this weekIncluded free

Your source code is downloadable

The site is publishing its Git folder. Anyone can download the project, including a short-lived GitHub token that was sitting in .git/config.

Why it matters

A token like that can read or change private repositories until it’s revoked. Old commits often hide other secrets too: API keys, passwords, the odd .env file someone committed on a Friday.

What we noticed

Opening /.git/HEAD returned the repository. /.git/config included a GitHub token (shown here as ghp_••••). Treat that token as public.

Fix prompt for your AI agent

Paste this into Lovable, Cursor, Bolt, or your agent.

You are fixing one security issue. Do not refactor, restyle, or change anything else.

Problem
The live site is serving the .git directory. Anyone can download the repository, and .git/config contains a GitHub token. Treat that token as already public.

What to do
1. Make sure the deployed site does not contain a .git folder. It must not be in public/, the static export, or the files uploaded to the host. Add .git to any deploy ignore list.
2. Block requests whose path is /.git or starts with /.git/. Respond with 404, not 403, so the path does not confirm that git is there. Use the host this project actually deploys to:
   - Vercel: a redirect or middleware matcher.
   - Netlify: _redirects or a netlify.toml edge rule.
   - nginx: location ~ /\.git { return 404; }
   - Cloudflare: a custom rule on the URI path.
   Add the one that matches this project. Do not add all of them.
3. Revoke the GitHub token. In GitHub: Settings → Developer settings → Personal access tokens. Delete the one that was in .git/config. Create a replacement only if a deploy still needs it, and store it in the host's secret manager, never in the repo.
4. Search git history for other secrets (API keys, private keys, .env files) and rotate anything you find.
5. Check the fix. https://YOUR_DOMAIN/.git/HEAD and https://YOUR_DOMAIN/.git/config must both return 404.

Done when both URLs 404 and the leaked token is revoked.
Fix this week

Anyone can send email that looks like you

The domain doesn’t say who is allowed to send email as you. There’s no SPF record, and DMARC is set to p=none, which means “please don’t do anything about fakes.”

Why it matters

Customers, investors, and app stores can be shown mail that looks like you sent it. Password resets and invoices are the usual targets. This is a domain setting, not a bug in the app’s code, and it’s one of the fixes that matters most.

What we noticed

A controlled proof message, sent only to a mailbox the owner controls, was accepted as if it came from [email protected]. Nothing was sent to customers. DMARC was p=none. No SPF record was published.

Fix prompt for your AI agent

The free scan includes one prompt. This one is in the Fix Pack.

Showing 2 of 8. The rest of the sample, including the quiet “probably fine” ones, is on the full report.

Read the full sample

Prices on this report follow the SealedShip A list.

Pricing

Start free. Seal what actually matters.

Prices in pounds. No retainer hiding in the small print. Paid plans aren’t charging cards yet — if you tap one, we’ll email you first.

Free scan

£0per site

  • A score, in plain English
  • How many issues, grouped by what matters
  • One fix prompt, ready to paste
  • Domain check before anything runs

Most people start here

Fix Pack

£29one-off, one site

  • Every fix prompt, not just the first
  • Written for your coding agent
  • One re-scan to confirm the fixes landed
  • Yours to keep

Stay covered

Monitor

£19per site, each month

  • A fresh scan every week
  • A note when a new deploy changes the picture
  • New fix prompts when something new shows up
  • A small “sealed by” badge for your site
Sealed by SealedShip

For agencies and freelancers

Studio

£99each month

  • 10 sites included
  • White-label reports you can send to clients
  • Everything in Monitor, for the whole set
  • One login for the studio, not ten

Yearly prices are 10 months for 12. Two months free. The free scan and the Fix Pack don’t change with the toggle.

FAQ

Questions, answered without the jargon

Ship it sealed.

A website, an email, and a tick to say you’re allowed to test it. We’ll show you the domain check straight after.

Get my free scan

SealedShip