How to find all domains owned by your company

No single source lists every domain a company owns. The reliable way is to combine the records you already have with public registration and certificate data, confirm which names are really yours, and then keep the list current, because it starts going out of date the day you finish it.

Why nobody has the full list

Domains are registered over many years, by many people. Marketing registers a name for a campaign. A developer registers one for a test and pays with a personal card. An acquired company arrives with its own registrar account. The legal team buys variants of the brand to keep them away from others. The registrations end up at several registrars, under different accounts and contact names.

Every one of those domains is still on the internet, whether or not anyone remembers it. It can point to an old server, carry a forgotten website, or expire and be registered by someone else. You cannot review or protect a domain that is not on your list, so the list comes first.

Step 1: Start inside, with the records you already have

Most of the answer is already inside the company, spread across teams. Collect it before you look outside.

  • Registrar accounts. List every account at every registrar and export the domains in each. Ask finance for invoices and card statements that mention a registrar: renewals reveal accounts nobody remembers.
  • DNS hosting and cloud accounts. Every domain someone set up has a DNS zone somewhere. List the zones in your DNS providers and cloud accounts.
  • Email and sign-in services. These keep a list of the domains added to them. In the Microsoft 365 admin center it is under Settings, then Domains. In the Google Admin console it is under Account, then Domains, then Manage domains. The list also holds names the provider created for you, such as yourcompany.onmicrosoft.com. Those are not domains you registered.
  • Certificate orders. Orders at your certificate authorities name the domains they were issued for.
  • Marketing, legal and brand teams. Ask for campaign sites, product names, and names bought to protect the brand.
  • Acquisitions and subsidiaries. Each legal entity has its own registrations. Repeat these steps for each one.
  • Renewal notices. Shared mailboxes such as hostmaster@ or admin@ collect expiry and renewal emails for domains nobody listed.

Step 2: Fill the gaps from outside

Internal records miss whatever was registered outside the usual accounts. Public data helps you find those names. Each source below has a blind spot, so use them together.

Registration data

Every domain has a registration record. For generic top-level domains such as .com, ICANN made RDAP the definitive source of registration data on 28 January 2025, replacing WHOIS. Its ICANN Lookup tool shows the record for any domain you enter: the registrar, the dates and, where it is published, the registrant. Country-code domains such as .de or .uk are looked up at their own registries.

A lookup answers one question: who registered this domain? Your question is the reverse: which domains did we register? Answering it takes a database built from registration records and searched by registrant name, organization or email. This is called a reverse WHOIS search, and commercial services offer it.

Its blind spot is privacy. Under ICANN's registration data policy, registrars redact personal contact data where the law requires it, and they may redact the organization name as well. Domains registered through a privacy service, or under a former company name, will not match either.

Certificate Transparency

Publicly trusted TLS certificates are recorded in public logs that anyone can query, and Chrome and Safari require proof of that logging before they accept a certificate. crt.sh, a public certificate search, lets you search those logs in two useful ways:

  • By organization name. This finds certificates that carry your company's name. Organization-validated certificates must include it. Domain-validated certificates cannot, so this search misses every domain that only has that kind.
  • By each domain you already know. A certificate can cover several names, so a certificate for one of your domains sometimes lists a sibling domain you did not have. The reverse also happens: a certificate that a CDN or software provider shares between customers lists other companies' domains next to yours.

DNS and name variants

Check your main name under other extensions, such as .net, .io and the country codes you operate in. A lookup shows whether a variant is registered and through which registrar.

Then compare each candidate with domains you know are yours. The same name servers, the same mail setup or a redirect to your main site all point to the same owner. These are hints, not proof: shared hosting and shared mail providers produce the same hints for unrelated companies.

What each source finds, and what it misses

Registrar accounts and invoicesFinds: Domains registered through accounts the company knows aboutMisses: Accounts opened by other teams, by acquired companies or by individuals
DNS hosting and cloud accountsFinds: Every domain that has a zone in your accountsMisses: Domains hosted elsewhere, and domains that were registered but never set up
Email and sign-in servicesFinds: Domains added for mail or sign-inMisses: Domains never used for either
Registration data: lookup and reverse WHOIS searchFinds: Domains registered under your organization's name or emailMisses: Redacted records, privacy services, former company names
Certificate Transparency logsFinds: Domains on certificates that carry your organization's name, and sibling names on shared certificatesMisses: Domains that only have domain-validated certificates (in an organization search), and domains with no certificate; a provider's shared certificate lists other customers' domains
DNS checks and name variantsFinds: The same name under other extensions, and hints that a candidate is yoursMisses: Unrelated names; shared providers give false matches

Step 3: Confirm what is really yours

You now have a list of candidates. Sort each one into ours, not ours, or not sure.

Control is the proof. A domain is yours if someone in the company can sign in to the registrar account that holds it, or can change its DNS records. If you can change a domain's DNS but cannot find its registrar account, the registration is held by someone else, such as an agency or a former employee. Find that account before the next renewal.

Matching name servers, a matching certificate or a familiar logo are reasons to look closer, and nothing more. Companies with similar names exist, and so do people who register look-alike names on purpose.

For every domain you confirm, note the legal entity that owns it and the registrar account it sits in. Take the "not sure" names to the team most likely to know. A name that carries your brand but is held by someone else is a matter for your legal team, not a line in your inventory.

Step 4: Turn the list into an inventory

A list of names is not yet useful. For each domain, record five things:

  • the registrar and the account that holds it,
  • the expiry date, and whether it renews automatically,
  • where its DNS is hosted,
  • the team that owns it,
  • what it is for.

The last two matter most. A domain with an owner and a purpose can be reviewed: someone can say whether it is still needed. A domain nobody can explain is a candidate to retire. Before you let one go, check that no mail, redirect or subdomain still depends on it, and decide on purpose whether to keep it parked or release it.

This is the same rule that reduces an attack surface as a whole: everything you expose has an owner and a reason, or it is closed. How to reduce your external attack surface covers that method.

Step 5: Keep it current

The list starts to age as soon as it is done. Teams register new domains, the company buys another company, a registration expires. Review the list of root domains at least twice a year, and again after every acquisition.

What sits under those domains changes far more often. A new subdomain, server or certificate can appear on any day, and no spreadsheet keeps up with that. That part needs monitoring, not a periodic review.

How Vulmon Recon keeps the list current

Vulmon Recon starts where the list ends. You add each root domain you confirmed as a seed, a starting point for discovery, along with your IP ranges. From each seed, Recon works outwards to find the domains, subdomains, IP addresses, ports, websites, technologies and certificates you expose. A domain seed covers that name and the names under it.

  • New names. Recon looks for the names under each domain in Certificate Transparency logs and in DNS, and it keeps looking. A new name on a certificate logged for one of your domains is picked up, even if you did not request that certificate.
  • A decision for everything found. Newly discovered assets arrive as scope pending. For each one, Recon shows how it was found and whether it is likely yours. It also takes a first look at the asset and shows how many open ports, websites, technologies and certificates it found. The details open when you put the asset in scope. You mark each one in scope, out of scope or a false positive.
  • Cloud accounts. Connect AWS, Azure, GCP or Cloudflare with read-only access and Recon lists the externally exposed resources in them. Public DNS zones are among the resource types it lists, which helps with the second item of step 1.
  • Owners and reasons. In asset review, every in-scope domain, IP address and port gets a business justification and an owner, or it is closed. Tags and owners are set on domains, IP addresses and seeds, and flow down to the websites and ports underneath them. Names found later under a tagged domain inherit its tags and owners. A tag such as "acquired" keeps a bought company's domains together.
  • Changes. You are told when a new asset is discovered or an asset's reachability changes: in the app, by email, in Slack or in Microsoft Teams.
  • Your list stays portable. Every inventory list can be downloaded as CSV or JSON.

Recon Essentials is the free, self-hosted edition. It covers discovery and inventory and runs with Docker on your own machine. The hosted product adds vulnerability findings, cloud connectors, integrations, the API, single sign-on and scheduled reports.

Frequently asked questions

What people ask when they start this work.

Is there one place that lists every domain a company owns?

No. Registration records are held by many registries and registrars, public lookups work one domain at a time, and contact details are often redacted. The reliable way is to combine the company's own records, such as registrar accounts, invoices and DNS zones, with public registration and certificate data.

Can I find all of a company's domains with WHOIS?

Only partly. A lookup tells you who registered one domain, where that is published. For generic top-level domains the lookup now runs on RDAP, which replaced WHOIS on 28 January 2025. Listing every domain registered by one organization takes a reverse WHOIS search, which commercial services offer, and it misses records that are redacted or registered through a privacy service.

How do Certificate Transparency logs help find domains?

Publicly trusted TLS certificates are recorded in public logs that anyone can query. Searching them by your organization's name finds certificates that carry it, and searching by a domain you know can reveal sibling domains listed on the same certificate. Domain-validated certificates carry no organization name, so search both ways. A certificate that a provider shares between customers also lists other companies' domains, so confirm every name you find.

How do I know a domain I found is really ours?

Control is the proof: someone in the company can sign in to the registrar account that holds the domain, or can change its DNS records. If you can change the DNS but cannot find the registrar account, the registration is held by someone else, so find that account before the next renewal. Matching name servers, mail setup or a redirect to your main site are only hints, because unrelated companies share the same providers.

How often should the domain list be reviewed?

Review the list of root domains at least twice a year and after every acquisition. What sits under those domains, such as subdomains, servers and certificates, changes far more often and needs continuous monitoring.

What is the difference between finding domains and finding subdomains?

A root domain is a name the company registered, such as example.com. You find root domains through registrar accounts, registration data and certificates. Subdomains are the names under a root domain, such as shop.example.com. They are found in Certificate Transparency logs and DNS, and they change much more often. The domain list is the starting point for finding them.

What does Vulmon Recon do in this process?

It starts after you have your root domains. You add each one as a seed, and Recon finds the names under it together with their IP addresses, ports, websites, technologies and certificates, then keeps scanning as they change. Recon Essentials, the free self-hosted edition, covers this discovery and inventory.

Start with the domains you know

Add the domains you have confirmed and see what is under them.