User guides
How to connect an app and use Tenty, and what each check looks for, why it matters, how to fix a finding and how to see it yourself
Get started
Security scans
Uptime
Check reference
What each check looks for, grouped by where the problem lives
Keys and secrets
- Leaked secret keysA secret key that ships in a page or a script file belongs to everyone who opens the site.
- Leaked environment variablesVariables with a public prefix are copied into the page at build time.
- Keys that are public on purposeSome keys are made to sit in a page. They stay safe when the provider side is set up for it.
- Supabase keys and tablesSupabase apps put a public key in the page on purpose. Row level security is the lock that makes that safe.
- AI endpoints anyone can callAn endpoint that forwards prompts to an AI provider can run up your bill when strangers can call it.
Data and backends
- Firebase rulesFirebase databases protect their data with rules. The Realtime Database and Firestore web addresses ship in your page, so the rules are the only protection the data has.
- Open storage bucketsA storage bucket holds the files of your app: uploads, images, exports. When the bucket lists its files to anyone, every file name is visible and every file can be downloaded.
- Data inside the pageData embedded in a page for the app's own use is readable by every visitor.
- GraphQL endpointsA GraphQL endpoint can describe its whole schema to any caller. This feature is called introspection, and it is meant for development tools.
- API descriptionsAn API description, usually an OpenAPI or Swagger file, lists every endpoint of your app and says which ones need a credential. The server has to enforce what the file says.
- CORSCORS decides which other sites may read answers from your server.
Exposed files and tools
- Exposed filesFiles that belong on a developer machine sometimes end up in the public folder of a site.
- Exposed source mapsA source map is the key that turns a minified script back into your original code.
- Exposed admin and debug toolsAdmin consoles, debug pages and API explorers belong behind a login or on a private network.
- Development mode in productionDevelopment servers and debug pages show more than a live site should.
- Basic Auth over httpBasic Auth sends the password with every request, so the connection has to be encrypted.
Headers, scripts and certificates
- Web basics and security headersResponse headers tell the browser how to treat your site. A few lines add a lot of protection.
- Session cookiesThree flags decide who can read a login cookie.
- HTTPS and certificatesHTTPS protects every request between your visitor and your site, and a valid certificate is what makes browsers trust it.
- Third-party scriptsA script from another site runs with full access to your page.
- Vulnerable librariesLibraries with a publicly known hole get found by searching for their version.
Domain, DNS and email
- Email recordsSPF, DKIM and DMARC records tell receivers which mail really comes from your domain.
- Domain expiryA domain that lapses takes the site and its email down, and someone else can register it.
- Subdomain and script host takeoverA name that points at a service nobody runs any more can be claimed by anyone.
- Browser warning listsChrome, Firefox and Safari check every address against Google Safe Browsing before they open it.
- Leftover hosts and addressesCode that points at a staging, internal or local host tells attackers where to look.
- Servers outside the CDNA CDN protects a site only when every name goes through it.
Mobile apps
Site basics
- Privacy policy and termsVisitors and buyers need to find the rules of the site.
- Sensitive paths in robots.txtA robots.txt lists paths for search engines, and every visitor can read it.
- security.txtA security.txt file tells researchers where to report a problem.
- What Tenty detects about your stackTenty names the services your app is built on and shows them as facts.