Site Exposure Scanner: exposed files, admin panels and response headers

Runs in: Site Exposure Scanner

Requests a fixed catalogue of paths that should never be public on your site (environment files, source control metadata, backups and database dumps, configuration files, CMS and framework files, admin and developer consoles, logs, private keys, known webshells, CI/CD configuration), judges each response, then checks the response headers of your site's root URL and fingerprints known web applications. The Site Exposure Scanner runs on demand and in scheduled reports. An interactive scan requires login and runs only against sites whose ownership your account has verified.

How it tests

  • The entered URL is reduced to scheme://host[:port]; a URL without a scheme gets https://. Any path in the entered URL is discarded; every probe is made from the site root.
  • Path catalogue: 247 entries in 11 sections, plus 3 entries in Backup & Database Dumps built from the hostname with a leading www. removed (/<host>.zip, /<host>.sql, /<host>.tar.gz). /configuration.php appears in two sections, so 249 distinct paths are requested with the option “I control this whole server” on and 247 with it off (the default), 12 in parallel, 8 s timeout each, User-Agent NetTests-ExposureScan/1.0.
Section Entries
Environment & Secrets 19
Source Control 10
Backup & Database Dumps 33 + 3 host-named
PHP & Generic Config Files 39
WordPress 20
CMS & Frameworks 31
Admin Panels & Dev Tools 44
Log Files 14
Private Keys & Certificates 10
Known Webshells 13
DevOps & CI/CD Config 14
  • Two entries in Admin Panels & Dev Tools address other ports on the same host: :2082/ (cPanel) and :8880/ (Plesk), with the scheme of the entered URL; the port replaces any port in the entered URL. They are optional and off by default: they are requested only when the option “I control this whole server” is ticked, on the tool page or in the report's tool settings. On shared hosting these ports belong to the hosting provider and serve every account on the server. With the option off, no request goes to a port other than the one of the entered URL and the standard web ports 80 (http) and 443 (https): a redirect to any other port (for example from /cpanel/ to :2083, or from /webmail/ to :2096) is not followed, that port receives no request, and the check reports the redirect as not followed. A report saved before the option existed runs with it off.
  • Each probe sends one GET without automatic redirects and reads the first chunk of the body (at most 512 bytes). A 301/302/307/308 whose Location stays on the same registrable domain is followed, at most 3 hops; a redirect to another registrable domain is not followed.
  • Each catalogue entry carries a list of content keywords and a severity (critical, high, medium, low). A 200 or 206 response is confirmed when any keyword occurs in the first 512 bytes. Archives and binary files carry their file signature as keyword: ZIP PK\x03\x04/PK\x05\x06, gzip \x1f\x8b\x08 (.tar.gz, .tgz), bzip2 block magic 1AY&SY, tar ustar (POSIX and GNU), OLE compound file (Thumbs.db), Vim swap b0VIM (.wp-config.php.swp). SQL dumps are confirmed by CREATE TABLE, INSERT INTO, DROP TABLE, mysqldump, the MySQL, PostgreSQL and phpMyAdmin dump headers, or PRAGMA foreign_keys.
  • Baseline: after the catalogue, every path that answered 200, 206, 401, 403 or an unfollowed redirect is compared with a path that cannot exist and that the server routes alike (same parent directory, leading dot, last extension and trailing slash; last segment nt-<16 hex>, one random token per scan). Each distinct baseline path is requested once. A response matches its baseline when the status is equal and, for 200/206, the first 512 bytes are at least 90 % similar, for an unfollowed redirect the Location host is equal. A site that answers 404 receives no baseline requests; a site that answers every path alike receives up to 91.
  • Security Headers section: one further GET of the root URL with redirects followed, 8 s timeout. Reads Strict-Transport-Security (only when the entered URL is HTTPS), X-Frame-Options, frame-ancestors within Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, Content-Security-Policy and Server. The same response headers feed the PHP version disclosure check, the PHP2Shell rule and the software version currency rule.
  • Software Versions section: the web application fingerprints rule, which includes the YesWiki version check; it makes its own requests as described there.
  • Interactive runs report progress per request; the total grows by the baseline requests. An interactive scan requires login and runs only against sites whose ownership your account has verified.

