SealedShipHome

Ship it sealed.

Find the security holes in your AI-built site or app before someone else does.

Free scan, plain-English results, and fix prompts you paste straight into your coding agent.

kindredkit.app

Sample

41

out of 100 · Needs a proper look

2 serious6 minor

Fix this week

Your source code is downloadable

The .git folder is public, and a GitHub token came with it. There’s a prompt ready to paste.

Open the sample report

I'm Max. An AI security scan of my own site found my .git folder public with a GitHub token inside, and anyone could send email as my domain. So I built SealedShip for founders like me.

Built for people shipping with

LovableCursorBoltv0VercelReplit

How it works

Four steps. Then you ship it sealed.

  1. 1

    Show it’s yours

    Tick the box, then add a DNS record or a tiny file.

  2. 2

    We look

    Headers, DNS, email settings, and public files.

  3. 3

    You get a prompt

    Paste it into the agent that built the site.

  4. 4

    We look again

    A re-scan shows the fix actually landed.

Sample report

One prompt free. The rest wait.

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

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.

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

Pricing

Start free. Seal what actually matters.

Payments by Stripe. Reports delivered by email within 24 hours.

Free scan

£0per site

  • Score and issue counts
  • One fix prompt
  • Domain check first

Most people start here

Fix Pack

£29one-off, one site

  • Every fix prompt
  • One re-scan after the fix
  • Emailed within 24 hours

Want it watched? Monitor re-scans monthly, £19/mo — .

FAQ

Questions, answered without the jargon

Ship it sealed.

Add your site, confirm you can test it, and we’ll show the domain check.

Get my free scan