MX2 White Rabbit Email Gateway, Wazuh Demo and Legal Precedent Workflow

Legal-grade secure communications and monitoring

Secure mail, Wazuh monitoring, legal precedents and private client workspaces.

MX2 protects email with filtering, quarantine, relay controls and disclosure review. The same environment can support Wazuh monitoring, private client chat and email, legal precedent templates, and WireGuard-only access for clients who need security beyond ordinary web hosting.

This public page shows preview and public-safe information only. No client material, mail content, security event detail, legal advice, quarantine content or external email sending is exposed from this site.

Live gateway activity

Public counters are safe summaries only. They do not include senders, recipients, subjects, message IDs, client names, matter names or quarantine contents.

-Messages processed in the last 24 hours

-Spam, malware and policy blocks in the last 24 hours

-Messages held for quarantine review this week

-Clean delivery rate after checks

Spam filtering

- spam messages blocked before inbox delivery.

Open relay protection

- unauthorised relay attempts rejected.

Policy and privilege holds

- messages held for disclosure or review policy.

Wazuh monitoring demo and trial onboarding

White Rabbit can provide a monitored trial path for clients who want endpoint visibility, security reports and a controlled introduction before moving to a permanent managed environment.

Install app preview

A client installer can prepare the endpoint, enrol the Wazuh agent, apply the correct group and show what monitoring is being enabled before anything is deployed.

Trial group

The intended trial group can be mapped to limited retention, limited permissions and demo reporting. Group discovery is pending before this is wired live.

Seven-day retention

Trial events can be configured for short retention, such as seven days, so a demo does not become an unnecessary long-term data store.

Email report preview

Reports can be generated and emailed to nominated contacts after the mail path and approval rules are confirmed. This page does not send reports.

Demo installer workflow

Identify client, device and approved monitoring scope.
Generate WireGuard or client access profile where required.
Install and enrol Wazuh agent into the correct group.
Confirm health, event flow and agent status.
Generate a short report showing endpoint posture and security findings.
Remove or expire trial data according to the trial retention rule.

Wazuh demo output

PREVIEW ONLY - WAZUH DEMO REPORT Client: Example Client Device: Example Windows endpoint Group: trial Retention: 7 days Report delivery: preview only, not sent Checks: - Agent installed: pending demo - Agent connected: pending demo - Critical alerts: pending live data - Authentication events: pending live data - Malware/security events: pending live data - Configuration posture: pending live data No live endpoint data is shown on the public site.

Private client workspace

For clients whose security matters, services can be delivered as a private online workspace instead of an ordinary public portal.

Internal chat

Client communication can remain inside the controlled environment rather than moving sensitive instructions into consumer messaging platforms.

Internal email

Client email can be handled inside the hosted environment with gateway controls, logging, retention rules and disclosure review.

WireGuard-only access

Workspace access can be restricted to registered WireGuard peers so services are not exposed directly to the public internet.

Client-to-client separation and anonymity-oriented design

Each client environment can be isolated so one client cannot see another client's services, data, traffic or identity. This is stronger than simply encrypting traffic: it combines private networking, identity separation, access control, logging policy, DNS control and service-level isolation.

No system should claim impossible absolute anonymity. The design goal is anonymity from other clients and public networks, strong compartmentalisation, and reduced metadata exposure, subject to lawful obligations, audit requirements and the client's chosen retention policy.

WireGuard peer registration before service access.
Separate client network scopes and DNS views.
No direct client-to-client visibility unless explicitly approved.
Internal chat and email retained inside the controlled workspace.
Security monitoring and reporting matched to the client's risk profile.
Optional short-retention trial mode before permanent onboarding.

Legal precedents and precedent templates

Many lawyers refer to reusable legal templates as precedents. This section uses that wording so lawyers searching for precedents, precedent templates or even "precidents" can find the workflow.

Precedent library

Store approved templates with instructions, review rules, jurisdiction, version history and allowed user roles.

Form-fill workflow

Collect structured answers, generate a preview, identify missing information and route the result for approval before sending.

Privilege-aware delivery

Completed forms should be sent only through controlled Vault or authorised user workflows, not casually emailed to external parties.

Precedent type	Preview status	Controls shown
Simple Will instruction precedent	Preview only	Client details, executors, beneficiaries, assets, special instructions.
Legal Aid application precedent	Preview only	Applicant details, matter type, urgency, financial position, supporting documents.
Email evidence receipt precedent	Future workflow	Headers, delivery proof, metadata, hash record, controlled recipient.
Disclosure approval precedent	Future workflow	Recipient authority, privilege warning, matter allocation, nominated approver.

Preview only: these examples are not legal advice and do not create legal documents. They show how a controlled form-fill workflow can collect information before lawyer or authorised-reviewer approval.

Preview-only form-fill demo

Select a precedent, enter sample information, then generate a preview and a draft email body. The Send function is intentionally disabled until external mail and approval routing are wired in.

Demo input

Generated preview

Select a precedent and enter sample details to generate a preview.

External sending is currently blocked. Later wiring should route drafts through Vault approval, matter/client permissions and MX2 policy checks before any delivery.

Why secure email and form controls matter

Email mistakes can create privacy, privilege and professional-risk issues. A gateway gives an organisation a controlled point to inspect, hold, approve and record risky communications before they leave the firm.

Reduces accidental disclosure

Outbound rules can hold messages where recipients, attachments, matter references or privilege markers indicate a risk of sending information to the wrong person.

Protects privileged material

Legal-privilege intelligence can identify sensitive communication patterns and require review before privileged client information is released externally.

Creates an audit trail

Review decisions, approvals, rejections and gateway events can be retained for revision history, compliance review and conference preparation.

White Rabbit domain security scorecard

Security features such as SPF, DKIM and DMARC help prove whether an email claiming to be from a domain should be trusted.

Feature	Status	Why it matters
SPF	Loading	Lists which mail systems are authorised to send for the domain.
DKIM	Loading	Signs email so tampering and unauthorised sending are easier to detect.
DMARC	Loading	Tells receivers what to do when anti-spoofing checks fail.
TLS	Loading	Encrypts email while it travels between mail servers where supported.
SSL Labs grade	Pending collector	Independent TLS configuration grade for the public web endpoint.

Check your own domain

Compare a domain against live public mail-security controls including MX, SPF, DMARC, MTA-STS, TLS-RPT, BIMI and common DKIM selector hints. Test-email verification is a later controlled mailcheck stage.

Domain security check

Enter a domain name to run safe public DNS and mail-policy checks. No email is sent and no private mailbox content is accessed.

What the check explains

SPF: says which servers are allowed to send mail for the domain.
DKIM: signs messages so tampering and unauthorised sending are easier to detect.
DMARC: can force fake mail claiming to be from your domain to be rejected.
TLS: encrypts mail between servers where supported.
MTA-STS: helps require encrypted mail delivery and resist downgrade attacks.
Open relay controls: prevent outsiders using a mail server to send spam.

White Rabbit secure infrastructure

MX2 is one part of a broader private hosting and legal-technology environment covering secure mail, Wazuh monitoring, AI, Vault, web hosting, cloud storage and managed infrastructure.

MX2 White Rabbit