Domain Blocklist exists because search firms routinely sign agreements that restrict who they can recruit from. Here are the situations where it's most useful.
Client no-poach agreements
When you sign a client, you often agree not to recruit from that client's own company for the duration of the engagement, or sometimes indefinitely. Blocking the client's domain means nobody on your team ends up with a saved email for someone at that company, whether adding a new record or editing an existing one.
Competitor or partner restrictions
Some engagements come with restrictions on recruiting from named competitors or partners of the client, not just the client itself. Add each of those domains too.
Preventing accidental cross-contamination between searches
If you're running multiple searches for competing clients at once, blocking each client's domain while working the other's search reduces the risk of an internal mix-up ending up with a saved contact detail.
Protecting your own bench
Some firms block their own placement clients' domains to avoid saving contact details for candidates they've already placed, protecting the relationship and any replacement guarantee period.
Enforcing team-wide compliance automatically
Instead of relying on every recruiter to remember which companies are off-limits, Domain Blocklist enforces the restriction automatically the moment someone tries to save an email on that domain, whether that's adding a new profile or editing an existing one, across manual add, the Chrome extension, AIRA Source, and the API.