Skip to main content

How Domain Matching Works

The matching logic behind Domain Blocklist, and what happens differently depending on whether a match is found at creation or during an edit.

Written by Amogh Balikai

Domain Blocklist matches on the domain portion of an email address, the part after the @. Understanding exactly how that matching works helps you predict what will and won't get caught.

Exact domain matching

When you add competitor.com to the blocklist, Recruiterflow checks emails for that exact domain. An email like jane@competitor.com matches.

Case-insensitive

Matching isn't case-sensitive. Jane@Competitor.com matches a blocklist entry for competitor.com just as much as an all-lowercase email would.

What happens when a match is found

What Recruiterflow does with a matched email depends on when the match happens:

  • Creating a new candidate or contact: the profile is still created, but the matched email is stripped and not saved to the record.

  • Editing an existing profile: the edit is rejected outright and Recruiterflow shows an error, rather than silently dropping the email.

See Where Domain Blocklist Applies for entry-point-specific detail.

Did this answer your question?