CompTIA PenTest+ guideStudy & preparation
CompTIA PenTest+ Reconnaissance: What Does the Evidence Prove?
Short answer
Reconnaissance evidence supports a specific observation, not every conclusion that observation suggests. CompTIA's PT0-003 objectives include passive information gathering, enumeration and reconnaissance tools; interpreting their results means keeping observed facts, possible explanations and unresolved questions separate. A certificate name does not prove current ownership, robots.txt does not grant permission, and an open|filtered UDP result does not confirm an open service.
What is an observation, an inference or an unknown?
Read reconnaissance output by stating what the source actually shows, then separating possible explanations from unresolved questions. CompTIA's PT0-003 objectives include passive information gathering, enumeration and reconnaissance tools in objectives 2.1–2.4; the objectives document, version 5.0, was checked November 11, 2026.
Use three labels in your study notes:
- Observation: the supplied certificate record contains a particular name.
- Inference: that name may identify an asset relevant to the engagement.
- Unknown: whether the asset exists now, who currently controls it and whether testing it is authorized.
These are editorial study labels, not a required CompTIA reporting template. Their purpose is to stop a plausible explanation from silently becoming a confirmed fact. If you cannot point to the evidence supporting a sentence, rewrite it as a question or qualify it.
For where this skill fits in the exam, use the PenTest+ domain and format overview. Here, the practical task is to build a defensible evidence ledger. Reconnaissance and Enumeration practice is planned for full CompTIA PenTest+ prep.
How do passive and active sources change what you know?
NIST SP 800-115 distinguishes passive observation from active discovery that sends probes. Its stable conceptual guidance, checked November 3, 2026, helps you identify how information was obtained; it does not make either method a guarantee of completeness or prescribe a universal CompTIA workflow.
Certificate Transparency logs, for example, are public, append-only records of certificate issuance and names. Consulting those records can reveal leads without querying the target systems. An active result answers a different question: what happened during a particular interaction with the target?
Keep the source attached to the statement. “The certificate record names Archive B” is stronger writing than “Archive B is an active client server,” because the latter adds facts the record has not established. Likewise, keep the time and collection context supplied with an active result instead of turning it into a timeless property of the asset.
Before combining two records, ask whether they concern the same asset and the same question. Two observations are not automatically independent confirmation of the conclusion you want to draw.
Why can a hostname or robots.txt entry mislead you?
A discovered name can look authoritative because it appears in a public certificate record. The record supports issuance and naming, not current ownership or authorization to test. Preserve it as a lead until the necessary asset and scope evidence is available.
A Disallow entry in robots.txt has a similarly limited meaning. RFC 9309 describes instructions for conforming crawlers; the file does not provide access control or define the written engagement scope. A listed path also does not prove that the path still exists. These source notes were checked November 11, 2026.
Avoid three unsupported substitutions:
- “Listed in a certificate” becomes “confirmed current asset.”
- “Listed in robots.txt” becomes “protected content exists there.”
- “Disallowed for crawlers” becomes “excluded from the engagement.”
Record the original observation first. Then write the separate question it raises. If that question concerns permission, resolve it against the engagement's authorization before choosing an active check; the crawler instruction cannot answer it.
What does an ambiguous UDP result leave unresolved?
Nmap's documentation, checked November 11, 2026, explains that no response after UDP retransmissions can produce open|filtered. An open service and a filtering device dropping traffic remain possible. The label therefore preserves uncertainty; it does not select one explanation. Scan-state meanings like this are worth recalling exactly, which is what recall flashcards planned for full CompTIA PenTest+ prep are for.
The captured distinctions are narrow but useful:
| Evidence supplied in the result | Supported interpretation |
|---|---|
| No response after UDP retransmissions | open|filtered; the two possibilities remain unresolved |
| A service reply | Supports an open classification |
| An ICMP port-unreachable response | Supports a closed classification |
Version detection can help distinguish open from filtered, but it does not guarantee a resolution. Treat it as a possible follow-up only when the engagement permits it. The immediate study task is to explain what additional evidence would answer the question, not to memorize an unsupported command or assume every ambiguous result must become conclusive.
How do you combine conflicting clues without overclaiming?
Consider this original fictional packet, created for study and unrelated to any official or recalled exam question. The engagement permits review of the supplied records and the listed checks on Asset A. It does not authorize testing Archive B. The exercise supplies no current confirmation of Archive B's status.
| Source | Observation | Confidence limit | Authorized next step in this exercise |
|---|---|---|---|
| Certificate Transparency extract | A certificate record contains the name assigned to Archive B | Issuance and naming do not establish current ownership or availability | Keep the record and request current asset information through the agreed contact |
| Client-supplied asset register | Archive B is labeled retired; Asset A is listed for the permitted checks | This establishes what the register says; it does not independently verify Archive B's present state | Note the difference between the register and the certificate lead; do not probe Archive B |
| Supplied robots.txt from Asset A | A crawler rule disallows /records-old/ | Neither path existence nor access protection is established | Check whether a path review is within the listed permissions before considering one |
| Asset A UDP result, capture A | No response after retransmissions; open|filtered recorded | An open service and filtering remain possible for this observation | Preserve the result and compare its collection context with capture B |
| Asset A UDP result, capture B | A service reply is recorded for the same labeled port at a different time | The reply supports open for this observation; it does not explain capture A | Reconcile asset identity, time and supplied collection notes before writing a combined conclusion |
The certificate and register are not necessarily contradictory: one describes a certificate record, while the other states a retirement status. Neither alone supplies a fresh asset check. Keep both, without deciding that the more recent-looking document must answer every question.
The UDP captures also need a bounded conclusion: “Capture B recorded a service reply; capture A remained ambiguous.” Do not rewrite capture A as confirmed open just because capture B is clearer. If the packet does not explain the difference, leave that explanation unresolved.
What should the evidence ledger send to the next phase?
Hand off the observation, its source, its limitations and the permitted next question. Do not promote a discovered name, crawler entry or open port into a vulnerability claim. NIST's distinction matters here: scanning can identify possible weaknesses that require validation.
When the packet actually includes a claimed weakness, move to validating a PenTest+ vulnerability finding. That is a separate task from establishing what reconnaissance evidence shows.
For practice, cover the interpretation column in the fictional packet and reconstruct each limit aloud. Then try the 20 free PenTest+ practice questions, recording the specific inference behind each missed answer. Fix It, planned for full CompTIA PenTest+ prep, holds those missed answers for a retry. Use the free PenTest+ study plan to schedule another review of the concepts you could not explain.
Your finished ledger should make two sentences easy to write: “This evidence supports this observation” and “This question still needs an authorized check.”
Trust the source
Official sources
Exam policies can change. Use these primary sources for the most current details.
- CompTIA PenTest+ PT0-003 V3 Certification Exam Objectives, document version 5.0CompTIA↗
- Technical Guide to Information Security Testing and Assessment, SP 800-115NIST↗
- Certificate TransparencyCertificate Transparency↗
- RFC 9309: Robots Exclusion ProtocolRFC Editor↗
- Port Scanning BasicsNmap↗
- Port Scanning TechniquesNmap↗