Host MTA-STS policies with Google Cloud infrastructure

MTA-STS tells other mail servers to deliver to you only over verified TLS, and it needs two pieces: a _mta-sts TXT record in DNS and a policy file served over HTTPS at mta-sts.yourdomain. On Google Cloud, the policy file is commonly served from Cloud Storage behind a load balancer with a Google-managed certificate, or from a small Cloud Run service on the same hostname.

The policy has to list your real MX hosts, and getting the mode, hostnames or certificate wrong can delay mail, so start in testing mode and move to enforce once reports look clean. The EmailAuth AI Agent reads your live MX and MTA-STS records, drafts the policy file for you, and checks it once it is published. Start with your domain below, or book a free call with an EmailAuth engineer.

To get specific help for Host MTA-STS policies with Google Cloud infrastructure, engage with our EmailAuth AI Agent. It reads your domain's live DNS, checks what is already in place, and gives you ready-to-paste records or walks you through each step.

Open the EmailAuth AI Agent

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

Transport security