Study guide

5.3 DNS, Certificate Transparency, and Search Engine Enumeration

CompTIA PenTest+ PT0-003

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current PT0-003 Exam Facts 1.2 Format, PBQs, Scoring, and Retake Policy 1.3 Recertification, CEUs, and Career Fit

2 Pre-Engagement Planning

2.1 Scope, Rules of Engagement, and Agreements 2.2 Target Selection and Assessment Types 2.3 Shared Responsibility, Legal Authorization, and Ethics

3 Collaboration, Frameworks, and Threat Modeling

3.1 Collaboration, Escalation, and Stakeholder Communication 3.2 Testing Frameworks and Methodologies 3.3 Threat Modeling: STRIDE, DREAD, and OCTAVE

4 Reporting and Remediation

4.1 Penetration Test Report Components 4.2 Findings Analysis and Remediation Recommendations

5 Information Gathering

5.1 Active vs Passive Reconnaissance 5.2 OSINT Sources and Techniques 5.3 DNS, Certificate Transparency, and Search Engine Enumeration 5.4 Network Recon, Protocol Scanning, Sniffing, and Banner Grabbing

6 Enumeration Techniques

6.1 OS Fingerprinting, Service Discovery, and Host Discovery 6.2 DNS, Directory, Share, and Account Enumeration 6.3 Secrets, Permissions, and Wireless Enumeration 6.4 WAF Enumeration, Web Crawling, and Attack Path Mapping

7 Recon Scripting and Tools

7.1 Modifying Bash, Python, and PowerShell for Recon 7.2 Recon and Enumeration Tools

8 Vulnerability Scan Types

8.1 Network, Host, Authenticated, and Wireless Scans 8.2 SAST, DAST, IAST, SCA, IaC, and Mobile Scans 8.3 Container, Secrets, and ICS Vulnerability Assessment 8.4 Core Vulnerability Scanners (Nessus, OpenVAS, Nikto)

9 Scan Analysis and Physical Security

9.1 Specialized Discovery Tools 9.2 Validating Scan, Recon, and Enumeration Results 9.3 Public Exploit Selection and Scripted Validation 9.4 Physical Security Concepts for PenTests

10 Attack Prioritization and Preparation

10.1 Target Prioritization: CVSS, CVE, CWE, and EPSS 10.2 Exploit Selection, Customization, and Attack Documentation

11 Network Attacks

11.1 On-Path, VLAN Hopping, Relay, and Multihomed Hosts 11.2 Default Credentials, Misconfigured Services, Packet Crafting, and Certificate Services

12 Authentication Attacks

12.1 Pass-the-Hash, Pass-the-Ticket, Pass-the-Token, and Kerberos Attacks 12.2 Password Attacks, MFA Fatigue, LDAP Injection, OIDC, and SAML

13 Host-Based Attacks

13.1 Privilege Escalation and Credential Dumping 13.2 Process Injection, Security Bypass, and Host Attack Tools

14 Web Application Attacks

14.1 SQL, Command, XSS, and SSTI Injection 14.2 CSRF, SSRF, Deserialization, IDOR, and Directory Traversal 14.3 LFI/RFI, Web Shells, API Abuse, JWT, and Session Hijacking

15 Cloud Attacks

15.1 IAM Misconfiguration, Metadata Service, and Exposed Storage 15.2 Container Escape, Supply Chain, and Cloud Attack Tools

16 Wireless and Social Engineering

16.1 Wireless Attacks and Tools 16.2 Phishing, Spearphishing, Whaling, Vishing, and Smishing 16.3 Physical Social Engineering and SE Tools

17 Specialized Systems

17.1 Mobile Attacks and AI Prompt/Model Attacks 17.2 OT/ICS, NFC, RFID, and Bluetooth Attacks

18 Attack Scripting and BAS

18.1 PowerShell, Python, and Bash Attack Automation 18.2 Breach and Attack Simulation (Caldera, Infection Monkey, Atomic Red Team)

19 Persistence

19.1 Scheduled Tasks, Services, Accounts, and Shells 19.2 C2, Backdoors, Rootkits, and Security-Control Tampering

20 Lateral Movement

20.1 Pivoting, Relays, and Additional Credential Capture 20.2 Remote Services: SMB, RDP, WinRM, WMI, SSH, and Others 20.3 Lateral Movement Tools and LOLbins

21 Exfiltration and Cleanup

21.1 Staging and Exfiltration 21.2 Cleanup, Restoration, and Artifact Preservation

5.3 DNS, Certificate Transparency, and Search Engine Enumeration

Key Takeaways Explain This Topic AI

DNS lookups (A, AAAA, MX, NS, TXT) at a public recursive resolver are ordinary OSINT; reverse DNS (PTR) maps IPs back to names; AXFR against the authoritative server is active zone enumeration.

Certificate transparency logs list hostnames and SANs from issued certificates — crt.sh-style searches often reveal vpn.dev.example.com and expired or leftover names without touching the host.

A CT or DNS name is a candidate, not automatic scope; reconcile it with SoW selectors and exclusions before any scan.

Search-engine analysis, Google-style dorking, and cached/archived pages (Wayback) recover forgotten endpoints passively; scraping the live HTML is active.

HTML scraping of an in-scope live app harvests comments, hidden fields, JavaScript endpoints, and robots.txt/sitemap clues that search caches may have missed.

Last updated: August 2026

Once social and leak OSINT is in the notes, example.com still has to become a list of names, addresses, and URLs. Objective 2.1 groups that expansion under DNS lookups , reverse DNS lookups , certificate transparency logs , search engine analysis/enumeration , cached pages , and HTML scraping . Together they are how testers find the VPN the marketing site never mentioned and the forgotten /old-admin path still sitting in a 2019 archive.

