Tags let you label domain names with custom key-value pairs so you can filter dozens or hundreds of domains in seconds — by owner, department, service, or any dimension you define.
With tags, you can:
-
Filter domain names by any combination of attributes (multi-tag filtering uses AND logic).
-
Group domain names for management and operational reporting.
-
Search across 100+ domain names without scrolling through a flat list.
The following example walks through a company with 100 domain names spanning three departments, each with its own services and executive owner.
Set up tags
Each tag consists of a key and a value. The company defines three keys for the dimensions most relevant to daily management:
| Key | Values |
|---|---|
| Department | E-commerce, Gaming, Entertainment |
| Service | Marketing, Game A, Game B, Post-production |
| Executive | Bob, John, Tom |
The following table shows how those tags map to each domain name:
| Domain name | Department | Service | Executive |
|---|---|---|---|
| domain1 | E-commerce | Marketing | Tom |
| domain2 | E-commerce | Marketing | Tom |
| domain3 | Gaming | Game A | Bob |
| domain4 | Gaming | Game A | Bob |
| domain5 | Gaming | Game B | John |
| domain6 | Gaming | Game B | John |
| domain7 | Gaming | Game B | John |
| domain8 | Entertainment | Post-production | Tom |
| domain9 | Entertainment | Post-production | Tom |
| domain10 | Entertainment | Post-production | Tom |
Filter domain names by tag
After tags are applied, you can filter domain names in the console by one or more tags. When you specify multiple tags, only domain names matching all tags are returned (AND logic).
Filter by a single tag
To find all domain names managed by Tom, filter by Executive: Tom. This returns domain1, domain2, domain8, domain9, and domain10.
Filter by multiple tags
To find domain names in the Gaming department that are managed by John, apply both tags at once: Department: Gaming and Executive: John. This returns domain5, domain6, and domain7.
Design your tag structure
The preceding example uses three dimensions — department, service, and owner — but you can define any keys that fit your organization. Common tagging dimensions include:
-
Technical: environment type (production, staging, development), region, service version
-
Business: cost center, business unit, project
-
Operational: owner, on-call team, criticality level
Start with the questions your team asks most often — "Which domain names does this team own?" or "Which domains support this service?" — and build your keys around those queries.