live.net
At risk, with 3 things to fix
live.net scored 33/100 (grade F). The main issues are no MX records and DMARC policy is none, plus 1 more. Detected senders: Microsoft 365.
Checked 2026-10-04 02:12 UTC · fresh check
Strengthen the DMARC policy
Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further.
_dmarc.live.net
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=quarantine; pct=25; rua=mailto:rua@dmarc.microsoft; adkim=r; aspf=r
v=DMARC1; p=none; rua=mailto:rua@dmarc.microsoft;ruf=mailto:ruf@dmarc.microsoft;fo=1:s:d
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?No MX recordsFailing
- Fail: No MX records
live.net has no MX records and no A/AAAA fallback, so it cannot receive mail, including bounces and DMARC reports. Publish an MX record pointing at your mail provider.
SPFWho may send as you?SPF ends in softfail (~all)Info
- Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.
DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
- Warning: No DKIM key found for the common selectors
None of the 47 selectors probed under live.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for live.net.
DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
- Warning: DMARC policy is none
A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.
How to fix this
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?No BIMI recordInfo
- Info: No BIMI record
No BIMI record at default._bimi.live.net. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.live.net. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.live.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Enable DKIM for Microsoft 365instruction
Microsoft 365 generates the DKIM key for each account, so the exact record must come from Microsoft 365. Without DKIM, mail it sends for live.net cannot pass DMARC through DKIM.
Applies to: selector1._domainkey.live.net
- In Microsoft 365, enable DKIM signing for live.net: tenant-specific: copy Selector1CNAME/Selector2CNAME from Microsoft 365 Defender > Email authentication > DKIM. Publish exactly the record Microsoft 365 shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://learn.microsoft.com/microsoft-365/security/office-365-security/email-authentication-dkim-configure
Enable DKIM for Microsoft 365instruction
Microsoft 365 generates the DKIM key for each account, so the exact record must come from Microsoft 365. Without DKIM, mail it sends for live.net cannot pass DMARC through DKIM.
Applies to: selector2._domainkey.live.net
- In Microsoft 365, enable DKIM signing for live.net: tenant-specific: copy Selector1CNAME/Selector2CNAME from Microsoft 365 Defender > Email authentication > DKIM. Publish exactly the record Microsoft 365 shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://learn.microsoft.com/microsoft-365/security/office-365-security/email-authentication-dkim-configure
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to live.net, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.live.net
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@live.net, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.live.net with the value v=TLSRPTv1; rua=mailto:<that address>.
Prepare BIMIinstruction
BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.
Applies to: default._bimi.live.net
- Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://live.net/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.live.net with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.