Terms of Service

MailBaseline is a sender-readiness monitor operated by Eastbase Studio (“we”, “us”). It checks whether a sending domain meets the technical requirements Gmail, Yahoo, and Outlook publish for senders, explains how to fix what's wrong, and watches for changes over time.

We are not affiliated with, or endorsed by, Google, Yahoo, or Microsoft.

MailBaseline reports technical readiness only: the presence and correctness of SPF, DKIM, DMARC, From-alignment, one-click unsubscribe, and a recommended hardening tier (MTA-STS, TLS-RPT, BIMI), read from your public DNS and from message headers you choose to paste in.

Mailbox providers also weigh sender reputation, recipient engagement, and message content. For that reason we do not and cannot guarantee that your mail reaches the inbox, that it avoids the spam folder, or any particular deliverability outcome. Scores and checks are informational, not a warranty of delivery.

Mailbox-provider documentation, requirements, thresholds, and enforcement change over time, and so does our scoring as we track those changes and improve the checks. A passing score is a point-in-time technical result for the records we could read at that moment — not a guarantee of continued compliance, inbox placement, or delivery. A domain that scores well today can fail tomorrow because a provider tightened a rule, a record changed, or your sending practices changed.

MailBaseline does not publish, edit, or delete DNS records for you. We read public DNS and hand you suggested record values to apply yourself at your DNS host or provider. We never ask for, and never hold, credentials or API access to your DNS.

Before you apply anything we suggest, it is your responsibility to:

• Review the change against your own sending setup and your provider's guidance.
• Preserve existing records — in particular, merge rather than replace when a host already has an SPF, DKIM, DMARC, or MX record in place.
• Keep a copy of the previous values so you can roll back.

Incorrect or incomplete SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT, BIMI, or related DNS changes can interrupt email authentication or delivery — including causing legitimate mail to be rejected or quarantined. You apply changes at your own risk, and we are not responsible for the consequences of changes you make.

• You must provide an accurate email address and keep your login credentials secure.
• You are responsible for activity under your account.
• You must be at least 18, or otherwise legally able to form a binding contract in your jurisdiction. MailBaseline is a business and technical service, not a consumer product for minors.
• We may suspend or close accounts that abuse the service, break these terms, or put other users at risk.

The two surfaces have different rules, because they place very different demands on third-party infrastructure.

Public scans. A public scan reads records that are already published in public DNS. You may use it for legitimate, limited evaluation — checking a domain you send from, a domain you are about to work with, a vendor or client domain you are assessing, or an example while learning. It is a lookup tool for occasional, human-scale use.

Ongoing monitoring. Adding a domain to continuous monitoring — daily scans, drift alerts, DMARC report analysis — is different. You may only monitor a domain you own, control, administer, or are authorized to manage on behalf of whoever does. If that changes, remove the domain.

You agree not to:

• Use the scanner for bulk reconnaissance or abusive enumeration — sweeping lists of domains, harvesting infrastructure detail across organizations, or profiling third parties you have no legitimate reason to assess.
• Use results to exploit a weakness in someone else's mail setup — including spoofing a domain with weak authentication or targeting it for phishing.
• Scrape the service, republish its output as your own, or circumvent rate limits, caching, or bot protections.
• Run excessive automated scanning — scripted, parallel, or high-volume requests, or automation that places an unreasonable load on us or on the DNS infrastructure we query.
• Use MailBaseline to support spam, phishing, or any unlawful or deceptive sending. The checks are framed around compliance and are of no use to abusive senders.
• Resell, white-label, or redistribute the service except where a plan expressly allows it, or attempt to reverse-engineer it beyond what the law permits.

Uploaded DMARC reports are parsed defensively (strict size caps, no external entities). Do not upload files crafted to exploit a parser. We may rate-limit, suspend, or block any use that breaks these rules.

The analyzer reads the raw headers of a message you already received and reports what they prove about authentication. Headers are ordinary technical metadata, but they are not anonymous: they routinely contain email addresses, IP addresses, message IDs, routing and relay data, authentication results, and unsubscribe metadata. Treat a paste as sharing that information with us.

Paste headers only. Do not paste message bodies, attachments, secrets, credentials, API keys, tokens, or confidential content. Only paste a message you are entitled to share.

What we do with a paste is set out in the Privacy Policy: the raw paste is processed in memory and is never written to our database, and when you are signed in the parsed result is saved to your analyzer history until you delete your account.

MailBaseline offers a free tier plus paid Starter ($9/month) and Growth ($19/month) plans. Paid plans renew monthly until cancelled.

Payments are handled by Lemon Squeezy, our payment provider and merchant of record, who also collect any applicable sales tax or VAT. You can cancel anytime and manage your card and invoices from the billing portal in Settings. Cancellation, downgrade, and refund details are in the Refund & Cancellation Policy.

We rely on a small set of vendors to run the service — including hosting, our database, email delivery (Resend), payments (Lemon Squeezy), optional Google sign-in, and privacy-first analytics and error reporting. How they handle your data is described in the Privacy Policy.

If you add a Slack or Discord webhook URL for drift alerts, treat that URL as a confidential credential: anyone who holds it can post into your channel. Alerts we send to it contain the domain being monitored and the DNS and authentication details of what changed. Add a webhook only for a channel whose audience should see that, keep the URL out of shared documents and public repositories, and rotate it in your Slack or Discord settings if it is ever exposed. You can remove or replace the webhook at any time in Settings.

We work to keep MailBaseline available and accurate, but it is provided on an as-is, best-effort basis. As an early-stage product we do not offer a formal uptime guarantee or service-level agreement, and DNS and provider behavior can change outside our control.

To the fullest extent permitted by law, MailBaseline is provided without warranties of any kind, express or implied — including any warranty of deliverability or inbox placement.

We are not liable for indirect, incidental, or consequential losses, including lost mail, lost revenue, or reputational harm arising from your use of the service — nor for the effects of DNS changes you apply, or of a provider changing its requirements after a scan. Our total liability for any claim is limited to the amount you paid us in the twelve months before the claim.

You can stop using MailBaseline at any time. To request account deletion, email support@eastbase.studio from your account address. We may suspend or terminate access for a breach of these terms. On deletion your monitored domains and stored scan history are removed; see the Privacy Policy for retention details.

We may update these terms as the product evolves; the “last updated” date above reflects the current version, and material changes will be noted in-product or by email. Continued use after a change means you accept it.

These terms, and any dispute or claim arising out of or connected with them or your use of MailBaseline, are governed by the laws of Vietnam, without regard to conflict-of-laws rules. We will always try to resolve a problem directly first — email support@eastbase.studio and a human will reply. If that doesn't work, the dispute will be resolved by the competent courts of Vietnam, and you and we submit to their exclusive jurisdiction. Nothing here removes any mandatory protection or venue that the law of your country of residence gives you and cannot be waived by agreement.