B80/100

live.com

Name: live.com email authentication report
Creator: MailAuthWatch
License: https://creativecommons.org/publicdomain/zero/1.0/

1 fix stands between this domain and a clean A. 1 item below, ordered by how much inbox it is costing you. Measured 0s ago from public DNS in 77 ms.

SPF PASSDKIM PASSDMARC NOT ENFORCINGMX OK

Monitor this domain Re-run check

Fix these, in this order, or hand the list to your agent

ranked by impact

DMARC is sitting at p=none.

You are collecting reports and enforcing nothing, so anyone can still send as you. Gmail and Yahoo accept p=none from bulk senders, but it protects nobody.

Do this: move to p=quarantine; pct=25 for two weeks, watch the reports, then step to pct=100 and p=reject.

Records found

SPF · TXT

v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~all

DMARC · _dmarc.live.com

v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1

DKIM · 1 of 79 selectors

selector1._domainkey · 2048-bit

MX · Microsoft 365

2 live-com.olc.protection.outlook.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 1 task in order, exact record values and Azure DNS commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for live.com

You are working on the DNS and mail configuration for live.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade B (80/100).
Report: https://www.mailauthwatch.com/check/live.com

## What is published right now (do not assume anything else)
- SPF (TXT live.com): v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~all   — valid, 5 of 10 lookups
- DMARC (TXT _dmarc.live.com): v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
- DKIM: selector1._domainkey (2048-bit)
- MX: live-com.olc.protection.outlook.com  → Microsoft 365
- Nameservers: ns1-37.azure-dns.com, ns2-37.azure-dns.net …  → records are managed in Azure DNS

## Tasks, in order of impact
…

# Fix email authentication for live.com

You are working on the DNS and mail configuration for live.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade B (80/100).
Report: https://www.mailauthwatch.com/check/live.com

## What is published right now (do not assume anything else)
- SPF (TXT live.com): v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~all   — valid, 5 of 10 lookups
- DMARC (TXT _dmarc.live.com): v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
- DKIM: selector1._domainkey (2048-bit)
- MX: live-com.olc.protection.outlook.com  → Microsoft 365
- Nameservers: ns1-37.azure-dns.com, ns2-37.azure-dns.net …  → records are managed in Azure DNS

## Tasks, in order of impact
### 1. DMARC is sitting at p=none.
Why: You are collecting reports and enforcing nothing, so anyone can still send as you. Gmail and Yahoo accept p=none from bulk senders, but it protects nobody.
Replace TXT record:
  _dmarc.live.com  TXT  v=DMARC1; p=quarantine; pct=25; sp=quarantine; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
Only after DKIM is verified working (see the DKIM task if present). Hold for 14 days, review reports, then pct=100, then p=reject.
Azure DNS CLI/API (adjust identifiers):
  az network dns record-set txt add-record -g $RESOURCE_GROUP -z live.com -n _dmarc -v "v=DMARC1; p=quarantine; pct=25; sp=quarantine; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1"

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access Azure DNS or Microsoft 365, stop and say exactly what access you need.

## Verify
  dig +short TXT _dmarc.live.com
  dig +short TXT live.com
Then open https://www.mailauthwatch.com/check/live.com?fresh=1 and confirm:
  DMARC p=quarantine. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.

Open in Claude Open in ChatGPT fix.md

Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.

History goes back as far as your subscription.

SPF OK

v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~all

DNS lookups: 5 of 10 allowed
Final mechanism: ~all

OK No problems detected.

Include tree

5 / 10

live.com0

├─ include:spf-a.hotmail.com+1

├─ include:spf-b.hotmail.com+1

├─ include:spf-c.hotmail.com+1

├─ include:spf-d.hotmail.com+1

└─ include:spf.protection.outlook.com+1

DKIM OK

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed.

Selector	Key	Record
`selector1`	RSA 2048-bit OK	`v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvWyktrIL8DO/+UGvMbv7cPd/Xogpbs…`

OK No problems detected.

DMARC OK

v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1

Policy: p=none · subdomains sp=quarantine
Applies to: 100% of failing mail
Aggregate reports: mailto:rua@dmarc.microsoft

WarningPolicy is p=none: you receive reports but spoofed mail is still delivered. Move to p=quarantine, then p=reject, once reports show legitimate mail passing.

Mail exchange and extras

OK No problems detected.

MTA-STS: OK v=STSv1; id=20190225000000Z;
TLS-RPT: OK v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
BIMI: Not published optional: brand logo in inboxes, requires p=quarantine or reject

How the grade is calculated

Score 80/100. SPF present and valid. SPF ends with ~all. DKIM found (1 selector). DKIM key is 2048-bit or stronger. DMARC present and valid. DMARC policy is none (monitoring only). DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain:

Other recently graded domains

Public checks from the last few days. Every report is re-measured from DNS when opened.

live

DomainSPFDKIMDMARCGrade

amazon.com4 lookups1024-bitp=quarantineA github.com10 lookups2048-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC microsoftonline.com6 lookupsnot foundp=rejectB salesforce.com4 lookups2048-bitp=rejectA mailauthwatch.com1 lookups1024-bitp=rejectA google.com1 lookupsnot foundp=rejectB notion.so0 lookupsnot foundp=quarantineC gandi.net2 lookupsnot foundp=noneC mailship.com1 lookupsnot foundmissingD azure.com2 lookupsnot foundp=rejectB facebook.com1 lookupsnot foundp=rejectB