Here's what to know about how Domain Blocklist behaves at the edges, including a few things that are still being confirmed.
Creation strips silently, edits get blocked with an error
This is the single most important behavior to know: adding a new candidate or contact with a blocked-domain email doesn't throw an error, the profile is created and the email is just left off it. Editing an existing profile to add a blocked-domain email is rejected outright with an error. The two don't behave the same way, and that surprises people who expect a hard stop in both cases.
Forward-looking only
Domain Blocklist doesn't retroactively strip emails already saved on existing profiles from before the domain was blocked. It only governs new emails going forward.
No limit on number of domains
There's no cap on how many domains you can add to the blocklist.
No confirmation step on removal
Unlike Off Limits, which uses a cool-off period, removing a domain from the blocklist takes effect immediately with no confirmation step or delay.
Subdomain matching
Blocking a parent domain does not block its subdomains. See How Domain Matching Works for more.
Audit trail
Recruiterflow does not log or notify Admins when a blocked email is stripped at creation. Rejected edits do show an inline error to the person making the edit, but that's not the same as an Admin-facing log.
Admin-only by design
Only Admins can view or edit the blocklist. This isn't currently configurable to other roles.