← Domain reports

calm.comemail setup

Public DNS report for calm.com, read on September 27, 2026: authentication, the email tools its records reveal, the sender rules it meets, and what would raise its score. Every line is a public record.

This page is a snapshot from our index. Re-run to read DNS as it is right now, or type any other domain.

The Email StackPublic DNS Report
Report
TES-20260927-6F017D
Read
27 Sept 2026, 12:53 UTC
Source
Index snapshot
Domain

calm.com

Authenticated end to end and enforced. Spoofed mail is rejected outright.

7 of 8 checks pass · 4 tools visible in DNS · nothing urgent

A 95/100 Grade A
SPFValid, soft fail20/20
DKIM3 keys found15/15
DMARCEnforced (p=reject)30/30
MX4 hosts10/10
MTA-STSPublished10/10
TLS-RPTPublished5/5
BIMIPublished5/5
DNSSECNot signed0/5

1 · Authentication and transport

SPF

PassValid, soft fail

Anything not on the list is accepted but marked. Google recommends ~all; with DMARC enforced it is as strong as -all.

v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.google.com include:_spf.sendergen.com include:mktomail.com include:_spf.mlsend.com ~all

DKIM

Pass3 keys found

Selectors google, hs1, hs2 publish a public key. 2 of them point at a vendor by CNAME.

google._domainkey, hs1._domainkey, hs2._domainkey

DMARC

PassEnforced (p=reject)

Failing mail is rejected. This is the finish line.

v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:dmarc_fr@dmarc.250ok.net; fo=1; rf=afrf

MX

Pass4 hosts

More than one receiving server, so a single outage does not bounce mail.

10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 alt3.aspmx.l.google.com

MTA-STS

PassPublished

The DNS record is present. The policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt cannot be read from a browser, so its mode is not verified here.

v=STSv1; id=G7p1XZqV2M9RdKUyT0aEbnLCfjwH34sQ;

TLS-RPT

PassPublished

TLS failure reports have somewhere to go.

v=TLSRPTv1; rua=mailto:tls-report@vali.email

BIMI

PassPublished

Logo record found and DMARC qualifies. Yahoo shows it from the record; Gmail and Apple Mail also need a VMC or CMC certificate (the a= tag).

v=BIMI1; l=https://amplify.valimail.com/bimi/calm/RReMcETt0-B-calm_com_inc_1456217668.svg; a=https://amplify.valimail.com/bimi/calm/RReMcETt0-B-calm_com_inc_1456217668.pem

DNSSEC

OptionalNot signed

Optional. Signing the zone protects every record in this report from tampering.

2 · Tools visible in DNS

LayerToolEvidence
MailboxGoogle WorkspaceMX aspmx.l.google.com
MarketingHubSpotDKIM hs1._domainkey → calm-com.hs01a.dkim.hubspotemail.net
MarketingMarketoSPF include:mktomail.com
DMARC reportingValimailDMARC rua=mailto:…@vali.email

Only tools that leave a DNS trace appear. A shared DKIM selector is attributed only when its CNAME target names the vendor.

3 · Sender requirements (Google, Yahoo, Microsoft)

RequirementApplies toStatusNote
Authenticate with SPF or DKIMGoogleYahooMicrosoftVerifiedAt least one method is in place.
Bulk senders: both SPF and DKIMGoogleYahooVerifiedBoth are present.
Publish a DMARC record (p=none is enough)GoogleYahooMicrosoftVerifiedPolicy is p=reject.
From: domain aligns with SPF or DKIMGoogleYahooMicrosoftNot checkable hereNeeds a real message. The Send-a-Test report will check this.
Valid forward and reverse DNS for sending IPsGoogleYahooNot checkable hereDepends on the sending server, not the domain.
Encrypt in transit (TLS)GoogleYahooVerifiedMTA-STS shows inbound TLS is required; outbound depends on your sending tool.
One-click unsubscribe (RFC 8058) for marketing mailGoogleYahooNot checkable hereA message header, not a DNS record. Microsoft recommends it rather than requiring it.
Spam complaint rate under 0.1% (0.3% is the hard limit)GoogleYahooNot checkable hereRead it in Google Postmaster Tools and Yahoo Sender Hub. Google’s target is 0.1%; 0.3% is where enforcement starts.

4 · What to fix, in order

  1. P3

    Sign the zone with DNSSEC

    Protects every record in this report from being swapped in transit. Two steps: enable signing at your DNS host (one switch at Cloudflare and most others), then add the DS record it gives you at your registrar.

    Publish atcalm.com

Appendix · Raw DNS answers

NameTypeAnswer
calm.comMX10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 alt3.aspmx.l.google.com
calm.comA108.158.46.2
108.158.46.119
108.158.46.80
108.158.46.23
calm.comTXTv=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.google.com include:_spf.sendergen.com include:mktomail.com include:_spf.mlsend.com ~all
(+ 30 other TXT records: site-verification tokens and the like, omitted)
_dmarc.calm.comTXTv=DMARC1; p=reject; pct=100; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:dmarc_fr@dmarc.250ok.net; fo=1; rf=afrf
<selector>._domainkey.calm.comTXTgoogle → key published
hs1 → CNAME calm-com.hs01a.dkim.hubspotemail.net
hs2 → CNAME calm-com.hs01b.dkim.hubspotemail.net
_mta-sts.calm.comTXTv=STSv1; id=G7p1XZqV2M9RdKUyT0aEbnLCfjwH34sQ;
_smtp._tls.calm.comTXTv=TLSRPTv1; rua=mailto:tls-report@vali.email
default._bimi.calm.comTXTv=BIMI1; l=https://amplify.valimail.com/bimi/calm/RReMcETt0-B-calm_com_inc_1456217668.svg; a=https://amplify.valimail.com/bimi/calm/RReMcETt0-B-calm_com_inc_1456217668.pem

How to verify this yourself. Every line above comes from public DNS. Run dig TXT _dmarc.calm.com or dig MX calm.com and compare. Method: theemailstack.com/methodology.

Scores weigh SPF 20, DKIM 15, DMARC 30, MX 10, MTA-STS 10, TLS-RPT 5, BIMI 5, DNSSEC 5. Message-level requirements (alignment, unsubscribe headers, complaint rate) are not checkable from DNS and are marked as such, never guessed.

Scan to re-run livetheemailstack.com/report/calm.com

About this report

The Email Stack reads public DNS for well-known domains and publishes the result as a report, the same one anyone can generate for any domain at /report. It is a point-in-time read: records change, and a domain that scores A today may score differently next month. The "Re-run live" button reads DNS again in your browser.

Scores weigh SPF 20, DKIM 15, DMARC 30, MX 10, MTA-STS 10, TLS-RPT 5, BIMI 5 and DNSSEC 5. Tools are named only when a DNS record names the vendor; a shared DKIM selector counts only when its CNAME target does. Message-level requirements such as alignment and one-click unsubscribe cannot be read from DNS and are marked as such, never guessed. Method: how we detect tools.

Own this domain and see something wrong? DNS is the source; fix the record and the next read will show it. Questions to hello@theemailstack.com.