What you see

Path catalogue sections (one check per catalogue entry, labelled with the entry's display label):

Situation Result
Same response as the baseline path Passed: "HTTP <status> at <path> — the same response as for a path that does not exist"
HTTP 200/206, keyword found, path public by design (/wp-login.php) Passed: "HTTP 200 at <path> — the standard WordPress login page, public on every WordPress site; not an exposure. Limit login attempts or require two-factor login"
HTTP 200/206, keyword found, severity critical or high Error: "HTTP 200 — confirmed exposure at <path>"
HTTP 200/206, keyword found, severity medium or low Warning: same text
HTTP 200/206, no keyword found, or the entry has no keywords Warning: "HTTP 200 at <path> — verify manually (content inconclusive)"
HTTP 401 Warning: "path exists behind authentication; confirm it must be reachable from the internet"
HTTP 403 Warning: "path exists but access is blocked; confirm intentional"
Redirect not followed (other registrable domain, or still redirecting after 3 hops) Warning: "HTTP <status> redirect at <path> — path exists, follows redirect"
Timeout or connection error Passed: "no response (timeout or connection error)"
Any other status (404, 5xx and others) Passed, label only
Option “I control this whole server” off (the default) No check for :2082/ and :8880/; Admin Panels & Dev Tools carries the note "Hosting control-panel ports not checked: the option “I control this whole server” is off. …", which counts as neither passed nor failed

Security Headers section:

Situation Result
HTTPS URL without Strict-Transport-Security Error: "HTTPS sites must send HSTS to prevent downgrade attacks."
Neither X-Frame-Options nor CSP frame-ancestors Warning: clickjacking
X-Content-Type-Options, Referrer-Policy or Content-Security-Policy absent Warning per header
Server header contains a version number (\d+\.\d+) Warning: "remove the version number from the Server header"
X-Powered-By discloses a PHP version Warning: "set expose_php = Off"
PHP2Shell rule, software version currency rule Verdicts as described in those rules
Header present Passed, with the header value
Root URL could not be fetched Error: "Could not retrieve headers"

Software Versions section:

Situation Result
A known web application found Verdict per the web application fingerprints rule (and the YesWiki version check)
Nothing found Passed: "None of the web applications we fingerprint (webmail, consoles, CMSs, frameworks) were found on this site."
None of the fingerprint requests got a response Warning: which web applications the site exposes "could not be determined"
Option “I control this whole server” off (the default) The same note as in Admin Panels & Dev Tools: the control-panel ports were not checked

Limits

  • The baseline recognises a server that answers every path of a route alike. A generic page that differs from the baseline by more than 10 % within its first 512 bytes (a large per-request token, a page that echoes a long path) is judged by keywords; short keywords in it (Error, host, password, WordPress for wp-login.php) can then still confirm. The other-port probes (:2082/, :8880/) get no baseline.
  • Only the first 512 bytes of a body are searched. A keyword further into the file leaves a real exposure at "verify manually".
  • Entries without keywords can never become an Error: .htdigest (its user:realm:hash lines have no fixed substring), .git/COMMIT_EDITMSG, debug.php, wp-cron.php. A .git/HEAD with a detached head (a bare commit hash) is a Warning.
  • The :2082/ and :8880/ probes use the entered scheme, so a panel serving only plain HTTP on that port is not reached by an HTTPS scan.
  • Security headers are judged by presence; their values are not evaluated (only the Server header is searched for a version). HSTS is checked only for HTTPS URLs.
  • Sites installed in a subdirectory are probed at the root only.
  • /configuration.php appears in two sections; one shared result serves both checks.

Rules this scan applies