SealedShipHome

Sample report

What “sealed” looks like on a real site

Two things worth fixing this week, six smaller ones, and one prompt you can copy right now. The others show you the shape of a locked prompt. Nothing here is a live scan of your site.

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.

Worth tidying

Browsers aren’t given the usual safety rules

The site doesn’t send the headers that tell a browser how to behave: don’t load it in a sneaky frame, don’t guess file types, and only talk to it over HTTPS.

Why it matters

Missing headers don’t mean someone is inside the app. They do make clickjacking, mixed content, and a few browser-side tricks easier than they need to be. They’re a small change with a quiet payoff.

What we noticed

The homepage response had none of: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, or Permissions-Policy.

Fix prompt for your AI agent

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

Worth tidying

Any certificate authority can mint a certificate for you

There’s no CAA record. That’s the DNS note that says which companies are allowed to issue HTTPS certificates for this domain.

Why it matters

If only one company should issue your certificates, say so. It won’t stop every mistake, but it closes an easy door for a lookalike certificate.

What we noticed

No CAA records were published on kindredkit.app.

Fix prompt for your AI agent

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

Worth tidying

Your DNS answers aren’t signed

DNSSEC is off. Visitors’ computers can’t check that the DNS answer really came from your domain’s name servers.

Why it matters

For a small app this is lower urgency than the Git folder or email settings. It’s still worth turning on at the registrar so a forged DNS answer is harder to pass off.

What we noticed

The domain has no DS record at the parent, so DNSSEC is not enabled.

Fix prompt for your AI agent

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

Probably fine

A Firebase config is sitting in the page

The JavaScript bundle includes a Firebase web config: an apiKey, a project id, and a few other fields. For Firebase, that config is meant to be public. It is not a secret password.

Why it matters

Other scanners love to flag this, and it sends founders into a panic. The thing that actually matters is the project’s security rules: who can read and write the database, storage, and auth. If those rules are tight, this finding is noise.

What we noticed

The client bundle includes a Firebase config for project kindredkit-prod. The apiKey is the public web key. We did not find a private service-account file.

Fix prompt for your AI agent

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

Worth tidying

A login cookie is missing two small flags

The session cookie is set without Secure and without HttpOnly. Secure means “only send this over HTTPS.” HttpOnly means “JavaScript on the page can’t read it.”

Why it matters

On a shared network, or if any script on the page is dodgy, that cookie is easier to pinch than it should be. It’s a one-line change in most frameworks.

What we noticed

The response set a cookie named session with no Secure flag and no HttpOnly flag.

Fix prompt for your AI agent

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

Worth tidying

The site announces which framework it runs

Responses include X-Powered-By: Next.js, and a bad address shows a detailed error page. That tells a curious person exactly which bugs to go and look up.

Why it matters

Hiding the version doesn’t fix a bug. It does stop you handing over a map. Turning the banner off is easy, and production error pages should be the friendly ones, not a stack trace.

What we noticed

The homepage sent X-Powered-By: Next.js. A request to /this-page-does-not-exist returned a framework error page with build details.

Fix prompt for your AI agent

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

Also checked, and fine

  • HTTPS is on, and the certificate is valid.
  • The homepage doesn’t list the files in its folders.
  • Common admin addresses we tried came back as not found.

Prices on this report follow the SealedShip A list.