← Domain reports

lemonade.comemail setup

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

lemonade.com

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

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

A 100/100 Grade A
SPFValid, soft fail20/20
DKIM3 keys found15/15
DMARCEnforced (p=reject)30/30
MX5 hosts10/10
MTA-STSPublished10/10
TLS-RPTPublished5/5
BIMIPublished5/5
DNSSECValidated5/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:gxmplfdaqa.powerspf.com include:mail.zendesk.com include:19532022.spf01.hubspotemail.net ~all

DKIM

Pass3 keys found

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

google._domainkey, s1._domainkey, s2._domainkey

DMARC

PassEnforced (p=reject)

Failing mail is rejected. This is the finish line.

v=DMARC1; p=reject; rua=mailto:6apt1u9lue@rua.powerdmarc.com; ruf=mailto:6apt1u9lue@ruf.powerdmarc.com; fo=0:1:d:s;

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=20240120125047841056;

TLS-RPT

PassPublished

TLS failure reports have somewhere to go.

v=TLSRPTv1;rua=mailto:6apt1u9lue@tls.powerdmarc.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://hostedbimi.com/2124/611e727e-455d-4a19-9518-3d6548ed7eb4.svg;a=https://hostedbimi.com/2124/611e727e-455d-4a19-9518-3d6548ed7eb4.pem;

DNSSEC

PassValidated

The resolver validated the zone, so the records above cannot be silently swapped in transit.

2 · Tools visible in DNS

LayerToolEvidence
MailboxGoogle WorkspaceMX aspmx.l.google.com
MarketingHubSpotSPF include:19532022.spf01.hubspotemail.net
TransactionalSendGridDKIM s1._domainkey → s1.domainkey.u17589619.wl120.sendgrid.net
SupportZendeskSPF include:mail.zendesk.com

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

Nothing to fix. Every check in this report passes.

Appendix · Raw DNS answers

NameTypeAnswer
lemonade.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
lemonade.comA104.18.4.148
104.18.5.148
lemonade.comTXTv=spf1 include:gxmplfdaqa.powerspf.com include:mail.zendesk.com include:19532022.spf01.hubspotemail.net ~all
(+ 39 other TXT records: site-verification tokens and the like, omitted)
_dmarc.lemonade.comTXTv=DMARC1; p=reject; rua=mailto:6apt1u9lue@rua.powerdmarc.com; ruf=mailto:6apt1u9lue@ruf.powerdmarc.com; fo=0:1:d:s;
<selector>._domainkey.lemonade.comTXTgoogle → key published
s1 → CNAME s1.domainkey.u17589619.wl120.sendgrid.net
s2 → CNAME s2.domainkey.u17589619.wl120.sendgrid.net
_mta-sts.lemonade.comTXTv=STSv1; id=20240120125047841056;
_smtp._tls.lemonade.comTXTv=TLSRPTv1;rua=mailto:6apt1u9lue@tls.powerdmarc.com
default._bimi.lemonade.comTXTv=BIMI1;l=https://hostedbimi.com/2124/611e727e-455d-4a19-9518-3d6548ed7eb4.svg;a=https://hostedbimi.com/2124/611e727e-455d-4a19-9518-3d6548ed7eb4.pem;

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