DNS lookups

A DNS lookup asks a resolver for records. For exam purposes, know what each common type is for :

  • Record What it answers Recon use
  • A IPv4 address for a name Map www.example.com to a host you may later scan if the IP is in-scope
  • AAAA IPv6 address Dual-stack hosts that never appear in an IPv4 CIDR

MX Mail exchangers Third-party mail (Microsoft 365, Google) versus an on-prem relay you might think is in-scope

  • NS Authoritative name servers Where to aim a later AXFR attempt; often a different vendor than the web host
  • TXT Arbitrary text SPF, DMARC, domain-verification tokens, sometimes leftover cloud-project IDs
  • CNAME Alias CDN, WAF, or SaaS fronts that are not the origin
  • PTR Reverse map (IP → name) Reverse DNS lookups

Querying those records at a public recursive resolver does not put a SYN on the web server. It is the usual passive DNS picture. Two traps sit next to that comfort.

Reverse DNS lookups

Reverse DNS uses PTR records. Given 10.4.12.8 in an in-scope CIDR (or a public IP you already know belongs to the client), a PTR of vpn.dev.example.com corroborates the CT finding from the worked scenario. Reverse lookups also cluster hosts: a block of PTRs named cam01-bldg4 versus pos-store-12 tells you camera versus payment — and payment may be excluded. PTR is not guaranteed; many cloud IPs have generic provider names. Absence of PTR is not absence of a host.

Zone transfer (AXFR) as enumeration

A zone transfer asks an authoritative name server to dump the zone. If it succeeds, you receive the full name list the organization intended only for secondaries. That is a classic misconfiguration finding and a gold-mine enumeration technique. It is not the same as an A-record lookup at Google Public DNS. AXFR is a protocol conversation with the client's NS (or a forgotten secondary still allowing transfers to any querier). Classify it as active DNS enumeration . If RoE has not opened yet, do not AXFR; stick to recursive lookups and third-party DNS history (SecurityTrails-style, DNSdumpster, Amass passive sources — tools chapter).

Failed AXFR is normal and not a finding by itself. Open AXFR to the world is the finding. Incremental transfers (IXFR) are the same idea with a smaller payload.

Certificate transparency logs

Certificate transparency (CT) is a public, append-only log of issued TLS certificates. Browsers and CAs participate so a sneaky certificate cannot hide. For a tester, CT is a hostname enumerator . Search a domain (the crt.sh pattern on the exam) and you see every name that appeared as a common name or subject alternative name (SAN) on a logged cert: www , api , dev , vpn.dev.example.com , *.internal.example.com if someone was careless, plus expired and revoked history.

Worked scenario, again: CT lists vpn.dev.example.com and an expired certificate . Passive facts you may write down now:

A VPN (or at least a VPN-named host) exists or existed.

Someone let a cert expire — cryptographic hygiene, possibly still serving a leftover name.

SANs may list more environments ( staging , okta , a partner domain).

Facts you may not assume:

The host is in-scope. Scope is the SoW, not the SAN list.

The expired cert is still presented. Confirming live TLS is a banner/handshake against the host (active).

A SAN for payments.partner.net is client-owned. It is probably a processor; exclusions apply.

CT does not decrypt HTTPS. It does not replace Nmap. It does not give you the private key. If a private key leaked in GitHub (previous section), that is the cryptographic flaw; CT only told you the name the key would have matched.

Search engine analysis and enumeration

Search engine analysis/enumeration is deliberate querying — including dorking — to find indexed pages the company did not mean to keep public: site:example.com filetype:pdf , login panels, directory listings, intitle:"index of" , exposed /server-status , backup zips, and third-party hosts that mention the brand. Shodan and Censys sit in this family as search-engine-like internet-scan databases : you query their index; you do not scan. From your perspective that is passive. Treat their banners as historical until you confirm.

Stay professional: dorking public indexes is recon. Using a search engine to locate exploit PoCs is research. Running those exploits is Domain 4 and out of this chapter.

Cached pages

Cached pages and archives (search-engine cache, the Wayback Machine ) recover content after the live site is "fixed." Forgotten endpoints, old JavaScript with API keys, product version numbers in a 2022 blog, a staging URL that still resolves, and a retired /phpmyadmin path are common. Reading cache or Wayback is passive . Hitting the live URL you just discovered is active and needs to be in-scope.

If the cache shows a key, handle it like a repo secret: redact, escalate rotation, do not replay it for fun.

HTML scraping

HTML scraping is collecting the live (or authorized-lab) markup and linked assets. CompTIA lists it separately from search engines because you are now talking to the origin or its CDN. In-scope scrape targets:

HTML comments ( <!-- todo: remove debug /api/v1/internal --> ).

Hidden fields and extra form parameters the UI does not show.

JavaScript bundles that list endpoints , feature flags, and sometimes tokens.

robots.txt and sitemap.xml (also reachable passively if a search engine cached them; fetching live is a request to the site).

Framework generator tags, generator meta, and versioned static paths.

Scraping is active when aimed at the live application. It is also usually low-and-slow HTTP GET , not a SYN sweep, so RoE that forbids "scanning" may still allow crawling — unless it forbids that too. Read the RoE. Do not confuse a polite scrape with permission to fuzz every parameter; that is later web-attack work.

Information disclosure from this cluster is often the forgotten thing: a hostname only in CT, a path only in Wayback, a comment only in HTML. The tester's job is to merge those lists, drop exclusions, and hand a clean target list to network recon.

Loading diagram... From one domain name to a reconciled host list