Study guide

4.4 Newsgroups, Mailing Lists & Public Archive Reconnaissance

CREST Practitioner Security Analyst CPSA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Soft Skills, Legal Framework & Assessment Management

1.1 The Penetration Testing Engagement Lifecycle & Scoping 1.2 Legal Framework: Computer Misuse Act & Compliance 1.3 Understanding, Explaining & Managing Technical Risk 1.4 Record Keeping, Interim Escalation & Reporting Standards

2 Chapter 2: Core Networking: IP Protocols & Network Architectures

2.1 IPv4 and IPv6 Addressing, Subnetting & Header Architecture 2.2 TCP and UDP Transport Protocols & Handshake Mechanics 2.3 ICMP Protocol, Network Diagnostics & Error Messages 2.4 Network Topologies, Switched Media & VLAN Segmentation 2.5 Network Media, Ethernet Standards & Physical Topologies

3 Chapter 3: Cryptography & Secure Communication Protocols

3.1 Symmetric & Asymmetric Cryptographic Algorithms 3.2 Cryptographic Hash Functions, MACs & Digital Signatures 3.3 Secure Protocols: SSL/TLS, IPsec & SSH

4 Chapter 4: Background Information Gathering & OSINT Reconnaissance

4.1 WHOIS Records, Domain Registrars & Autonomous Systems 4.2 DNS Infrastructure, Record Types & Zone Transfers 4.3 Search Engine Reconnaissance, Google Dorking & Information Leakage 4.4 Newsgroups, Mailing Lists & Public Archive Reconnaissance

5 Chapter 5: Networking Equipment & Infrastructure Protocols

5.1 Router & Switch Management: SNMP, SSH & Authentication 5.2 Layer 2 Protocols: ARP, CDP, STP, VTP & Redundancy 5.3 Core Network Services: DHCP, NTP & TFTP 5.4 Wireless Security (802.11) & VoIP Assessment 5.5 Out-of-Band Management, Console Access & Cisco Reverse Telnet

6 Chapter 6: Network Mapping, Nmap Techniques & Target Identification

6.1 Host Discovery Techniques & Ping Sweep Methodologies 6.2 Port Scanning Mechanics: TCP, UDP & Stealth Scans 6.3 OS Fingerprinting, Service Detection & Timing Templates 6.4 Firewall and IDS/IPS Evasion Techniques 6.5 Passive OS & Service Fingerprinting 6.6 Network Access Control Analysis & Firewall Rule Base Review

7 Chapter 7: Vulnerability Identification & Tool Output Analysis

7.1 Vulnerability Scanning Principles & Methodology 7.2 CVE Referencing, CVSS Scoring & Risk Prioritisation 7.3 Banner Grabbing, Service Verification & Manual Triage 7.4 Host Audit Techniques: Processes, Sockets, Patch Levels & Interesting Files

8 Chapter 8: Microsoft Windows Security Assessment & Active Directory

8.1 Active Directory Architecture & Domain Reconnaissance 8.2 Windows User & Group Enumeration via SMB & RPC 8.3 Windows Authentication: NTLM, Kerberos & Password Security 8.4 Windows Patch Management, Local Security & Common Services 8.5 Windows File System, Share & Registry Permissions 8.6 Desktop Lockdown, Citrix Breakout & Common Windows Applications

9 Chapter 9: Unix & Linux Security Assessment & Legacy Services

9.1 Linux/Unix Security Architecture, Permissions & Filesystem 9.2 Unix User Enumeration & Service Discovery 9.3 Network File System (NFS) & RPC Services Assessment 9.4 Legacy Unix Services: R-Services, X11, FTP & Modern SSH 9.5 Unix Remote Information Services: rusers, rwho, finger & systat 9.6 Unix Vulnerability Exploitation & Post-Exploitation Workflow

10 Chapter 10: Web Architectures, Technologies & Testing Methodologies

10.1 Web Server Architecture & the HTTP/HTTPS Protocol 10.2 Web Application Components, Frameworks & State Management 10.3 Web Reconnaissance, Content Discovery & Threat Modelling 10.4 Testing Authentication, Authorization & Session Management 10.5 Web Service Protocols: SOAP, REST & XML Messaging 10.6 Web APIs, Server Extensions & Client-Side Sub-Components

11 Chapter 11: Web Testing Techniques & OWASP Top Vulnerabilities

11.1 Input Validation Vulnerabilities & Parameter Manipulation 11.2 Cross-Site Scripting (XSS): Types, Impact & Defenses 11.3 Cross-Site Request Forgery (CSRF) & Client-Side Attacks 11.4 Command Injection, File Upload Vulnerabilities & API Flaws 11.5 Information Disclosure: Error Messages & Mark-up Leakage 11.6 Injection Beyond SQL: LDAP, XPath, Code & Template Injection 11.7 Source Code Review & Encoded/Cryptographic Value Analysis

