live.com is a free email provider
live.com is a major consumer mailbox provider. Anyone can open an address, and at this scale a forged message is usually caught by the provider even where the domain's own records would let it through.
85 /100
Strong
Email authentication report card
What live.com publishes in DNS to stop other people sending mail in its name, read record by record.
Can mail be forged as this domain?
Yes on paper, but unlikely to land
DMARC is set to p=none, which only asks for reports, so nothing this domain publishes tells a receiver to reject a forged message. In practice a forgery will still be caught: a provider this size runs its own reputation and content filtering on top of what the domain publishes. That safety net is the provider's, not the domain's.
- Weak
SPF ~all
The record ends in ~all. Mail from a host outside the list is only marked, not rejected, so it usually still arrives.
- Weak
DMARC p=none
A DMARC record is published, but p=none only asks for reports. Receivers are told to deliver failing mail anyway, so this stops no forgery.
A checker that reports "DMARC found" here is telling you nothing useful.
- Weak
MTA-STS testing
A policy is published in testing mode. Failures are reported but delivery still goes ahead over an unverified connection.
- Pass
DNSSEC Signed
The zone is signed, so the MX, SPF and DMARC answers above cannot be quietly rewritten in transit.
- Pass
TLS-RPT Published
Sending servers have an address to report failed TLS deliveries to.
Why it scores 85?
- Registered more than five years ago.
- Accepts mail through 1 MX host.
- Mail is handled by a mailbox provider we recognize.
What to publish to close the gaps
The records live.com is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.
Tighten SPF to -all
Namelive.comTypeTXTValuev=spf1 <your existing mechanisms> -allKeep the mechanisms you already have and change the final qualifier. Anything softer leaves the forgery path open.
Move DMARC off p=none
p=none blocks nothing. Once your reports show every legitimate sender passing, raise the policy to quarantine and then to reject.
Switch MTA-STS to enforce
Valuemode: enforceChange mode in https://mta-sts.live.com/.well-known/mta-sts.txt and bump the id in the TXT record. Testing mode reports failures but still delivers.
Questions about live.com
Every answer below is generated from the stored record for this domain.
Is live.com a disposable email domain?
Is live.com spoofable?
Does live.com publish SPF and DMARC?
Who handles email for live.com?
How old is the live.com domain?
How do I block live.com on my signup form?
Can I trust email from live.com?
Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.