<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Methodology on </title>
    <link>/categories/methodology/</link>
    <description>Recent content in Methodology on </description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 01 Sep 2025 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="/categories/methodology/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Apex-Hunting 101: How to Expand Attack Surface by Finding Hidden Company Domains (Case Study)</title>
      <link>/blog-posts/apex-hunting-101/</link>
      <pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate>
      
      <guid>/blog-posts/apex-hunting-101/</guid>
      <description>Goal: turn a single target into a wide, defensible attack surface by discovering apex domains owned by the company, its acquisitions, and its sub-organizations—using only open sources.
 Great bugs often live just outside the obvious example.com. If you can map acquired brands and subsidiaries, you’ll uncover older tech stacks, forgotten portals, and regional sites that are still very much in scope for “wide-scope” programs.
Below is the exact recon playbook I use.</description>
    </item>
    
  </channel>
</rss>