Information Disclosure Scanner
Look for the files that should never be public: exposed .env and .git, published source maps, backup files, and stack traces that leak paths and secrets in error responses.
Critical5High6Medium15Low9Info12
Critical5 checks
- Flask debug mode enabled in productionThe Flask interactive debugger (Werkzeug) is accessible, indicating DEBUG=True in a production environment.
- Django technical 500 debug page exposedA Django debug error page (yellow screen) is visible, indicating DEBUG=True in the production environment.
- Rails exception page accessible in productionA Rails exception page is visible, exposing stack traces and application internals to the public.
- Terraform State File (.tfstate) Publicly AccessibleThe response body matches the structural shape of a Terraform state file: a terraform_version version string, a lineage UUID, and a top-level resources array, all present in the same JSON document. This checks the .tfstate format itself, not just a filename in a URL.
- etcd API Reachable Without Client Certificate AuthenticationThe response body matches etcd's own /version endpoint format: an etcdserver version string and an etcdcluster version string returned together in the same JSON object. This field pairing is unique to etcd's version handler and confirms the etcd API is answering requests without a client certificate.
High6 checks
- SQL error message in responseThe response contains an SQL error message, indicating unhandled database exceptions are being returned to clients.
- Spring Boot Actuator endpoint publicly accessibleA Spring Boot Actuator endpoint (/actuator, /health, /env, /metrics, etc.) is publicly accessible.
- Vite development client endpoint accessibleThe Vite development server HMR (Hot Module Replacement) client is accessible, indicating a development server is running in a production or staging environment.
- ASP.NET Core Developer Exception Page ExposedThe ASP.NET Core Developer Exception Page ('An unhandled exception occurred while processing the request' with Microsoft.AspNetCore references) was found in the response.
- Docker Registry HTTP API V2 Open Without AuthenticationThe Docker-Distribution-Api-Version response header (registry/2.0) is present together with an empty '{}' JSON body and no WWW-Authenticate challenge, the exact success response the Docker Registry HTTP API V2 spec defines for a request to the API root that was allowed through without credentials.
- Consul HTTP API Reachable Without AuthenticationThe response carries the X-Consul-Index and X-Consul-Knownleader headers that Consul's HTTP API attaches to every catalog/health/KV query, together with a JSON body that is not an ACL-denied error, confirming the Consul agent's API is reachable and answering queries without a valid ACL token.
Medium15 checks
- Rails Session Cookie Missing HttpOnly FlagA Rails-style session cookie (matching the *_session naming pattern) was found in the Set-Cookie header without the HttpOnly flag. HttpOnly prevents client-side JavaScript from reading the cookie value, which blocks XSS-based session hijacking.
- MySQL Access Denied Error ExposedThe application returned a raw MySQL 'Access denied for user' error message in the response body. These messages include the database username, host, and whether a password was provided, directly exposing database configuration details.
- Credentials or keys embedded in HTML commentsHTML comments in the page source contain potentially sensitive information such as developer notes, internal paths, or debug data.
- Django CSRF token cookie missing security attributesThe Django csrftoken cookie is present but may be missing Secure or SameSite attributes.
- Laravel session cookie missing security attributesThe Laravel session cookie is present but may lack Secure, HttpOnly, or SameSite attributes.
- Express session cookie missing security attributesAn Express.js session cookie is set without required security attributes (HttpOnly, Secure, SameSite).
- Express.js error stack trace in responseThe response contains an Express.js error page with a stack trace, indicating the app is running in development mode or missing a production error handler.
- Rust Panic Trace ExposedA Rust panic message ('thread ... panicked at ...') with a source file reference was found in the response body.
- Go Panic / Goroutine Trace ExposedA Go panic message with a goroutine stack trace ('goroutine N [running]' plus .go file references) was found in the response body.
- Ruby Exception Backtrace ExposedA Ruby exception backtrace (two or more '<file>.rb:LINE:in `method'' frames) was found in the response body.
- Phoenix (Elixir) Debug Error Page ExposedA Phoenix framework debug error page, identifiable by an Elixir error marker alongside a '_web/controllers' or '_web/router.ex' module path, was found in the response.
- Node.js UnhandledPromiseRejectionWarning Leaked to ResponseThe literal text 'UnhandledPromiseRejectionWarning' was found in the response body, indicating Node.js process console output is leaking into HTTP responses.
- Perl CGI Software Error Page ExposedA classic Perl CGI 'Software error:' page with a script path and line number was found in the response.
- Kubernetes API Server Publicly ReachableThe response body matches the structural shape of the Kubernetes API server's meta/v1.Status object (kind, apiVersion, a numeric HTTP code, and a machine-readable reason together) or its /version endpoint (gitVersion, gitCommit, and gitTreeState together), confirming a live Kubernetes control plane is reachable from the public internet.
- Prometheus /metrics Endpoint Exposed Without AuthenticationThe response body contains real Prometheus text-exposition-format output: paired '# HELP' and '# TYPE' comment lines plus at least one actual metric sample line (metric_name{labels} value), not just the word 'Prometheus' or a documentation reference to the format.
Low9 checks
- CORS exposes internal CDN hostnameThe Access-Control-Allow-Origin header references an internal-only host pattern (e.g., .internal, .local, .corp). This reveals internal infrastructure details that should not be visible in public responses.
- nginx version disclosed in 404 / error pagesDefault nginx error pages and the Server response header expose the exact nginx version (e.g., 'nginx/X.Y.Z'). Knowing the version lets attackers search CVE databases for targeted exploits without any active scanning.
- Apache version disclosed in 404 / error pagesDefault Apache error pages expose the full server version, loaded modules, and OS in the footer (e.g., 'Apache/2.4.57 (CentOS) Server at example.com Port 443').
- IIS version disclosed in 404 / error pagesInternet Information Services (IIS) leaks its version in the Server header and detailed error pages. These may also include the .NET CLR version via X-Powered-By and the machine name in some configurations.
- AWS S3 NoSuchBucket error pattern exposedS3 bucket hosting returned a 'NoSuchBucket' or 'AccessDenied' XML error response, revealing the bucket name, region, and an x-amz-request-id header that can be correlated with AWS account activity.
- Privacy Policy page not foundNo privacy policy link or page was detected on the site. A privacy policy is legally required in many jurisdictions (GDPR, CCPA).
- Terms of Service page not foundNo terms of service or terms of use page was detected. Terms of service are recommended for all web services that accept users.
- Jenkins version disclosed in responseThe HTTP response reveals the Jenkins CI server version, either via headers or page content.
- Grafana version disclosed in responseThe Grafana dashboard version is exposed in HTTP headers or page content.
Info12 checks
- Server header truncatedThe Server response header ends with the literal string '(truncated)', which indicates the upstream version was actively hidden but the truncation marker is itself a fingerprint.
- PHP session cookie naming exposes runtimeThe PHPSESSID cookie name in the Set-Cookie header reveals that the server-side runtime is PHP. Default framework cookie names act as free fingerprints for attackers performing stack reconnaissance.
- config.js / settings.js referenced (verify contents)A reference to a config.js or settings.js file was found in the page source. This filename is sometimes used to store API keys, backend endpoints, or environment-specific values, but is just as often a harmless frontend bundle (feature flags, CMS theme settings, public API base URLs). This finding only matches the filename, it does not inspect the file's actual contents.
- env.js / environment.js referenced (verify contents)A reference to env.js or environment.js was found in the page source. These files are commonly placed in the public directory as a deployment-time configuration injection point, and sometimes carry secrets, but just as often only carry a public deployment-stage flag (e.g. window.ENV = 'production'). This finding only matches the filename, it does not inspect the file's actual contents.
- Sitemap.xml publicly accessiblesitemap.xml is publicly accessible or referenced in the page. While a sitemap is designed to help search engines index public content, it may inadvertently list admin paths, internal tools, or staging URLs that were not intended for public visibility.
- OpenAPI schema version exposed in URLThe OpenAPI or Swagger schema version is exposed in the URL or response body. Pinning a specific schema version in the URL or body makes it easy for attackers to identify whether the API is running a release with known vulnerabilities.
- reCAPTCHA site key exposureA Google reCAPTCHA site key was found in the page source. reCAPTCHA site keys are intentionally public (they must be embedded in the browser to work), but their exposure is worth noting for rotation policy awareness.
- Google Analytics tracking ID exposedA Google Analytics tracking ID (UA-XXXX or G-XXXX) was found in the page source. Analytics tracking IDs are public by design and must be present in the browser to work, but their exposure allows third parties to identify the analytics property.
- XML sitemap not foundNo XML sitemap was found at /sitemap.xml or referenced in robots.txt. A sitemap helps search engines index the site correctly.
- Rails default session cookie name reveals frameworkA cookie matching Rails' default *_session naming convention was found in the Set-Cookie header. This reveals that the server-side framework is Ruby on Rails, but not which version.
- Next.js App Router RSC headers exposedReact Server Component (RSC) response headers from Next.js App Router are present, confirming the application is built with Next.js.
- SvelteKit application detectedThe page contains SvelteKit-specific markers, identifying the framework being used.
About the Info disclosure checks
- What does the Info disclosure category check?
- Look for the files that should never be public: exposed .env and .git, published source maps, backup files, and stack traces that leak paths and secrets in error responses. Source maps, .env files, .git exposure, stack traces in errors.
- How many info disclosure checks are there?
- VulnRadar runs 47 checks in this category, ranging across critical, high, medium, low, info severity.
- Do I need to install anything to run the info disclosure checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the info disclosure checks on your site
VulnRadar runs all 47 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.