This Addendum is part of the Clasp Security Terms of Service for Hosted Email Encryption, our managed MTA-STS hosting service. If this Addendum conflicts with the Terms on Hosted Email Encryption, this Addendum controls, except that nothing in it limits a right that applicable law does not allow you to give up.
Service and term. Hosted Email Encryption covers one domain. It is a one-year prepaid commitment of $100, charged at purchase and on the first day of each renewal Term. There is no monthly billing option. At the end of each Term it renews automatically for another one-year Term, paid annually, until you cancel. You can cancel your renewal anytime online. To stop the next renewal, cancel by 11:59 p.m. Central Time on the day before your current Term ends. Cancelling stops the next renewal; the service continues until the Term ends, and there is no refund for the current year except as Terms Section 9 provides (Terms Sections 7, 8 and A12.8).
What Hosted Email Encryption does. MTA-STS lets your domain ask sending mail servers to use an encrypted, verified connection when they deliver email to the mail servers you list. Hosted Email Encryption is our managed MTA-STS hosting service. MTA-STS enforces encryption in transit between mail servers. It does not encrypt stored mail or message content end to end, and it does not affect sending servers that do not support it. It applies to email others send to your domain. It is not designed to change how your organization sends outbound mail.
The policy host and the records you add. We host the policy file at https://mta-sts.(your domain)/.well-known/mta-sts.txt. The standard set is three records at your DNS host: (1) a CNAME for mta-sts.(your domain) that points to our policy host, policy.claspsec.net, on the claspsec.net zone; (2) a CNAME for _mta-sts.(your domain) that points to a name we control on claspsec.net, in the form (token)._mta-sts.claspsec.net, where we publish the TXT record v=STSv1; id=(policy id); and (3) a TLS-RPT TXT record for _smtp._tls.(your domain) that sends SMTP TLS reports to an address we host at reports.claspsec.net (Terms Section A12.2). RFC 8461, Section 3.1, allows the _mta-sts name to return a CNAME that points (directly or through other CNAMEs) to a TXT record, and sending mail servers must follow that CNAME; the resolved TXT satisfies Section 3.1. Certificate validation uses HTTP domain control validation. If your domain's DNS is hosted on Cloudflare, you must set the mta-sts record to DNS-only (not proxied). In rare cases, for example if Cloudflare cannot confirm hostname ownership through HTTP validation, our support team may ask you to add one additional verification record. We will tell you the exact record and when it may be removed. We do not send that request by default. You keep control of your domain's DNS. You add the records we give you, and you may change or remove them at any time. Because we control the TXT record behind the _mta-sts CNAME, we change the policy and its id on our side, with no edit to the DNS records you added, when we switch the policy to testing, move it to "none" after unresolved drift, restore it, or publish mode "none" at offboarding. We never change your MX records, mailboxes, mail provider, or any other DNS record or service that you do not point to us.
How sending mail servers behave if something goes wrong. If our policy file cannot be reached, a sending mail server that has no valid cached policy normally delivers your mail the ordinary way, as if your domain had no MTA-STS policy (RFC 8461, Section 3.3). A sending mail server that has already fetched your policy keeps applying that cached copy until the policy's max_age expires, even if it cannot reach us: 1 day (86400 seconds) in testing or "none" mode, and 7 days (604800 seconds) in enforce mode (RFC 8461, Sections 3.2, 3.3 and 5.1; Terms Section A12.5). Outgoing email is not designed to be affected. The policy covers only email others send to your domain (RFC 8461, Section 1.1). The main risk is changing your mail provider or MX records without telling us. If you move your email while the policy is in enforce mode, sending mail servers that still hold the old enforce policy may defer or bounce incoming mail until that cached copy expires, up to 7 days (RFC 8461, Sections 4, 5 and 10). Sending mail servers that follow the standard must check for an updated policy id before permanently failing (RFC 8461, Sections 5 and 5.1). That is why you must tell us at least 7 days before you change MX records or mail providers, and why we may switch the published policy to mode:testing, on our side and with no customer DNS edit, if we detect drift (Terms Sections 12.6, A12.6 and A12.7).
Caching. Sending mail servers may keep a copy of your policy for up to its max_age and keep applying it after the policy is changed, after you change your DNS, and after the service ends. We set max_age as Terms Section A12.5 states (604800 seconds, 7 days, in enforce mode, and 86400 seconds, 1 day, in testing and "none" mode). We cannot clear copies that others hold.
Your notices to us, our checks, and automatic fail-safe. You tell us at least 7 days before you change your MX records, mail provider, mail servers, or their certificates (Terms Section A12.7). If you do not, you remain responsible for the consequences of the unannounced change. While your policy is in testing mode, we run the checks in Terms Section A12.6 every day. While it is in enforce mode, we run them every 15 minutes. If we detect drift, we may switch the published policy to mode:testing automatically, with max_age set to 86400 seconds (1 day) and a new policy id, on our side and with no customer DNS edit, and we email the Report Address. Testing mode is designed not to block delivery (RFC 8461, Section 5). Your policy starts in testing mode. Clasp schedules and runs a meeting about 14 days after setup. We send you a Calendly booking link, and the booking includes a Zoom link. We move it to enforce mode only after that meeting, and only if you approve the move in or after that meeting (Terms Section A12.4). If you do not attend the meeting, do not reschedule it, or do not approve the move, the policy stays in testing mode, the service continues, and no fee is refunded or credited except as Terms Section 9 provides.
Unresolved drift after 14 days. If the drift that caused us to switch your policy to mode:testing stays unresolved for 14 days after that switch, we may publish a new policy with mode "none" and a max_age of 86400 seconds (1 day), and a new policy id, on our side and with no customer DNS edit (Terms Section A12.6). Mode "none" tells sending mail servers that fetch the new policy to treat your domain as having no MTA-STS policy, so a stale or mismatched policy does not normally cause delivery failures at senders that have not cached it. A sending mail server that still holds a cached policy may keep applying it until that policy's max_age expires. When we switch the policy to testing under paragraph 6, we email the Report Address (the Order Email Address) and state the date, 14 days later, on which we may publish mode "none." We send a reminder notice to the Report Address at least 3 days before we publish mode "none." Your subscription continues, and no fee is refunded or credited for the period the policy is in testing or "none" mode, except as Terms Section 9 provides. After you fix the records or confirm the new mail provider, and after we re-verify, we restore the policy to testing mode within 2 business days. We return the policy to enforce mode only after a new meeting that Clasp schedules and runs (a Calendly booking with a Zoom link), and your approval given in or after that meeting, and only after we confirm 14 consecutive clean days of checks, as Terms Section A12.4 describes. You may still cancel under Terms Section 8.
Failed payments. Terms Section 7.7 applies. If the final retry fails, we stop providing the service, and we do not collect any further amount for that Term after the last successful payment. We do not change your MX records or other DNS records because of a failed payment.
When the service ends. When Hosted Email Encryption ends, we follow the RFC 8461, Section 8.3, guidance for removing a policy: we publish a new policy with mode "none" and a max_age of 86400 seconds (1 day), and we publish a new policy id, on our side and with no customer DNS edit. We keep serving that policy for the longer of (a) the prior max_age we used for your domain (and, if a longer max_age was previously served, that longer period) or (b) 90 days. After that period, you should remove the records in paragraph 3 (the three standard records, and any additional verification record we asked you to add). We may then remove our hosting for your hostname. If you have already removed the two CNAME records, we may remove our hosting after that period as well (Terms Section A12.8).
Availability. We will use commercially reasonable efforts to keep the policy host available so that sending mail servers can fetch your policy. This Service has no uptime service-level agreement and no service credits (Terms Section A12.13).
Third-party providers and force majeure. Hosted Email Encryption depends on third parties, including Cloudflare (the network, the Worker that serves the policy file, Cloudflare for SaaS custom hostnames, related DNS for claspsec.net, and intake of SMTP TLS reports sent to reports.claspsec.net), your DNS host and domain registrar, and a certificate authority selected by Cloudflare, which issues the certificate for mta-sts.(your domain) through HTTP domain control validation. We are not liable for delay, interruption, or failure caused by those parties, or by other events, beyond our reasonable control. Terms Section 23 applies (Terms Section A12.14).
Service-incident notice. If a service incident materially affects the availability of the policy host, we will aim to notify you by a post on our status page at https://status.claspsec.net and by email to the Report Address, which is the Order Email Address for the Order. Our target, which is not a guarantee, is to send a first notice within 4 hours of confirming a problem that affects your domain, and updates at least every 4 hours until it is fixed. That timing does not create an uptime SLA or a service credit. This paragraph covers service incidents. Security incidents and personal-data breach notification are governed by our Privacy Policy and applicable law (Terms Section A12.15).
No guarantees; liability. Terms Sections 19.7 and 20.5 apply, including the exclusion of consequential losses and the cap of fees you paid us for Hosted Email Encryption in the twelve (12) months before the event giving rise to the first claim, with the carve-outs in Terms Section 20.3. This Addendum is not a release of claims.
I acknowledge that:
Signature. By typing my name below and selecting "Sign and continue", I sign this Addendum and Acknowledgment electronically and intend my typed name to be my signature.
| Field | Entry |
|---|---|
| Full legal name of the customer (organization) | [required] |
| Domain | [required] |
| Signer's full name (typed signature) | [required] |
| Signer's title | [required] |
| Authority | [required, not preselected] I am authorized to sign for the customer and to authorize these changes for this domain (Terms Sections 1.3 and 10) |
| Date and time | [recorded by the system] |
After you sign, we email you a secure link to download a copy of what you signed, which you can keep.