free tool

Free Secrets Scanning Tool

Repository scanners read your code. This free hardcoded secrets scanning tool checks what your live web application already serves to the internet. Penti's AI pentester works through your JavaScript assets, configuration paths, and public files, looks for exposed API keys, access tokens, and hardcoded credentials, and backs the result with an evidence log. Enter your company email and target URL to start.

empowering customers to close deals with Fortune 500 companies like:
/ what are hardcoded secrets
[ 01 / 14 ]

What are hardcoded secrets?

A hardcoded secret is a credential written straight into code, configuration, or client-side assets instead of being kept in a secrets manager. It works, it ships, and it stays readable to anyone who looks.
The secret types that leak most often:
  • API keys for payment, email, analytics, and AI services
  • Access tokens that carry the rights of the account behind them
  • Hardcoded credentials in scripts, deployment templates, and configuration files
  • Private keys and encryption keys that unlock servers and sign releases
  • Database credentials and connection strings
Exposure rarely takes an attack. A key placed in client-side code is open to interception, which is why Google tells developers to keep API keys out of client code. A backup file or a debug log stays in a public directory after a deploy. Development teams run repository scanners to detect hardcoded secrets in source code, and those scanners read the repository, not the pages your visitors load.
Whoever finds an exposed credential holds a working key to your systems and your customer records. MITRE ATT&CK notes that adversaries using valid accounts can move as a legitimate user and stay harder to detect, so a so a single leaked key leads to data breaches, security incidents, and exposed sensitive data long before anyone notices.
/ feature overview
[ 02 / 14 ]

What you can do with Penti's hardcoded secrets detection tool

The free hardcoded secrets detection tool is one of the free web application tests on Penti's agentic pentesting platform, and it runs as a real penetration test: an AI agent that decides its next move from what your application returns and works through your live application in real time.

Find exposed secrets in your own application before anyone outside does.
A new deploy can serve something the previous one did not, so run the test again once it is live.
Show that your web app was tested for secrets exposure, backed by an evidence log.
Watch the AI pentester probe, confirm, and record every step, then read the full log at the end.
/ how it works
[ 03 / 14 ]

How Penti's free secrets scan works

The test runs as a live feed you can pause, rewind, and replay at half or double speed. You watch the AI pentester think, probe, and confirm in real time, then read the full evidence log at the end.
01

Launch

Add your company email and the target URL, accept the terms and the pentesting agreement, then start the test.
02

Reconnaissance

The AI pentester extracts every link, script, and form action from your homepage to map how the application is built.
03

Discovery

It reads your robots.txt and sitemap, then builds a full list of the pages and endpoints worth testing.
04

AI testing

The agent probes JavaScript assets, environment and configuration files, backups, debug logs, and public directories for exposed credentials.
05

Verification

Each response is checked, and every endpoint and status code is recorded, including the paths your server or WAF blocked.
06

Report

You get an evidence log with a clear verdict, the proof behind it, and advice on what to fix.
/ what we detect
[ 04 / 14 ]

What this hardcoded secrets scanner looks for

Penti's free test works from the outside, the way an attacker would. It takes your URL, maps what the application serves, and checks the places where sensitive credentials end up by accident. This secret scanner covers what your live application exposes to the internet, not your git history or pull requests inside your code repositories.

What the browser receives

JavaScript assets and front-end bundles, where a key added to make an analytics, payment, or AI integration work usually ends up.

Files left on the server

Environment files, exposed version control configuration, configuration and backup copies, and debug logs that shipped with the build.

Directories that answer

Upload, theme, and plugin paths that list their contents to anyone who asks.

Everything reachable

Form parameters and hidden inputs, plus every endpoint found through your robots.txt, your sitemap, and your own internal links.
/ technical details
[ 05 / 14 ]

Technical details

The platform lists this test as OWASP A04 · Hardcoded Secrets at Critical severity. It is built for web applications, takes two inputs, and finishes in a few minutes with nothing to configure.

