When to use this
Use this after you identify repeated bad traffic from the same source patterns.
How Verifence evaluates it
The account block list turns a repeated abuse pattern into an enforceable tenant policy. Rules can target one email, an email domain, an IPv4 or IPv6 address, a CIDR range, a blocked country, or a country allowlist.
Email rules
Block a specific normalized email address or every address from a domain.
Network rules
Block exact IPv4 or IPv6 addresses and CIDR ranges when abuse comes from a known network.
Country policy
Block selected two-letter ISO countries or create an allowlist that rejects known countries outside the permitted set.
Hit history
Matched requests are logged with the rule type, matched value, source, request IP, endpoint, and timestamp.
Privacy controls
Rules can remain private, and account-level sharing can be disabled when a tenant does not want to contribute entries to network data.
How to do it
- 01 Collect several related events and identify the narrowest stable attribute: one email, email domain, IP address, CIDR range, or country.
- 02 Open Block List, choose the matching rule type, enter the normalized value, and add a note explaining the evidence and intended scope.
- 03 Use country allowlists only for deliberately regional workflows; known countries outside the list are blocked while unknown country data is allowed.
- 04 Monitor the block-list hit history to confirm the matched value, request IP, endpoint, and timing correspond to the abuse pattern.
- 05 Remove or narrow rules that catch legitimate leads, and use the privacy controls when a client entry should not contribute to shared network data.
How to act on the result
Use an email or IP rule when the abusive identity is stable and narrowly scoped.
Use CIDR or email-domain rules only when evidence shows the wider source is abusive; these rules have a larger false-positive radius.
Use when a client has a clear geographic restriction and can tolerate rejecting every known request from that country.
Use for tightly controlled regional workflows. Requests with unknown country data are allowed rather than guessed.
Implementation notes
- Add a note explaining why a rule exists, then review the hit history to confirm it is stopping the intended traffic.
- Start with the narrowest rule that solves the problem. Broad domain, CIDR, or country rules can block legitimate leads.