Sender address and domain
The business email address and domain used in the messages that will display the seal.
← All seal categories
EML verification category
Help recipients check the domain behind a business email
Email verification seals are designed for signatures, templates and customer communications. Low Security verifies the sender domain and published authentication records. High Security adds a unique, expiring VEM code for each email Message-ID.
2 available seals
✓
SPF, DKIM and DMARCRecord current sender-domain authentication results in the live verification record.
✓
Two security levelsChoose domain-level assurance or Message-ID-bound High Security verification.
What is reviewed
Evidence and information used for verification
Email verification checks published DNS authentication and the relationship between the sender domain and the approved organization.
DKIM selector
The selector identifying the correct public DKIM key, found in the sending platform or a delivered email header.
SPF, DKIM and DMARC DNS
Current public authentication records are retrieved automatically and recorded with their latest check result.
Why use this category
Benefits designed for email security
SPF, DKIM and DMARC
Record current sender-domain authentication results in the live verification record.
Two security levels
Choose domain-level assurance or Message-ID-bound High Security verification.
Email-safe seal code
Use an image and link that works in common signatures and email templates.
Automatic rechecks
Scheduled DNS checks can identify when authentication records need attention.
Available seals
All seal designs
Choose your level of verification
Open any seal to see its exact checks, requirements, availability, limitations and current design.
Live design preview
Email sender verification
Low Security
Email Sender Verification
Email Sender VerifiedConfirms sender-domain control and current SPF, DKIM and DMARC records.
See this seal and what it verifies →
Live design preview
Email sender verification
High Security
High Security Email Verification
High Security Email VerifiedHigh Security: current domain authentication plus unique, expiring VEM codes bound to email Message-IDs.
See this seal and what it verifies →
How it works
From application to live verification
Product requirements can vary, but every category follows a clear path from submitted information to a public status record.
Designed forBilling teamsSupport desksProfessional servicesOrganizations sending sensitive email
- 1Verify the sender domain
Provide the domain, DKIM selector and required organization information.
- 2Check DNS authentication
SPF, DKIM and DMARC records are retrieved and assessed.
- 3Add the email seal
Install it in a signature or generate High Security VEM codes through the API.
Where to use the seal
Put verification where customers make trust decisions
The live certificate remains the source of truth. These placements make it easier for a visitor to find and open it.
Staff email signatures
Add the linked image beneath the normal contact block without embedding scripts.
Invoices and billing emails
Give recipients a verification route on messages that are commonly imitated by scammers.
Support replies
Help customers compare the sender domain before following support instructions.
Transactional templates
Use the static seal link or create Message-ID-bound VEM codes through the High Security API.
Common questions
Understand the verification scope before applying
Every seal page also explains its exact checks, requirements and important limitations.
What is the difference between Low and High Security?+
Low Security verifies the sender domain and its SPF, DKIM and DMARC records. High Security adds a unique expiring VEM code bound to the Message-ID of one email.
Can the DKIM selector be corrected?+
Yes. Customers and authorized administrators can update an incorrect selector and run the DNS check again.
Does a valid seal prove the message body is genuine?+
A domain-level seal does not. High Security binds a code to a Message-ID, while recipients should still confirm their mail provider reports aligned DKIM and DMARC passes.
Ready to compare?