CEH Footprinting, Reconnaissance and Scanning Practice Question
Which Google dork would a penetration tester use to find login pages that are indexed by Google?
⚠ Common exam trap
Many candidates confuse 'inurl:login' with 'intitle:login' or 'intext:login', but 'inurl:' is the precise operator for finding login pages by their URL structure, while 'intitle:' and 'intext:' target page titles and body content, respectively, which are less reliable for this specific purpose.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
inurl:login
The Google dork 'inurl:login' specifically searches for URLs containing the word 'login', which commonly appear in login page paths (e.g., /login.php, /login.aspx). This allows a penetration tester to quickly identify indexed login portals for further reconnaissance, such as testing for default credentials or brute-force attacks.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
filetype:xls username password
Why it's wrong here
This Google Dork, `filetype:xls username password`, is designed to locate specific file types, such as Excel spreadsheets, that contain the literal strings "username" and "password." While highly effective for discovering inadvertently exposed credentials, data dumps, or sensitive internal documents, it is fundamentally distinct from identifying an active web application's login interface. A login page is a functional HTML form, not a static document, making this dork unsuitable for its discovery.
- ✗
intitle:"index of"
Why it's wrong here
The `intitle:"index of"` dork specifically targets web pages where the HTML `<title>` tag contains the exact phrase "index of." This pattern is characteristic of default Apache or Nginx web server directory listings, which expose the server's file system structure and contents. While useful for discovering sensitive files or directory traversal vulnerabilities, it does not directly lead to an application's dedicated login form, which typically has a more descriptive and application-specific title.
- ✓
inurl:login
Why this is correct
The `inurl:login` dork instructs Google to return results where the string "login" appears anywhere within the URL path or filename. Web developers commonly incorporate terms like "login," "signin," or "authenticate" into the URL structure to designate their authentication pages. This makes `inurl:login` a highly precise and efficient method for directly identifying and locating the entry points for user authentication within various web applications.
- ✗
site:example.com intext:password
Why it's wrong here
The dork `site:example.com intext:password` restricts the search to a specific domain (`site:example.com`) and then looks for pages containing the literal word "password" within their visible text content. While a login page might contain this word, this dork is too broad and imprecise. It would also match password policy documents, "forgot password" pages, or even forum posts discussing passwords, making it an inefficient tool for exclusively finding the primary login form.
Go deeper
Related to this question
About these practice questions
One of 870 original CEH practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CEH practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CEH exam.