Known domains#

The known domains system tracks a large database of apex domains that the platform monitors over time. Unlike verified domains (which link a domain to a brand for display purposes), known domains are tracked for historical analysis and change detection.

What are known domains?#

Known domains are apex domains that administrators have added to the system for ongoing monitoring. The system periodically analyzes each known domain and stores the results. Over time, this builds a history of how each domain's DNS records, email security, and web security change.

This data is only available to administrators. Public users see live, real-time results for any domain they look up, but they do not see historical analysis data or change tracking.

How known domains differ from verified domains#

Feature	Verified domains	Known domains
Purpose	Show a brand badge on public lookup results	Track a domain's configuration over time
Visible to public users?	Yes — they see the brand badge	No — historical data is admin-only
Requires a brand?	Yes	No — brand is optional
Stores history?	No — only the current brand association	Yes — stores every analysis result
Detects changes?	No	Yes — flags when DNS records change

A domain can be both verified and known. Being verified controls the public display. Being known enables historical tracking.

Viewing known domains#

Go to Known Domains under Manage Data in the navigation.
You'll see a table of all tracked domains with their status, type, tags, and scan information.

Filtering and searching#

The known domains list supports several filters:

Filter	What it does
Search	Find domains by name (partial matches work).
Domain type	Show only domains of a specific type: verified, discovered, imported, or unknown.
Tag	Filter by tags assigned to domains (such as industry or category tags).
Status	Show only active or inactive domains.
Scan status	Filter by whether the domain has been scanned recently.

Viewing a domain's details#

Find the domain in the known domains list.
Click the domain name or the View button.

The detail page shows:

Domain information — Type, company name, tags, and status.
Current DNS records — The live NS, TXT, MX, and other records.
WHOIS data — Registration information.
Analysis history — A list of past analyses with timestamps, security scores, and whether changes were detected.
Scan history — When the domain was last scanned and the results.

Adding known domains#

Adding a single domain#

Known domains are typically added through bulk import (see below), but individual domains can also be added through the admin interface or API.

Bulk importing domains#

Go to Bulk Import Known Domains under Manage Data in the navigation.
Paste a list of domains into the text area, one domain per line.
Click Preview to see how many are valid, invalid, or already in the system.
Click Import to add the valid domains.

The bulk import tool:

Accepts up to 50 domains at a time.
Validates each domain before importing.
Skips domains that are already in the system.
Shows a count of successful and failed imports.

Known domain fields#

Field	What it stores
Apex domain	The registered domain name.
TLD	The top-level domain (like .com or .co.uk).
Is active	Whether the system is currently monitoring this domain.
First seen	When the domain was first added to the system.
Last checked	When the domain was last analyzed.
Check frequency	How often the system re-analyzes this domain (in hours). Default is 24 hours.
Priority level	How important this domain is: 1 (normal), 2 (high), or 3 (critical). Higher-priority domains are analyzed more frequently.
Brand	The associated brand, if any.
Estimated traffic	A rough traffic estimate: 0 (unknown), 1 (low), 2 (medium), 3 (high).
Domain type	How the domain entered the system: verified, discovered, imported, or unknown.
Source	Where the domain came from (such as "bulk-import" or "manual").

Change detection#

When the system re-analyzes a known domain, it compares the new results to the previous analysis. If anything changed — such as a new TXT record, a different MX provider, or a changed SPF policy — the system records the change with details about what was different and whether it improved or worsened the domain's security.

Administrators can review these changes from the domain's detail page to track configuration drift or detect unexpected modifications.

Scanning#

Known domains are analyzed on a schedule based on their check frequency and priority level. The system processes domains in batches, with higher-priority domains scanned first. See Enterprise scanning for details on how scanning works.