12 Chapter 12: Database Security Assessment & SQL Injection

12.1 Database Architectures, Default Ports & Authentication 12.2 SQL Injection (SQLi) Foundations & In-Band Techniques 12.3 Blind SQL Injection & Database Enumeration 12.4 Database Attack Vectors, Stored Procedures & Hardening

4.4 Newsgroups, Mailing Lists & Public Archive Reconnaissance

Key Takeaways Explain This Topic AI

NNTP runs on TCP port 119 in cleartext and TCP port 563 for NNTP over TLS (NNTPS).

The Path: and NNTP-Posting-Host: headers of a Usenet article record the relaying servers and the posting client's host or IP address.

Message-ID headers embed the originating domain and frequently the internal hostname of the mail or news server that generated them.

Mailing list archives are the highest-yield source for verbatim internal configuration, because administrators paste real configs when asking for help.

Header-derived intelligence needs no packets sent to the target, so it is collected entirely within the passive phase of an engagement.

Last updated: September 2026

4.4 Newsgroups, Mailing Lists & Public Archive Reconnaissance

Two CPSA syllabus items sit squarely in this territory. C5 (NNTP Newsgroups and Mailing Lists) requires you to search newsgroups or mailing lists for useful information about a target. C6 (Information Leakage from Mail & News Headers) requires you to analyse those headers to identify internal system information. Both are pure passive reconnaissance : you query third-party archives, never the client's infrastructure, so nothing you do can be seen by the target's monitoring.

The underlying insight is simple and has not changed in thirty years. Technical staff ask for help in public, and they paste real data when they do. A firewall rule that will not match, a Kerberos error they cannot decode, an Exchange queue that keeps filling — the fastest way to get an answer is to post the actual output. Sanitising it properly is tedious, and it is very often done badly or not at all.

1. Usenet and NNTP Mechanics

Usenet is a distributed discussion system that predates the web. Articles are posted to hierarchically named newsgroups ( comp.security.firewalls , uk.telecom , microsoft.public.exchange.admin ) and flooded server-to-server until every participating server holds a copy.

The transport protocol is NNTP (Network News Transfer Protocol) , originally RFC 977 and now RFC 3977 .

Cleartext NNTP listens on TCP port 119. NNTP over TLS (NNTPS) listens on TCP port 563.

Articles use the same header/body structure as e-mail (RFC 5322 style), which is why the same header analysis applies to both.

Usenet's practical relevance today is as an archive . Google Groups absorbed the Deja News archive and holds decades of posts; independent archives and mirrors hold the rest. An engineer who posted a router configuration to comp.dcom.sys.cisco in 2003 is still findable, and organisations rarely renumber or rename their internal infrastructure.

The Modern Successors

For assessment purposes, treat these as the same class of source:

Source What accumulates there Search approach

Vendor / product mailing lists (e.g. oss-security , nginx , postfix-users ) Verbatim configuration files, version banners, error output Public archive search plus site-restricted search engine queries

Usenet / Google Groups Historic infrastructure detail, old internal hostnames Group and author search, then the raw article headers

Public issue trackers and forums Stack traces, connection strings, internal URLs in bug reports Search the target's domain and employee usernames

Q&A sites (Stack Overflow, Server Fault) Redacted-but-not-really configs, sample code with credentials Search by employee profile, then their question history

Job adverts and CVs Exact product versions, in-house application names, team structure Search the company name with product keywords

2. What to Search For

Work outward from identifiers you already hold from WHOIS, DNS and the corporate website:

Domain and subdomain strings — @example.co.uk , example.local , corp.example.com . Internal AD namespaces leak constantly in error messages.

Named individuals — the technical contact from WHOIS, the SOA RNAME mailbox, authors of the company's engineering blog. Then search those people's posting history across every source above.

Product and version strings — "Cisco ASA 5510" plus the company name; "Exchange 2016 CU23" plus the domain.

Internal hostnames and IP ranges — once you have one internal naming convention ( LON-DC-01 , 10.20.30.0/24 ) search for it directly; naming schemes are consistent across an estate.

Distinctive error strings — an application's unique exception text posted verbatim identifies both the software and often the stack trace path on disk.

3. Reading News and Mail Headers

This is syllabus item C6, and it is the part most candidates under-prepare. Both news articles and e-mail carry a header block that records the path a message took. Those records are written by intermediate servers, not by the author, so they are rarely sanitised.

  • Usenet Article Headers Path: news.bigisp.net!feeder.example.net!news.example.co.uk!not-for-mail
  • From: j.smith@example.co.uk (John Smith)
  • Newsgroups: comp.dcom.sys.cisco
  • Subject: ASA 5510 failover pair dropping state
  • Date: Tue, 14 Mar 2006 10:22:41 +0000
  • Organization: Example Manufacturing Ltd
  • Message-ID: <4415a2c1$0$8712$ba4acef3@nws-01.corp.example.co.uk>
  • NNTP-Posting-Host: 62.145.19.34
  • X-Newsreader: Microsoft Outlook Express 6.00.2900.2180

