zintara.io

Lead management · Practical guide

Blocklist domain matching in Zintara: exact domains and subdomains

Zintara's current send-time blocklist compares recipient domains exactly. A block for example.com should not be assumed to cover mail.example.com automatically.

Reviewed · Examples are illustrative

Who this helps: Operators preparing contact data, exclusions and campaign audiences.

Define the decision

Domain suppression is broader than one address but narrower than a wildcard over every related organization. Define the intended scope: one person, all addresses at an exact domain or several verified domains belonging to an account. Keep that scope in the reason and review record.

Work through the procedure

  1. Extract the recipient domain after the final @ and compare it with the proposed entry.
  2. Choose an email entry for one address and a domain entry for the intended domain-wide exclusion.
  3. List subdomains and alternate domains separately when they belong in scope. Verify relationships rather than blocking similarly named businesses.
  4. Review the saved normalized value. Supported pasted URLs can be normalized, but normalization is not wildcard or organization-graph matching.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Entry: example.com
[email protected] → exact domain match
[email protected] → different domain; review separately
Entry: [email protected]
[email protected] → different address unless a domain entry also applies

Read the result

A parent domain can look related to a subdomain without matching the current lookup. Conversely, a domain entry can exclude many people, so its breadth should reflect a deliberate decision. If you intended to suppress one person's address, adding the entire company domain changes the scope and deserves a separate review.

Check before moving on

  1. Inspect spelling, trailing punctuation and saved entry type.
  2. Do not enter wildcard syntax unless explicitly supported.
  3. Record alternate domains deliberately included or excluded.

Limits and next action

These details were checked against Zintara's current normalization and lookup code, not inferred as a universal email-platform rule. If an inherited entry cannot be edited in this workspace, manage it through the owning context. Do not recreate contacts to bypass that ownership boundary.

Source: Zintara product and contact workflow context

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow