Domain Security Info
Analytics and Reporting
Updated May 1, 2026, 8:24 AM
The analytics system tracks how the public tool is used and how it performs. All analytics data is only visible to administrators โ public users do not see any of this information.
Dashboard statistics#
The dashboard shows high-level counts of everything in the system:
| Metric | What it shows |
|---|---|
| Total brands | How many brand entries exist. |
| Total TXT tags | How many TXT record patterns are set up. |
| Total MX tags | How many MX record patterns are set up. |
| Total NS tags | How many NS record patterns are set up. |
| Total verified domains | How many domains have brand associations. |
| Total IP prefixes | How many known IP address ranges are tracked. |
Request tracking#
Every domain and IP lookup on the public website is recorded. Each request captures:
| Field | What it records |
|---|---|
| Domain | The domain or IP address that was looked up. |
| Apex domain | The apex domain extracted from the query (for subdomains). |
| Timestamp | When the lookup happened. |
| Country, region, city | The approximate location of the person who made the request. This comes from Cloudflare request headers. |
| Is verified domain | Whether the domain is in the verified domains database. |
| Brand | The brand associated with the domain, if any. |
| Has TXT/MX/NS tags | Whether the domain's records matched any known tags. |
| Has WHOIS data | Whether WHOIS data was available. |
| WHOIS cache hit | Whether the WHOIS data came from the 24-hour cache or required a fresh API call. |
| Response time | How long the full response took, in milliseconds. |
| DNS lookup time | How long the DNS queries took, in milliseconds. |
| WHOIS lookup time | How long the WHOIS lookup took, in milliseconds. |
| Error status | Whether an error occurred, and what kind. |
The system also records the client IP address and browser user agent for debugging and abuse prevention.
Daily statistics#
The system calculates totals once per day:
| Metric | What it shows |
|---|---|
| Total requests | How many lookups happened that day. |
| Unique domains | How many different domains were looked up. |
| Verified domain requests | How many lookups matched a verified domain. |
| WHOIS cache hits | How many WHOIS lookups came from cache. |
| WHOIS API calls | How many fresh WHOIS API calls were needed. |
| Error count | How many requests returned errors. |
| Average response time | The mean response time for the day, in milliseconds. |
| Peak hour | The hour of day (0โ23) with the most traffic. |
| Peak hour requests | How many requests happened during the busiest hour. |
Popular domains#
The system tracks the most-requested domains over different time periods:
| Period | What it covers |
|---|---|
| Daily | The most popular domains today. |
| Weekly | The most popular domains this week. |
| Monthly | The most popular domains this month. |
Each entry shows the domain name, how many times it was looked up, its rank, the associated brand (if any), and whether it is a verified domain.
Brand analytics#
See how often each brand appears in lookups:
| Metric | What it shows |
|---|---|
| Domain count | How many unique domains are associated with this brand. |
| Request count | How many lookups involved this brand. |
| TXT tag usage | How many times this brand's TXT tags matched records. |
| MX tag usage | How many times this brand's MX tags matched records. |
| NS tag usage | How many times this brand's NS tags matched records. |
Brand analytics are available by day, week, and month.
Tag usage analytics#
See how often individual tags match records in lookups:
| Metric | What it shows |
|---|---|
| Tag type | Whether the tag is TXT, MX, or NS. |
| Tag pattern | The pattern text. |
| Match count | How many times this tag matched a record. |
| Domain count | How many different domains triggered this tag. |
Use this to find out which tags are most useful and which may need updating.
Geographic analytics#
See where requests come from:
| Metric | What it shows |
|---|---|
| Country | How many requests came from each country. |
| Region | How many requests came from each state or region. |
| City | How many requests came from each city. |
| Error rate | The error rate for each location. |
| Response time | The average response time for each location. |
Performance monitoring#
The analytics data helps you spot performance problems:
- High average response time may mean DNS or WHOIS API calls are slow.
- Low WHOIS cache hit rate may mean many different domains are being looked up for the first time, or the 24-hour cache is not covering enough queries.
- High error rate may point to API rate limiting, DNS resolution failures, or other service issues.
Response time breakdown#
Each request records three timing measurements:
| Measurement | What it covers |
|---|---|
| DNS lookup time | How long it took to resolve all DNS records (NS, TXT, MX, A, AAAA, DMARC, MTA-STS, TLS-RPT). |
| WHOIS lookup time | How long the WHOIS data took to retrieve (0 milliseconds if it came from cache). |
| Total processing time | The full request time, including tag matching, page generation, and all other processing. |
Data integrity checks#
The system runs periodic checks to make sure the database is consistent:
| Check | What it looks for |
|---|---|
| Foreign key validation | Confirms that all brand references in tags, domains, and prefixes point to brands that actually exist. |
| Record count monitoring | Watches for unexpected changes in how many records each table contains. |
| Orphaned records | Finds records that reference brands or domains that have been deleted. |
You can view integrity check results through the stats API at /api/v1/stats/integrity.
How to view analytics#
- Go to Analytics under System in the navigation.
- Choose a time period using the date range selector.
- Switch between tabs to see different views: requests, brands, tags, and geography.
You can also go to Stats for an overview of system-wide counts and recent activity.