netlify.com
The three core checks pass. What is missing is the transport and trust layer around them.
6 of 8 checks pass · 4 tools visible in DNS · nothing urgent
1 · Authentication and transport
SPF
PassValid, hard failAnything not on the list is rejected. The strongest setting.
v=spf1 include:_spf.google.com include:amazonses.com include:7477936.spf06.hubspotemail.net -all
DKIM
Pass3 keys foundSelectors 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; rua=mailto:fexahwip@ag.dmarcian.com; ruf=mailto:fexahwip@fr.dmarcian.com; fo=1
MX
Pass5 hostsMore 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
ReviewNot publishedSending servers cannot tell that this domain requires TLS, so inbound mail can be downgraded to plain text by anyone on the path.
TLS-RPT
PassPublishedTLS failure reports have somewhere to go.
v=TLSRPTv1; rua=mailto:fexahwip@tls.us.dmarcian.com
BIMI
PassPublishedLogo 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://www.netlify.com/assets/logos/logo-netlify-avatar.svg;
DNSSEC
OptionalNot signedOptional. Signing the zone protects every record in this report from tampering.
2 · Tools visible in DNS
| Layer | Tool | Evidence |
|---|---|---|
| Mailbox | Google Workspace | MX aspmx.l.google.com |
| Marketing | HubSpot | SPF include:7477936.spf06.hubspotemail.net |
| Transactional | Amazon SES | SPF include:amazonses.com |
| DMARC reporting | dmarcian | DMARC rua=mailto:…@ag.dmarcian.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)
| Requirement | Applies to | Status | Note |
|---|---|---|---|
| Authenticate with SPF or DKIM | GoogleYahooMicrosoft | Verified | At least one method is in place. |
| Bulk senders: both SPF and DKIM | GoogleYahoo | Verified | Both are present. |
| Publish a DMARC record (p=none is enough) | GoogleYahooMicrosoft | Verified | Policy is p=reject. |
| From: domain aligns with SPF or DKIM | GoogleYahooMicrosoft | Not checkable here | Needs a real message. The Send-a-Test report will check this. |
| Valid forward and reverse DNS for sending IPs | GoogleYahoo | Not checkable here | Depends on the sending server, not the domain. |
| Encrypt in transit (TLS) | GoogleYahoo | Not checkable here | Outbound TLS depends on your sending tool; MTA-STS would cover inbound. |
| One-click unsubscribe (RFC 8058) for marketing mail | GoogleYahoo | Not checkable here | A 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) | GoogleYahoo | Not checkable here | Read 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
-
P3
Publish MTA-STS (record and policy file)
Tells sending servers to require TLS to your MX hosts, which prevents downgrade attacks. The TXT record alone does nothing: the policy file must be served over HTTPS at mta-sts.netlify.com. Start in testing mode, watch TLS-RPT, then switch to enforce.
Publish at_mta-sts.netlify.com and https://mta-sts.netlify.com/.well-known/mta-sts.txtTXT v=STSv1; id=2026100401 mta-sts.txt: version: STSv1 mode: testing mx: aspmx.l.google.com mx: alt1.aspmx.l.google.com mx: alt2.aspmx.l.google.com mx: aspmx2.googlemail.com mx: aspmx3.googlemail.com max_age: 86400
-
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 atnetlify.com
Appendix · Raw DNS answers
| Name | Type | Answer |
|---|---|---|
| netlify.com | MX | 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 |
| netlify.com | A | 3.33.186.135 15.197.167.90 |
| netlify.com | TXT | v=spf1 include:_spf.google.com include:amazonses.com include:7477936.spf06.hubspotemail.net -all (+ 28 other TXT records: site-verification tokens and the like, omitted) |
| _dmarc.netlify.com | TXT | v=DMARC1; p=reject; rua=mailto:fexahwip@ag.dmarcian.com; ruf=mailto:fexahwip@fr.dmarcian.com; fo=1 |
| <selector>._domainkey.netlify.com | TXT | google → key published hs1 → CNAME netlify-com.hs01a.dkim.hubspotemail.net hs2 → CNAME netlify-com.hs01b.dkim.hubspotemail.net |
| _mta-sts.netlify.com | TXT | no record |
| _smtp._tls.netlify.com | TXT | v=TLSRPTv1; rua=mailto:fexahwip@tls.us.dmarcian.com |
| default._bimi.netlify.com | TXT | v=BIMI1; l=https://www.netlify.com/assets/logos/logo-netlify-avatar.svg; |