DetailValue
TestOWASP A04 · Hardcoded Secrets
SeverityCritical
Designed forWeb applications (webapp targets)
What you enterCompany email, plus the target URL or hostname of a web application with JavaScript assets
EngineAI-powered agentic penetration test, runs in an isolated environment
StandardsOWASP Top 10 and the OWASP Testing Guide, NIST Cybersecurity Framework, MITRE ATT&CK
Typical run timeAbout three minutes
Free tier1 test at a time, up to 3 tests per month per business address
What one real run looked like:
168
endpoints checked
397
HTTP requests
~3 min
to a verdict
Your own numbers depend on the size of your application, so treat these as one run, not a fixed figure.
Before you run it. Test only what belongs to you. Starting the test confirms that you are the lawful owner, operator, or authorized controller of the target. Tell your own team first: the test sends real requests to your live application, and your WAF, intrusion detection, or on-call alerts can pick them up.
/ results
[ 06 / 14 ]

Secret scanner results

Every test ends with a full Penetration Test Evidence Log, shown on screen when the live run finishes. A clean result is still a verdict: the report gives a posture rating, explains why the exploit did not get through, and lists what to keep doing. It walks through everything the AI pentester did, in this order.

[  01  ]

HTTP Requests and Responses

The full request and response detail for each URL that answered, plus a summary of the paths that returned 404.

[ 02 ]

Endpoint Enumeration

Every endpoint tested with its status (200 / 403 / 404) and a summary count.

[  03  ]

Authentication Details & Vulnerabilities Confirmed

The authentication process that was checked, plus each confirmed issue with its name, description, how it was exploited, evidence from the logs, and risk level.

[  04  ]

Data Exposed

Whether any sensitive data was exposed during testing.

[ 05 ]

Execution Metrics & Technical Details

Total time, steps executed, HTTP requests made, execution environment, and the detected server or WAF.

[  06  ]

Penetration Test Report & Evidence Summary

A Security Assessment of your overall posture and risk, plus an Executive Summary of what was tested, what was found, and what to fix.

/ benefits
[ 07 / 14 ]

Why use Penti to detect secrets in your web app

Penti runs a real penetration test, not a surface scan: proof-based results, clear fixes, and nothing to set up.

Each confirmed issue carries the evidence from the logs that produced it, which is what separates a real finding from a false positive.
The live feed shows every step and replays on demand, so nothing about the result is hidden.
About three minutes, no install, no account setup. A company email, a target URL, and the pentesting agreement are all it takes to start.
Every endpoint, status code, and finding is written down and stays readable after the run.
The report ends with remediation advice, so your development teams know what to change.
This free test is one of the OWASP Top 10 checks Penti covers, and the same platform runs deeper testing across more of your attack surface when you need it.
/ start scanning
[  08  /  14  ]

Run your free secret scan now

Penti's free tool for detecting hardcoded secrets points an AI pentester at your live web app and shows you what it exposes. Enter your company email and target URL to start.

/ next steps
[ 09 / 14 ]

Found an exposed secret? What to do next

A credential that reached the public internet should be treated as compromised, even when nothing in your logs looks wrong. Work through these steps in order.
01

Revoke and rotate first

OWASP's guidance for an exposed key is immediate revocation. Create a replacement, update the application, then delete the old credential.
02

Check what happened while it was open

Most providers log API key usage, so check whether the key was used, from where, and when.
03

Take it off the client side

Google's own advice is to keep API keys out of client code. Route the call through your backend so the value never reaches a visitor.
04

Cut the blast radius

Grant the replacement the least privilege it needs and keep user access to it narrow, so the next exposure costs less.
05

Tell the people who need to know

Your security and platform teams, and any customer or vendor whose data sat behind that credential.
06

Re-test

Run the free test again once the fix ships and confirm that nothing is still served.
/ prevention
[ 10 / 14 ]

How to prevent hardcoded secrets

These exposures are preventable, and none of the habits below require a dedicated secrets security platform to get started.

Keep secrets out of the code

Use environment variables and a secrets manager such as AWS Secrets Manager or its equivalent in your cloud, instead of literal values sitting in files.

Never ship a secret to the browser

A value that must stay private belongs on your backend, never in the bundle you send to visitors.

Catch secrets before the commit

