A company’s public footprint can extend well beyond the website in its assessment request. Old domains, staging hosts, campaign sites, and vendor portals are easy to miss. Compare the internal inventory with independent discovery before deciding what the next test will cover.
Build the asset list first, then prioritize and authorize the testing scope.
Why this step gets skipped, and why that's expensive
The main website and product application are useful starting points. Add assets introduced through acquisitions, campaigns, former employees, and vendor projects. Ask who maintains each one now.
Certificate transparency, passive DNS, and subdomain discovery can reveal assets missing from internal records. Attackers can use the same sources. Investigate forgotten hosts because they may have missed maintenance and access reviews.
Documenting primary domains
List primary domains, regional variants, defensive registrations, and earlier brand names. Record the registrar, DNS owner, current destination, and whether each domain serves content or redirects. Check that the business controls renewal and recovery.
Subsidiaries and acquired brands
Include subsidiaries and acquired brands, even when they still use separate hosting and vendors. Identify whether their security ownership transferred during integration or remains with another team.
Documenting this layer means listing every subsidiary and acquired brand, confirming who currently owns security responsibility for each one's digital footprint, and being explicit about whether that ownership was ever formally transferred or just quietly assumed. An acquired company's legacy website, still running on infrastructure nobody from the parent company has ever logged into, is a common and completely avoidable finding.
Marketing websites and campaign microsites
Ask marketing and agencies for campaign domains and microsites. Some may remain live after the campaign and maintenance contract end. Assign a current owner or plan retirement.
This category is a recurring finding precisely because it falls into an ownership gap. IT doesn't know it exists because marketing built it directly with an agency. Marketing considers the project finished the day the campaign ends. The agency's contract usually ended with it too. The site itself, meanwhile, is still sitting on the internet, often running outdated CMS software or plugins nobody's touched since launch.
Forgotten subdomains
Look for staging and test hosts, sales demos, retired products, and one-off engineering projects. Compare their current DNS and responses with the original purpose and owner.
Use certificate transparency to find recorded hostnames and passive DNS to inspect historical destinations. Reconcile discoveries with the internal list. A historical record is a lead to check, not proof that the service is still live.
Externally hosted services
Include vendor-hosted support, status, developer, careers, knowledge-base, and billing services using company domains. Record the provider, account owner, and data handled by each.
Review vendor-hosted services as part of the company’s public footprint. Record the provider, account owner, data flow, and available security evidence. Clarify which configuration and access decisions remain with your team.
Building the actual inventory
Maintain one inventory with the asset, purpose, internal owner, provider, review date, and testing status. Investigate missing ownership and unclear scope instead of letting those entries disappear from the next assessment request.
Why this determines whether your next assessment means anything
A clean report applies to its tested scope. It does not cover forgotten sites that never reached the asset list. Keep exclusions visible and agree how newly discovered assets affect the engagement.
If the engagement covers ten assets, select them using their data, reachability, and business role. A larger footprint may need a broader scope or a staged testing plan. Discovery gives you the information to make that choice.
Why this isn't a one-time exercise either
Update the inventory when a domain, campaign, project, or vendor service is added or retired. Review it before each scheduled assessment so the test list follows the systems still in use.
Where to start
Start with registration and DNS records, ask each business team about hosted services, and reconcile the answers with discovery. Resolve ownership before scheduling the test, and keep the untested assets in view.