Mail Security Studioby TechKee Limited

GUIDED EMAIL SECURITY CONFIGURATION

Build safer email-security records

Check what is published, load the current settings and prepare carefully reviewed updates. Nothing is published or changed automatically.

1 Configure records2 Review and download

Start with the domain

Enter the domain used after the @ sign in an email address. We will check its mail servers and existing security records.

Enter only the domain—do not include https://, www or an email address.

Review and configure the records

Values marked Loaded from current configuration came from public DNS or the published MTA-STS policy. Check them carefully before making changes.

Receiving mail servers (MX)
Where should other organisations deliver email?

Existing MX records are loaded below. You may add, change or remove a server, but confirm every change with the email provider first.

No proposed MX records are available. Ask the email provider which receiving servers and priorities to use, then add them below before continuing.
Proposed MX configuration

What would you like to draft?

The administrator's recommended default is preselected; adjust it if your DNS provider requires a different value.

SPF
Who may send email for this domain?

Include every platform and service that sends using this domain. Unknown mechanisms from an existing record are preserved separately.

The SPF mx mechanism follows the domain’s published MX records automatically; individual MX hostnames are not written into the SPF text.

Advanced terms are kept visible so imported SPF behaviour is not silently lost.

Proposed SPF record

DMARC
What should happen when authentication does not align?

Begin with monitoring and correct legitimate senders before requesting quarantine or rejection.

Enter an email address or complete mailto: destination.

Proposed DMARC record

MTA-STS
Require trusted TLS for incoming email

MTA-STS uses a DNS discovery record and a policy file hosted on your website. The published policy is loaded when it can be retrieved securely.

Linked MX hostnames update automatically. Additional custom or wildcard patterns are preserved.

Proposed MTA-STS records
DNS discovery recordHTTPS policy file

                
TLS-RPT
Receive reports about secure SMTP delivery
Publish one or more destinations for aggregate reports about TLS, certificate and MTA-STS failures.
Enter an email address, mailto: URI or HTTPS reporting endpoint.
Proposed TLS-RPT record

            

            
Open glossary in a new tab