B75/100

bing.com

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

2 fixes stand between this domain and a clean A. 2 items below, ordered by how much inbox they are costing you. Measured 0s ago from public DNS in 145 ms.

SPF PASSDKIM NOT FOUNDDMARC REJECTMX OK

Monitor this domain Re-run check

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

ranked by impact

No DKIM key found under 79 common selectors.

Either DKIM signing is off, or it uses a selector we did not probe. Without DKIM, forwarded mail and anything that breaks SPF fails DMARC.

Do this: in Microsoft 365 Defender go to Email & collaboration → Policies → DKIM, publish the two CNAME records (selector1 and selector2) and enable signing.

Aggregate reports are being sent to a domain that has not authorised yours.

microsoft.com has not published bing.com._report._dmarc.microsoft.com, so receivers will discard aggregate reports sent there.

Do this: ask the report provider to publish the authorisation record, or use an address on your own domain.

Records found

SPF · TXT

v=spf1 include:spf.protection.outlook.com -all

DMARC · _dmarc.bing.com

v=DMARC1; p=reject; pct=100; rua=mailto:BingEmailDMARC@microsoft.com;

DKIM · 0 of 79 selectors

none under common selectors

MX · Microsoft 365

10 bing-com.mail.protection.outlook.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 2 tasks 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 bing.com

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

## What is published right now (do not assume anything else)
- SPF (TXT bing.com): v=spf1 include:spf.protection.outlook.com -all   — valid, 1 of 10 lookups
- DMARC (TXT _dmarc.bing.com): v=DMARC1; p=reject; pct=100; rua=mailto:BingEmailDMARC@microsoft.com;
- DKIM: no key found under 79 common selectors
- MX: bing-com.mail.protection.outlook.com  → Microsoft 365
- Nameservers: ns1-204.azure-dns.com, ns2-204.azure-dns.net …  → records are managed in Azure DNS

## Tasks, in order of impact
…

# Fix email authentication for bing.com

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

## What is published right now (do not assume anything else)
- SPF (TXT bing.com): v=spf1 include:spf.protection.outlook.com -all   — valid, 1 of 10 lookups
- DMARC (TXT _dmarc.bing.com): v=DMARC1; p=reject; pct=100; rua=mailto:BingEmailDMARC@microsoft.com;
- DKIM: no key found under 79 common selectors
- MX: bing-com.mail.protection.outlook.com  → Microsoft 365
- Nameservers: ns1-204.azure-dns.com, ns2-204.azure-dns.net …  → records are managed in Azure DNS

## Tasks, in order of impact
### 1. No DKIM key found under 79 common selectors.
Why: Either DKIM signing is off, or it uses a selector we did not probe. Without DKIM, forwarded mail and anything that breaks SPF fails DMARC.
Add CNAME record:
  selector1._domainkey.bing.com  CNAME  selector1-bing-com._domainkey.<tenant>.onmicrosoft.com   (value comes from the provider step below)
Add CNAME record:
  selector2._domainkey.bing.com  CNAME  selector2-bing-com._domainkey.<tenant>.onmicrosoft.com   (value comes from the provider step below)
Microsoft 365 Defender → Email & collaboration → Policies & rules → Threat policies → DKIM → select the domain → Create DKIM keys.
Publish the two CNAME records it shows, then return and turn signing on.
Where: Azure portal → DNS zones → the zone → Record sets.

### 2. Aggregate reports are being sent to a domain that has not authorised yours.
Why: microsoft.com has not published bing.com._report._dmarc.microsoft.com, so receivers will discard aggregate reports sent there.
Ask the report provider to publish the authorisation record, or use an address on your own domain.

## 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 CNAME selector1._domainkey.bing.com
  dig +short CNAME selector2._domainkey.bing.com
  dig +short TXT bing.com
  dig +short TXT _dmarc.bing.com
Then open https://www.mailauthwatch.com/check/bing.com?fresh=1 and confirm:
  DKIM found. 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.protection.outlook.com -all

DNS lookups: 1 of 10 allowed
Final mechanism: -all

OK No problems detected.

Include tree

1 / 10

bing.com0

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

DKIM Not found

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed. "Not found" means none of those selectors exist; the domain may still sign with a custom selector.

WarningNo DKIM key found under 79 common selectors. If you know your selector, add it to the check; if you have no DKIM at all, enable it at your mail provider.

DMARC OK

v=DMARC1; p=reject; pct=100; rua=mailto:BingEmailDMARC@microsoft.com;

Policy: p=reject
Applies to: 100% of failing mail
Aggregate reports: mailto:BingEmailDMARC@microsoft.com

Warningmicrosoft.com has not published bing.com._report._dmarc.microsoft.com, so receivers will discard aggregate reports sent there.

Mail exchange and extras

OK No problems detected.

MTA-STS: Not published optional: enforces TLS for inbound mail
TLS-RPT: Not published
BIMI: Not published optional: brand logo in inboxes, requires p=quarantine or reject

How the grade is calculated

Score 75/100. SPF present and valid. SPF ends with -all. DMARC present and valid. DMARC policy is reject. 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

mailship.com1 lookupsnot foundmissingD icloud.com4 lookupsnot foundp=quarantineC mail.ru1 lookups1024-bitp=rejectA digicert.com3 lookups2048-bitp=quarantineA msn.com7 lookups2048-bitp=noneB stagewest.org4 lookups2048-bitp=noneB jlwaviation.com1 lookups2048-bitp=rejectA claude.ai0 lookupsnot foundp=rejectA github.com10 lookups2048-bitp=quarantineA gandi.net2 lookupsnot foundp=noneC salesforce.com4 lookups2048-bitp=rejectA amazon.com4 lookups1024-bitp=quarantineA