Is Zix still a separate company?

No. OpenText's Zix legacy page says Zix is formally part of the OpenText family. Follow the sending organization's documented support route for account or recipient help.

Is Zix email security the same as email encryption?

Not exactly. The Zix name can appear across legacy services and support resources. The current OpenText Core Email Encryption page is the relevant product evidence when the question concerns policy-based encryption of outbound email. Confirm the actual product and policy with the operating organization.

Does an encrypted Zix message prove that the sender is legitimate?

No. Encryption can protect message content under a policy, but it does not prove that the visible From domain is authorized. Check SPF, DKIM, and DMARC evidence separately when sender-domain identity is the question.

Can a DMARC check show whether Zix encrypted a message?

No. DMARC evaluates author-domain authentication and publishes a requested handling policy for failed validation. It does not report an encryption provider's tenant policy or prove whether a specific message was encrypted.

Should a recipient use a link in a Zix notification?

Only after confirming that the sender and message are expected. Use the sending organization's support route if you need help opening encrypted email. Do not use a message notification as proof that the sender is trustworthy.

Zix email security: what the name means today

Zix email security is a legacy name now represented by OpenText Cybersecurity. OpenText says Zix is formally part of its family while its established customer portals remain available; its current Core Email Encryption page describes policy-based protection for outbound email. Encryption protects confidential content, but it does not establish that a message using your domain is authorized. Keep SPF, DKIM, and DMARC in scope for the separate job of domain authentication.

At a glance

Quick takeaways

Zix is formally part of OpenText, while established Zix customer portals remain available.
The current encryption offering applies actions according to the organization's content and DLP policies.
Encryption policy and sender-domain authentication answer different security questions.
A public domain check cannot confirm a Zix tenant's policy or the outcome of one encrypted message.

What does Zix email security refer to today?

OpenText's Zix legacy page says Zix is formally part of the OpenText family and directs customers to its OpenText Cybersecurity portfolio. It also says that the established support and account portals remain available. That is why a recipient, administrator, or procurement record may still use the Zix name while current product information appears under OpenText.

For a recipient, confirm the sender and follow the sending organization's support guidance. For an administrator, treat the name on an old portal, message notification, or documentation link as a product-context clue, not proof of the exact service tier, policy, or message state in use.

What does the encryption service do?

OpenText's current Core Email Encryption page describes DLP filters and policy actions that can encrypt, quarantine, or block email. It also describes delivery choices and reporting on encryption triggers and message handling. The exact trigger and action remain tenant-specific, so only the organization that operates the service can confirm why a particular message was handled a certain way.

The useful distinction is simple: encryption protects the message content according to policy. It does not, by itself, decide whether the visible From domain is a legitimate sender identity.

What encryption does not establish

RFC 9989 defines DMARC as a way for a domain owner to validate use of its author domain, state a handling preference for failed validation, and request reports. In practical terms, encryption and authentication work alongside each other, but neither replaces the other.

SPF publishes which hosts are authorized to use a domain in SMTP HELO and MAIL FROM identities, as specified in RFC 7208.
DKIM provides a signed identifier whose public key can be retrieved from the signing domain, as specified in RFC 6376.
DMARC applies alignment and publishes the domain owner's requested handling for failed validation.

If an encrypted message arrives, do not infer from encryption alone that its visible From domain passed DMARC. If a message passes DMARC, do not infer that its content was encrypted. Those are separate observations.

A practical way to sort the evidence

Use the evidence object below before opening a support request or changing DNS. It keeps a vendor-policy question separate from a domain-authentication question.

Technical exampletext

Observed issue: "This message mentions Zix" or "this message was encrypted"
Need to know the current product context?
  Read the current OpenText legacy and product documentation.
Need to know why one message was encrypted, quarantined, or blocked?
  Ask the organization that operates the OpenText or Zix policy.
Need to inspect a domain's public authentication posture?
  Check SPF, DKIM, and DMARC separately.

For the third path, run the domain through Palisade's Email Security Score. It can inspect public authentication records, but it cannot prove a tenant's encryption policy, a recipient's portal experience, or the handling of one particular message.

Evidence