Asset types
HTTP routes and endpoints are tracked separately and attached to the asset that serves them — see the Routes tab below.
Sources
Each asset is tagged with how Odin learned about it:- Manual: added by a member of your team
- Recon: discovered by Continuous Asset Discovery
- Import: added via CSV/JSON import
- Agent: discovered by Odin’s AI agent during a pentest run
Adding assets
There are two ways to add assets manually:- Add asset: click Add Asset in the page header, choose the type, and enter the value. You can also toggle Continuous Asset Discovery on at creation time.
- Import assets: click Import and upload a CSV or JSON file containing multiple assets. Files exported from the Assets page import as they are. Assets you already have are skipped, and the confirmation says how many were added. Imported assets are tagged Import; a status of Active, Inactive or Unverified is kept, and any other status from an export starts as Unverified.
Activating Continuous Asset Discovery
If your organisation has CAD enabled but hasn’t yet activated a subscription, a banner on the Assets page prompts you to start. Once active, you can toggle CAD on a per-asset basis as you add or edit them. See Continuous Asset Discovery for what CAD does and how it’s billed.Asset detail
Click any asset in the list to open the detail panel. The panel has five tabs:Overview
Key metadata about the asset:- Type, source, status, and creation date
- DNS data: A, AAAA, CNAME, and other resolved records (for domains and subdomains)
- HTTP data: response status, headers, redirects (for domains and subdomains)
- TLS data: certificate subject, issuer, expiry, and chain (for HTTPS endpoints)
- Open ports and services (for IPs): each open port Odin found, with its detected service, web server, frameworks, and whether it supports TLS. When an IP sits behind an edge provider with nothing useful to scan, a note explains why no ports are listed (see Infrastructure providers)
- Notes: a free-text field your team can edit; useful for owner / on-call info
- Monitoring toggle: turn CAD on or off for this asset
Tech
Technologies detected on the asset — web frameworks, CMSes, JavaScript libraries, analytics tools, server software, and so on. Useful for understanding your supply chain and tracking inventory of risky dependencies.Relation
A focused view of how this asset connects to other assets in your inventory:- Domain hierarchy: parent and child relationships in your domain tree
- Certificate sharing: other assets that share the same TLS certificate
- IP co-resolution: domains and subdomains resolving to the same IP
Routes
HTTP routes (paths and endpoints) Odin knows about for this asset. Click a route to open it, or use Add route to capture additional paths Odin hasn’t yet seen — useful when you know about an endpoint that’s not linked from any crawled page.Findings
All findings that reference this asset, with the same filter, sort, and detail experience as the main Findings page.Infrastructure providers
When Odin recognises that an IP belongs to a known cloud or edge provider, it marks the asset with a provider badge. The badge shows in the assets list and in the detail panel header, so you can tell at a glance who owns an address range. Odin labels Cloudflare, Google Cloud, AWS, and Azure by name. A provider badge marks who owns the range, not whether Odin scanned it:- Cloud compute (AWS, Azure, and Google Cloud, including its global load balancers) is labelled and still fully port-scanned, so its open ports appear in the Overview tab as usual.
- Front-end edge ranges (such as Cloudflare, CloudFront, and Front Door) host many customers behind shared addresses, so a port scan reveals nothing about your asset. Odin labels these and skips the scan. When that happens, the Open ports section shows a note saying the IP is edge infrastructure rather than a port list.
A badge on its own never means scanning was skipped. The skipped-scan note appears only on an edge-provider IP that has no recorded open ports.
Tree view
The list is a domain tree, not a flat table. Subdomains sit under the closest parent that is already in the inventory (staging.api.example.com under api.example.com, then under example.com). When the parent domain is not in the inventory, sibling hosts that share a root still group together. An IP nests under a hostname only when that hostname is the only asset that resolves to it.
The tree loads every asset that matches your filters at once, so the number next to a collapsed domain is its full count of subdomains. If your organisation has more than 5,000 matching assets, Odin shows the first 5,000 and says so above the list. Search or filter to see the rest; counts then cover the assets shown.
Use the visibility control next to the filters:
- Everything (the default): show every asset, including those with no findings. Switching to this view does not expand the tree — expand a row yourself when you want its children.
- With findings: show only assets that have findings. Parents needed to keep those assets in the tree stay visible, with a quieter name and metadata so they read as context rather than matches. Expand controls stay at full strength. Branches that lead to a finding stay open.
Filtering and search
Use the filters at the top of the Assets page to narrow your view:- Type: show only domains, subdomains, or IPs
- Status: filter by active, inactive, or unverified
- Source: filter by Manual, Recon, Import, or Agent
- Search: free-text search across asset names and metadata. Press / to jump to it
- Sort: order by value, last seen, or date added
- Presets: use the bookmark menu to save the current filters under a name and apply them later. Applying a preset replaces the filters you have, so it shows the same list each time. Presets are kept in your browser for you and the organisation you saved them in. Presets saved on this browser before that appear under Earlier presets on this browser: add them to your presets or discard them.