CPSA ยท Web testing techniques
Spidering vs forced browsing
Crawling linked content, brute-forcing paths, default and unlinked files and client-side functionality.
Key points
- Spidering: follows the links and forms the application exposes, mapping what is reachable from the UI.
- Forced browsing: guesses paths and file names from wordlists, revealing unlinked content such as backup files, admin panels, default files, old versions.
- Client-side code (JavaScript, comments, hidden fields): often names endpoints the crawler never clicks.
Practice questions
Which resource is a spider LEAST likely to discover on its own?
- A page linked from the main navigation menu
- A form action URL present in the HTML
- A file such as config.php.bak that no page references
- A script URL included in a script tag
Show answer
Answer: C. A file such as config.php.bak that no page references
A spider only follows references present in the content it fetches. A backup file that no page links to must be found by guessing names (forced browsing).
Which client-side items can reveal endpoints or paths a spider may miss?
- URLs built inside JavaScript files
- HTML comments left by developers
- The TCP window size of the response
- Hidden form fields in the page source
- The packet TTL value
Show answer
Answer: A. URLs built inside JavaScript files, B. HTML comments left by developers, D. Hidden form fields in the page source
JavaScript files and HTML comments frequently contain API paths or leftovers; hidden form fields can expose internal names. Response status line text and the TCP window size say nothing about application paths.
If a page is not linked anywhere, it is protected from being accessed by users.
Show answer
Answer: False
False. Not being linked is obscurity, not access control. Anyone who guesses or learns the URL can request it unless the server enforces authorisation.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