Pre-commit hooks and repository scanning in your CI/CD pipelines stop a key from reaching a branch. GitHub Secret Protection goes further and blocks a push that contains a secret.

Automate the check on every change

An automated hardcoded secrets detection tool running on pull requests catches what a human reviewer can miss on a busy day.

Keep configuration files out of public paths

Environment files, database backups, and debug logs do not belong anywhere a browser can reach them.

Re-test after every release

Each build ships new assets, and a free secret detection run takes minutes. Re-testing is the cheapest way to prevent future exposures from going unnoticed.
/ reviews
[ 11 / 14 ]

What our clients say

Security teams come to Penti for pentest results they can act on straight away.

DREW DANNER
Managing Director, BD Emerson

Penti's service is a game changer for our compliance needs. The insights we gained were invaluable for our team.  Doing this well is crucial for our compliance targets and key in advancing our strategic initiatives.

ALBERTO SHEINFELD
CTO, Lev

The integration between Penti, our system, and third parties like Vanta is exceptional. I would also like to mention that their response times are extremely fast!

CAMERON SWAIM
CTO, ReadWorks

Penti has been like having an experienced and nimble Security Engineer on staff. They have outlined issues in our platform and guided us towards implementations and fixes that allow for us to ensure we are treating our users data with the utmost care.

/ related
[  12  /  14  ]

Other free tools

[ 01 ]

Reflected XSS

Learn more
[ 02 ]

Weak JWT Secret

Learn more
[ 03 ]

Grafana Path Traversal (CVE-2021-43798)

Learn more
/ start scanning
[  13  /  14  ]

Secure your web app with Penti

Do not wait for someone else to find a live key in your front end. Run the free hardcoded secrets test, see what your application exposes, and get a clear plan to fix it.

/ q&a
[ 14 / 14 ]

FAQ

[  01  ]

What is a secrets scanning tool?

A tool built to detect secrets, meaning credentials left where they can be read. Some work inside code repositories. Penti's free test works from the outside, checking what your live application serves to the internet.

[  02  ]

What happens if the test finds no secrets?

Most runs come back clean, and that is a useful outcome. You still get the full evidence log and a posture rating, so you can show the application was tested for secrets exposure rather than assumed safe.

[  03  ]

Is this hardcoded secrets scanner free?

Yes. The free tier runs one test at a time, up to three tests per month per business address, and needs only a company email. There is no account setup.

[  04  ]

Do I need to install anything?

No install and nothing to configure. You provide a company email and the target URL, and the test starts.

[  05  ]

Do I need permission to scan a site?

Yes. Test only a target you own or are authorized to assess. You confirm this by accepting the Terms of Service and the Pentesting Agreement before the test starts, and you should tell your own team, since the test sends real requests to a live application.

[  06  ]

How long does a scan take?

About three minutes for a typical application. The exact time depends on how many pages and endpoints the agent finds.

[  07  ]

What do I get at the end?

A full Penetration Test Evidence Log on screen: the request and response detail, every endpoint tested with its status, any confirmed findings with evidence and risk level, execution metrics, and a summary with remediation advice.

[  08  ]

How often should I run this test?

Run it after every release that changes your front-end or adds a server-side feature, since each build ships new assets that a previous run never saw. The free tier allows up to three tests per month per business address.

[  09  ]

My site is static. Does this still apply?

Less of it does. With no server-side backend there are no debug logs, environment files, or database credentials left behind on a server, and a run against a static site reports exactly that. What still applies is everything shipped to the browser: a key pasted into front-end code to make an analytics, payment, or AI integration work reaches every visitor. Run it again whenever you add a dynamic feature or a custom API integration.

[  10  ]

Does it scan my code repository?

No. It tests your live web application from the outside: the assets and files your server sends to visitors. Repository scanning is a separate discipline, and a dedicated tool for detecting hardcoded secrets in source code covers it.

[  11  ]

What does this free test not cover?

It checks one issue class, hardcoded secrets, on one target, from the outside, and a single run reflects only what was live at that moment. It does not monitor your whole attack surface on an ongoing basis. A full Penti pentest goes further: your entire attack surface, on a schedule, verified by humans.