Domain Blocklist behaves differently depending on whether someone's creating a new record or editing an existing one, and that difference is the source of most confusion. Here's how to tell expected behavior from an actual bug.
"A profile still got created for someone on a blocked domain"
This is expected. Domain Blocklist doesn't stop the profile from being created, it strips the blocked email so it's never saved to the record. Open the profile and check the email field: it should be empty, or missing that specific address. If the blocked email is actually showing up saved on the profile, that's a real bug, see the next section.
"The blocked email is showing up saved on a profile anyway"
Cause: Usually one of: the domain was entered in the wrong format (see below), the email is on a subdomain of a blocked domain rather than an exact match (matching subdomains isn't confirmed, see How Domain Matching Works), or the record came in through an entry point Domain Blocklist doesn't cover.
Fix: Check the domain entry under Settings → General Settings → Domain Blocklist matches the email's domain exactly, for example competitor.com not @competitor.com or www.competitor.com.
"It's stripped when I add manually, but not from another source"
Cause: The record may have come in through an entry point outside the four covered by Domain Blocklist, such as a data import, a Zapier integration, or a migration tool.
Fix: Domain Blocklist currently covers manual add, the Chrome extension, AIRA Source, and the API. See Where Domain Blocklist Applies for the full list. If the record came in another way, it isn't covered yet.
"I'm trying to add an email to a profile and getting a blocked-domain error"
This is expected too. Editing an existing profile to add an email on a blocked domain is rejected outright, unlike creation, which strips the email silently. If you believe the domain shouldn't be blocked anymore, an Admin needs to remove it from Settings → General Settings → Domain Blocklist first.
"The record was already in Recruiterflow, email and all, before I blocked the domain"
Cause: Domain Blocklist only governs emails going forward, it doesn't retroactively strip emails that were already saved before you added the domain.
Fix: Find the existing record and remove the email manually if needed, or use Off Limits if you want to restrict outreach to it rather than edit it.
Still stuck?
Reach out to support with the domain you blocked and exactly what you saw, whether an email got saved when it shouldn't have, or an edit was blocked when it shouldn't have been, so it can be investigated.