Header Intelligence it yields

Path: The chain of news servers that relayed the article, read right to left from the originating server. news.example.co.uk is the target's own news server.

NNTP-Posting-Host: The IP address or hostname of the machine that injected the article — frequently the poster's own workstation or the corporate NAT address.

Message-ID: Generated by the injecting server and conventionally contains its FQDN . Here it exposes an internal server naming convention, nws-01.corp.example.co.uk .

Organization: Confirms the employer even when the From address is personal.

X-Newsreader: / X-Mailer: Exact client software and build — a direct client-side attack surface and an indicator of the desktop build standard.

E-mail Headers

The same reading applies to any e-mail you can legitimately obtain — a mail to a public enquiries address, a mailing list post, an autoresponder reply, or a bounce message. Received: from mail.example.co.uk (mail.example.co.uk [62.145.19.20])

  • by mx.listserver.org with ESMTPS id 4Rk2Jd1pqz
  • for <list@listserver.org>; Tue, 14 Mar 2026 10:22:43 +0000
  • Received: from LON-EX-02.corp.example.local (10.20.30.52) by
  • LON-EDGE-01.corp.example.local (10.20.30.20) with Microsoft SMTP
  • Server (TLS) id 15.1.2507.39; Tue, 14 Mar 2026 10:22:41 +0000
  • X-Originating-IP: [10.20.31.117]
  • X-MS-Exchange-Organization-AuthAs: Internal

Read the Received: chain from the bottom upwards — the earliest hop is the innermost server. In this example the passive observer has just learned, without sending a packet:

  • the internal AD DNS suffix ( corp.example.local );
  • the internal RFC 1918 addressing scheme ( 10.20.30.0/24 for servers, 10.20.31.0/24 for clients);
  • the internal hostnames and roles ( LON-EX-02 mailbox server behind LON-EDGE-01 edge transport);

the exact Exchange build ( 15.1.2507.39 ), which maps to a specific cumulative update and therefore to a precise patch level;

the sender's workstation IP , via X-Originating-IP .

That build number alone is enough to determine whether the host predates the ProxyLogon or ProxyShell fixes.

Other Header Fields Worth Harvesting

X-Mailer: / User-Agent: — mail client and version.

X-Spam-* / X-Barracuda-* / X-Mimecast-* / X-Forefront-Antispam-Report: — identify the security gateway product in front of the mail estate, which tells you what filtering an eventual phishing exercise must survive.

DKIM-Signature: d= and s= — the signing domain and selector; the selector lets you fetch the public key via DNS and confirm key length.

Return-Path: and SPF/DMARC results — whether the domain can be spoofed, which is a finding in itself.

  • 4. Turning Archive Findings Into an Attack Path Public archive post Extracted fact Attack use
  • -----------------------------------------------------------------------------
  • "ASA 5510 failover pair..." -> Perimeter product + model -> Version-specific
  • vulnerability search
  • Message-ID @nws-01.corp... -> Internal naming scheme -> Subdomain and host
  • brute-force wordlist
  • Received: 10.20.30.52 -> Internal addressing plan -> Post-compromise
  • pivot targeting
  • X-Mailer: Outlook Express 6 -> Desktop build standard -> Client-side payload
  • selection
  • Pasted snmp-server community -> Live credential -> Direct device access

The last row is not hypothetical. Configuration snippets posted for troubleshooting routinely retain SNMP community strings, pre-shared key hints, ACL contents with real internal subnets, and occasionally enable secret hashes. Treat any credential recovered this way with care: finding it is passive OSINT, but using it against the client's systems requires that the host be in scope and the activity authorised by the Rules of Engagement.

5. Reporting and Remediation

Archive leakage is awkward to report because the information is often years old and cannot be recalled. Useful, actionable recommendations include:

A publication policy : staff must not post configuration, log or error output containing internal identifiers to public forums, and should use a sanitisation checklist when they must.

Header minimisation at the boundary : configure the mail edge to strip internal Received: hops and X-Originating-IP from outbound mail. Exchange Edge Transport and most secure e-mail gateways support header firewall rules that do exactly this.

Assume internal names are public : because they frequently already are, internal hostnames and RFC 1918 ranges must never be treated as a security control. Authentication and segmentation have to stand on their own.

Periodic self-OSINT : the client should run the same searches you did, on a schedule, and request removal where an archive operator permits it.