Scanner de secrets collés

Comment l’utiliser

Paste the code or configuration you are about to share and run the scan. Matching lines are listed with the type of pattern that matched.

Ce que cet outil vérifie

Common secret shapes are matched by pattern: long random strings, known key prefixes, JWT structure, private key blocks and password fields inside connection strings. Matching is pattern-based only - no key is validated or sent to any service.

Comment lire le résultat

A match does not prove the string is a live secret, only that it looks like one. False positives are common: hashes, fixtures and long identifiers fit similar shapes. If you did publish a matched value, the correct response is to revoke and reissue it - deleting it from the text is not enough.

Exemples

Check an error log before sending it to support, or a configuration sample before adding it to documentation.

Cas d’usage

Useful for developers, support teams and anyone sharing snippets.

Erreurs fréquentes

The critical mistake is reverting the commit after pushing a secret: the value remains in history and probably in clones. The second is treating an empty result as assurance - a pattern-based scanner cannot see a format it does not know.

Les limites de cet outil

The tool sees only what you paste. It does not scan your repository, environment variables, commit history or server configuration. An empty result means "no known pattern found in this text", not "no leak".

Confidentialité et traitement des données

Text is discarded after the scan; only an anonymised run record is kept. Even so, the safest habit is never to paste a live production secret into any online tool.