← Domain reports

asana.comemail setup

Public DNS report for asana.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-EDB7F8
Read
27 Sept 2026, 12:53 UTC
Source
Index snapshot
Domain

asana.com

The three core checks pass. What is missing is the transport and trust layer around them.

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

B 87/100 Grade B
SPFValid, hard fail20/20
DKIM2 keys found15/15
DMARCPartial (p=quarantine)22/30
MX5 hosts10/10
MTA-STSPublished10/10
TLS-RPTPublished5/5
BIMIPublished5/5
DNSSECNot signed0/5

1 · Authentication and transport

SPF

PassValid, hard fail

Anything not on the list is rejected. The strongest setting.

v=spf1 include:_spf.google.com include:amazonses.com exists:%{i}._spf.sparkpostmail.com include:mktomail.com include:mg-spf.greenhouse.io include:mail.zendesk.com -all

DKIM

Pass2 keys found

Selectors google, smtp publish a public key.

google._domainkey, smtp._domainkey

DMARC

PassPartial (p=quarantine)

Failing mail goes to spam. One step from full enforcement.

v=DMARC1; p=quarantine; rua=mailto:7ddf7bedf2@rua.easydmarc.us,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:7ddf7bedf2@ruf.easydmarc.us,mailto:dmarc-ruf@asana.com; fo=1; sp=quarantine;

MX

Pass5 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 aspmx2.googlemail.com
50 aspmx3.googlemail.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=20251008T001826

TLS-RPT

PassPublished

TLS failure reports have somewhere to go.

v=TLSRPTv1; rua=mailto:dmarcreports@asana.com

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://vmc.digicert.com/a026a7f7-edfa-427b-ae54-f89d7534b056.svg;a=https://vmc.digicert.com/a026a7f7-edfa-427b-ae54-f89d7534b056.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
MarketingMarketoSPF include:mktomail.com
TransactionalAmazon SESSPF include:amazonses.com
SupportZendeskSPF include:mail.zendesk.com
DMARC reportingEasyDMARCDMARC rua=mailto:…@rua.easydmarc.us

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=quarantine.
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. P2

    Finish DMARC at p=reject

    Quarantine still delivers spoofed mail, just into spam.

    Publish at_dmarc.asana.com
    v=DMARC1; p=reject; rua=mailto:dmarc@asana.com; fo=1
  2. 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 atasana.com

Appendix · Raw DNS answers

NameTypeAnswer
asana.comMX10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
asana.comA15.197.167.90
3.33.186.135
asana.comTXTv=spf1 include:_spf.google.com include:amazonses.com exists:%{i}._spf.sparkpostmail.com include:mktomail.com include:mg-spf.greenhouse.io include:mail.zendesk.com -all
(+ 42 other TXT records: site-verification tokens and the like, omitted)
_dmarc.asana.comTXTv=DMARC1; p=quarantine; rua=mailto:7ddf7bedf2@rua.easydmarc.us,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:7ddf7bedf2@ruf.easydmarc.us,mailto:dmarc-ruf@asana.com; fo=1; sp=quarantine;
<selector>._domainkey.asana.comTXTgoogle → key published
smtp → key published
_mta-sts.asana.comTXTv=STSv1;id=20251008T001826
_smtp._tls.asana.comTXTv=TLSRPTv1; rua=mailto:dmarcreports@asana.com
default._bimi.asana.comTXTv=BIMI1;l=https://vmc.digicert.com/a026a7f7-edfa-427b-ae54-f89d7534b056.svg;a=https://vmc.digicert.com/a026a7f7-edfa-427b-ae54-f89d7534b056.pem

How to verify this yourself. Every line above comes from public DNS. Run dig TXT _dmarc.asana.com or dig MX asana.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/asana.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 B 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.