DirectAdmin
Install the seal through DirectAdmin File Manager and publish the domain callback file in the correct domain document root.
Choose the system that runs your website or email. Each guide explains the correct embed method, domain callback setup, testing and common platform restrictions.
Every email seal starts with sender-domain authentication. Low Security uses a linked signature image; High Security additionally requires a trusted server integration for each final Message-ID.
The integration must create the final Message-ID, call VerifySeal, insert the returned header and footer, and then allow DKIM signing. A normal signature editor cannot safely perform those steps.
| Sending system | High Security path | What will not work |
|---|---|---|
| PHP, Laravel, Node.js or Python | Direct trusted-server integration before the mail transport signs and sends. | Calling the API from browser or frontend code. |
| WordPress | Dedicated protected plugin at the PHPMailer or final transport layer. | A theme snippet, page builder or signature-only plugin. |
| WISECP or WHMCS | Custom mail transport/add-on or trusted outbound gateway with final Message-ID control. | A template footer or pre-send merge-field hook alone. |
| Google Workspace or Microsoft 365 | Trusted application that sends completed MIME through Gmail API, Graph, SMTP or a preserving gateway. | A Gmail/Outlook signature or mail-flow disclaimer alone. |
| Desktop and webmail clients | Use the existing Low Security linked-image seal, or send through an integrated organizational gateway. | Storing a VerifySeal API key in the email client. |
Install the seal through DirectAdmin File Manager and publish the domain callback file in the correct domain document root.
Use cPanel File Manager to add the seal to a website template and create the domain callback file.
Add the seal with Plesk File Manager and place the callback file under the selected domain’s httpdocs directory.
Install directly in an HTML, PHP or server-rendered website without a CMS.
Use a Custom HTML block, footer widget or child-theme template to display the live seal.
Publish the seal in a Custom module or a template override without allowing the editor to strip the script.
Place the seal in a custom block or theme region using a text format that permits the embed.
Add the seal through an HTML card for an exact location or through footer code injection for a site-wide display.
Add the live seal with a Custom Liquid section or a small theme snippet.
Use the linked-image seal inside an Embed HTML element because Wix commonly isolates visible embeds in an iframe.
Add the seal with a Code block or use the linked-image fallback when the plan does not run JavaScript in blocks.
Place the seal with Webflow’s Code Embed element and publish it to the registered custom domain.
Add the seal to a WISECP website template footer, custom page or HTML content area.
Install the seal in a child-theme footer while preserving WHMCS template variables and required scripts.
Use the linked-image markup in a component or load the VerifySeal script only on the browser client.
Commit the seal to the site template and deploy the callback file from the project’s public/static directory.
Understand the trusted-server workflow used to issue a unique, expiring VEM verification code for each final email Message-ID.
Set the final PHPMailer MessageID, request a VEM code, add its header and footer, then let the configured mail transport apply DKIM.
Use a protected WordPress mailer plugin or gateway integration; an email signature or page-builder snippet cannot issue per-message VEM codes.
Create the Message-ID in the queued job, call VerifySeal through Laravel’s HTTP client and pass the returned values into the Mailable.
Set Nodemailer messageId and headers explicitly, append the returned HTML/text footer and send only after the VEM request succeeds.
Create the Python EmailMessage identity, request its VEM code, add the returned header and MIME footers, then submit the finished message through SMTP.
Add VEM processing at the billing platform’s final mailer or outbound gateway; a template footer alone cannot bind a code to the final Message-ID.
Use a trusted application to create the complete MIME message and send it through the Gmail API; a Gmail web signature cannot call the VEM API.
Use a trusted Graph or SMTP application that submits the completed MIME message; Outlook signatures and mail-flow disclaimers are Low Security only.
Publish one DMARC TXT record, monitor aligned SPF and DKIM results, then move safely from reporting to quarantine or reject.
Find the exact selector used to sign your email and enter it correctly in an Email Sender Verification application.
Enable DKIM for a DirectAdmin-hosted domain, identify its selector and prepare the email sender seal.
Use cPanel Email Deliverability to find or repair DKIM and SPF, then identify the selector for VerifySeal.
Enable DKIM signing in Plesk, publish the records in local or external DNS and identify the selector.
Locate Hostinger Email DKIM records in hPanel, confirm the active selector and prepare the email seal.
Publish the SPF, DKIM and DMARC records supplied by your email service in a Cloudflare-managed DNS zone.
Generate a Google Workspace DKIM key, publish it in DNS, start authentication and identify the selector.
Publish both Microsoft 365 DKIM CNAME selectors, enable signing and identify the selector active on current mail.
Create and enable a Zoho Mail selector, publish its public key and prepare the sender seal.
Add an email-sender seal as a linked image in a Gmail signature. JavaScript cannot run in email.
Add the email-sender seal as a linked signature image in Outlook on the web or desktop.
Use a linked seal image in the signature assigned to the verified sender account.
Create an HTML signature for the verified sender and insert the linked Email Sender Seal image.
Add the issued Email Sender Seal to the correct Roundcube sender identity as an HTML signature.
Use the Plain HTML or PHP website guide, or contact support with the name of your platform.
The visual style changes by seal type, but each issued website seal uses the same secure live-image and certificate system.