Email sent in your name
Who can send as your domain, phishing filters
Measured score
47
Partial assessment · 2 left out of the score
Needs attention (8)
- SeriousNeeds fixingEmail sent in your name
Enforce DMARC
What this means
contoso.com: DMARC is published but set to p=none for contoso.com — monitoring mode only. Spoofed email is not blocked. Move to p=quarantine after reviewing reports. Also checked: contoso.onmicrosoft.com (warn).
What to do
Move from p=none → p=quarantine after reviewing aggregate reports.
- Who does it
- Your IT person or provider
- How long
- About 10 minutes
2 evidence rowsTechnical detailsevidence
Learn more ↗Evidence · 2 recorded items
- _dmarc.contoso.com — v=DMARC1; p=none; rua=mailto:[email protected]
- _dmarc.contoso.onmicrosoft.com — No DMARC record found
- SeriousNeeds fixingEmail sent in your name
SPF includes a name that has no SPF record
What this means
SPF issues for contoso.com: Record ends in ~all (soft fail) — receivers typically deliver but mark as suspicious. Move to -all for stronger protection. spf.protection.outlook.com is named in the record and has no SPF record, or more than one. A receiver that gets as far as that name returns PermError, and SPF effectively fails open.
What to do
Adjust SPF record. Test changes with a tool like dmarcian SPF Surveyor before publishing.
- Who does it
- Your IT person or provider
- How long
- Not estimated
2 evidence rowsTechnical detailssetting, evidence
The setting
SPF TXT record at contoso.com
Your DNS provider (GoDaddy / Cloudflare / Route 53 / etc.) → DNS records → Edit TXT record
Now: v=spf1 include:spf.protection.outlook.com ~all→Should be: v=spf1 include:spf.protection.outlook.com -all (≤10 DNS lookups)
Open in the admin portal ↗Learn more ↗Evidence · 2 recorded items
- contoso.com — v=spf1 include:spf.protection.outlook.com ~all
- spf.protection.outlook.com — Named in the record, and has no SPF record of its own (or more than one)
- SeriousNeeds fixingEmail sent in your name
No DKIM signing key published
What this means
No DKIM signing key is published for contoso.com under Microsoft 365's two names, selector1 and selector2. Mail from contoso.com is not signed in your own name. Microsoft 365 still signs the mail it sends, but under your onmicrosoft.com name, which does not count for DMARC. So DMARC for contoso.com rests on SPF alone, and SPF breaks when mail is forwarded.
What to do
Enable DKIM signing for the domain in the Defender portal — this publishes the two required CNAMEs (you publish them at your DNS provider) and turns on signing.
- Who does it
- Your IT person or provider
- How long
- About 20 minutes
2 evidence rowsTechnical detailssetting, steps, evidence
The setting
DKIM signing for contoso.com
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Email authentication settings → DKIM
Now: No signing key published under selector1 or selector2→Should be: Enabled — both selector1 and selector2 CNAMEs published, signing toggled ON
Open in the admin portal ↗Steps
- security.microsoft.com → Email & collaboration → Policies & rules → Threat policies → Email authentication settings → DKIM
- Select contoso.com
- Microsoft shows you the two CNAME records — publish them at your DNS provider
- Return to portal and toggle 'Sign messages for this domain with DKIM signatures' to ON
Learn more ↗Evidence · 2 recorded items
- selector1._domainkey.contoso.com — No key found
- selector2._domainkey.contoso.com — No key found
- Should fixNeeds fixingEmail sent in your name
MTA-STS not published
What this means
contoso.com receives mail but has no MTA-STS policy. Sending servers fall back to opportunistic TLS, which an on-path attacker can strip (STARTTLS downgrade) to read or alter inbound email in transit — including password resets and invoices.
What to do
Publish an MTA-STS policy: a TXT record at _mta-sts.<domain> plus a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt (start in mode=testing, then enforce). Microsoft 365 supports MTA-STS for hosted domains.
- Who does it
- Your IT person or provider
- How long
- About 45 minutes
- Before you change it
- Enforcing MTA-STS before your MX/TLS certs are correct can defer legitimate mail. Publish mode=testing first and watch TLS-RPT reports.
1 evidence rowTechnical detailssetting, evidence
The setting
MTA-STS for contoso.com
DNS: TXT at _mta-sts.contoso.com + an mta-sts.<domain> HTTPS policy endpoint
Now: (no MTA-STS policy)→Should be: v=STSv1; id=<timestamp> + policy at mode=enforce
Open in the admin portal ↗Learn more ↗Evidence · 1 recorded item
- _mta-sts.contoso.com — No MTA-STS (v=STSv1) TXT record
- Should fixNeeds a lookEmail sent in your name
Turn on anti-phishing protection
What this means
Judged: Office365 AntiPhish Default. Office365 AntiPhish Default: EnableOrganizationDomainsProtection, EnableTargetedUserProtection and EnableMailboxIntelligenceProtection are all false, so no impersonation protection covers your people or domains. 1 to tighten.
What to do
Fix: impersonation protection. Add your executives and your own domain to impersonation protection.
- Who does it
- Your IT person or provider
- How long
- About 15 minutes
1 evidence rowTechnical detailssetting, steps, evidence
The setting
Anti-phishing policy
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-phishing
Now: impersonation protection = off→Should be: Enabled = true; EnableSpoofIntelligence = true; HonorDmarcPolicy = true; at least one impersonation protection on
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-AntiPhishPolicy | Format-List Name, Enabled, EnableSpoofIntelligence, HonorDmarcPolicy, EnableOrganizationDomainsProtection, EnableTargetedUserProtection, EnableMailboxIntelligenceProtection
Evidence · 1 recorded item
- Office365 AntiPhish Default — EnableOrganizationDomainsProtection, EnableTargetedUserProtection and EnableMailboxIntelligenceProtection are all false, so no impersonation protection covers your people or domains
- Should fixNeeds a lookEmail sent in your name
Enable Safe Links
What this means
Judged: Built-In Protection Policy. Built-In Protection Policy: AllowClickThrough is true (people can click through to a flagged site). 1 to tighten. Exceptions to Built-in protection, and which people a preset policy covers, are not readable through Microsoft's configuration snapshots.
What to do
Turn on or tighten: AllowClickThrough. Microsoft's Standard and Strict presets set these.
- Who does it
- Your IT person or provider
- How long
- About 10 minutes
1 evidence rowTechnical detailssetting, steps, evidence
The setting
Safe Links policy
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Safe Links
Now: AllowClickThrough = true→Should be: EnableSafeLinksForEmail/Teams/Office = true; AllowClickThrough = false; ScanUrls = true
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-SafeLinksPolicy | Format-List Name, EnableSafeLinksForEmail, EnableSafeLinksForTeams, EnableSafeLinksForOffice, AllowClickThrough, ScanUrls
Evidence · 1 recorded item
- Built-In Protection Policy — AllowClickThrough is true (people can click through to a flagged site)
- Should fixNeeds a lookEmail sent in your name
Detected phishing is not quarantined
What this means
Judged: Default. Mail Microsoft detects as phishing goes to people's Junk Email folder, where they can still open it, instead of quarantine. 1 to tighten.
What to do
Set the phishing action to quarantine.
- Who does it
- Your IT person or provider
- How long
- About 15 minutes
1 evidence rowTechnical detailssetting, steps, evidence
The setting
Anti-spam inbound policy
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-spam → Anti-spam inbound policy
Now: PhishSpamAction = MoveToJmf→Should be: AllowedSenderDomains and AllowedSenders empty; PhishSpamAction = Quarantine; HighConfidencePhishAction = Quarantine; SpamAction and HighConfidenceSpamAction = MoveToJmf or Quarantine
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-HostedContentFilterPolicy | Format-List Name, AllowedSenderDomains, AllowedSenders, SpamAction, HighConfidenceSpamAction, PhishSpamAction, HighConfidencePhishAction
Learn more ↗Evidence · 1 recorded item
- Default — PhishSpamAction is MoveToJmf, so mail detected as phishing goes to the Junk Email folder, where people can still open it
- MinorNeeds a lookEmail sent in your name
TLS-RPT not published
What this means
contoso.com has no TLS-RPT record, so you get no reports when senders fail to deliver over TLS — you'd be blind to an active downgrade or a broken MX certificate.
What to do
Add a TLS-RPT TXT record so you receive aggregate TLS-failure reports.
- Who does it
- Your IT person or provider
- How long
- About 10 minutes
1 evidence rowTechnical detailssetting, evidence
The setting
TLS-RPT for contoso.com
DNS: TXT at _smtp._tls.contoso.com
Now: (no TLS-RPT record)→Should be: v=TLSRPTv1; rua=mailto:[email protected]
Open in the admin portal ↗Evidence · 1 recorded item
- _smtp._tls.contoso.com — No TLS-RPT (v=TLSRPTv1) TXT record
Not verified (2)
- Not verifiedEmail sent in your name
Remove stale allow-list entries
What this means
Whether the Tenant Allow/Block List has stale or permanent (no-expiration) allow entries — but Microsoft only exposes this setting through PowerShell, or through a preview API we don't yet depend on. Verify with Exchange Online PowerShell using the command below — it takes about a minute.
How to check it
Run the PowerShell command below to review the current setting.
Technical detailssetting, steps, evidence
The setting
Remove stale allow-list entries
Not exposed via Microsoft Graph as of 2026. Available only via Exchange Online PowerShell.
Now: Not readable via Graph→Should be: Action = Allow entries: each should have an ExpirationDate within 90 days; flag any with ExpirationDate set to a date >12 months out or unset; review entries older than 6 months for whether the justification still holds
Open in the admin portal ↗Steps
- 1. Open PowerShell as your tenant admin
- 2. Connect-ExchangeOnline
- 3. Get-TenantAllowBlockListItems -ListType Sender; Get-TenantAllowBlockListItems -ListType Url; Get-TenantAllowBlockListItems -ListType FileHash
- 4. Review: Action = Allow entries: each should have an ExpirationDate within 90 days; flag any with ExpirationDate set to a date >12 months out or unset; review entries older than 6 months for whether the justification still holds
PowerShell
Connect-ExchangeOnline Get-TenantAllowBlockListItems -ListType Sender; Get-TenantAllowBlockListItems -ListType Url; Get-TenantAllowBlockListItems -ListType FileHash
Evidence · 1 recorded item
- How to verify — Connect-ExchangeOnline → Get-TenantAllowBlockListItems -ListType Sender; Get-TenantAllowBlockListItems -ListType Url; Get-TenantAllowBlockListItems -ListType FileHash
- Not verifiedEmail sent in your name
Tag external senders
What this means
Whether the External sender tag is enabled tenant-wide — but Microsoft only exposes this setting through PowerShell, or through a preview API we don't yet depend on. Verify with Exchange Online PowerShell using the command below — it takes about a minute.
How to check it
Run the PowerShell command below to review the current setting.
Technical detailssetting, steps, evidence
The setting
Tag external senders
Not exposed via Microsoft Graph as of 2026. Available only via Exchange Online PowerShell.
Now: Not readable via Graph→Should be: Enabled = True. AllowList is empty (or contains only tenants you legitimately consider 'internal'). If disabled, enable with: Set-ExternalInOutlook -Enabled $true
Open in the admin portal ↗Steps
- 1. Open PowerShell as your tenant admin
- 2. Connect-ExchangeOnline
- 3. Get-ExternalInOutlook
- 4. Review: Enabled = True. AllowList is empty (or contains only tenants you legitimately consider 'internal'). If disabled, enable with: Set-ExternalInOutlook -Enabled $true
PowerShell
Connect-ExchangeOnline Get-ExternalInOutlook
Evidence · 1 recorded item
- How to verify — Connect-ExchangeOnline → Get-ExternalInOutlook
In good shape (10)
- In good shapeEmail sent in your name
Route mail through Microsoft 365
MX correctly points to Exchange Online Protection.
Technical detailsevidence
Evidence · 1 recorded item
- contoso-com.mail.protection.outlook.com — Priority 0
- In good shapeEmail sent in your name
Block external auto-forwarding
Judged: Default. Default has AutoForwardingMode Automatic, Microsoft's default, which behaves as Off; CIS asks for Off set explicitly.
Technical detailssetting, steps
The setting
Outbound spam policy: automatic forwarding
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-spam → Anti-spam outbound policy (Default)
Now: Meets the standard→Should be: AutoForwardingMode = Off
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Set-HostedOutboundSpamFilterPolicy -Identity Default -AutoForwardingMode Off Get-RemoteDomain Default | Format-List AutoForwardEnabled
- In good shapeEmail sent in your name
Enable Safe Attachments
Judged: Built-In Protection Policy, EXOAtpPolicyForO365. Safe Attachments is on and blocks or detonates attachments before delivery. Exceptions to Built-in protection, and which people a preset policy covers, are not readable through Microsoft's configuration snapshots.
Technical detailssetting, steps
The setting
Safe Attachments policy
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Safe Attachments
Now: Meets the standard→Should be: Enable = true; Action = Block or DynamicDelivery; EnableATPForSPOTeamsODB = true; AllowSafeDocsOpen = false
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-SafeAttachmentPolicy | Format-List Name, Enable, Action Get-AtpPolicyForO365 | Format-List EnableATPForSPOTeamsODB, AllowSafeDocsOpen
- In good shapeEmail sent in your name
Enable anti-malware and auto-purge
Judged: Anti-malware policy Default, Content filter policy Default. Zero-hour auto purge is on for malware, phishing and spam, and the file-type filter is on.
Technical detailssetting, steps
The setting
Anti-malware and anti-spam policies
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-malware and Anti-spam
Now: Meets the standard→Should be: ZapEnabled = true; EnableFileFilter = true; PhishZapEnabled = true; SpamZapEnabled = true
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-MalwareFilterPolicy | Format-List Name, ZapEnabled, EnableFileFilter Get-HostedContentFilterPolicy | Format-List Name, PhishZapEnabled, SpamZapEnabled
- In good shapeEmail sent in your name
Remove risky mail flow rules
No transport rules are configured.
Technical detailssetting, steps
The setting
Mail flow rules
Exchange admin center → Mail flow → Rules
Now: Meets the standard→Should be: No enabled, enforcing rule that redirects or copies mail outside your domains, or sets SCL -1 for a sender
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-TransportRule | Format-List Name, State, Mode, Priority, SetSCL, BlindCopyTo, RedirectMessageTo, CopyTo, AddToRecipients
- In good shapeEmail sent in your name
Keep the IP allow list narrow
Judged: Default. The IP allow list is empty and Microsoft's safe list is off.
Technical detailssetting, steps
The setting
Connection filter policy
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-spam → Connection filter policy
Now: Meets the standard→Should be: IPAllowList empty; EnableSafeList = false
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Get-HostedConnectionFilterPolicy | Format-List Name, IPAllowList, EnableSafeList
- In good shapeEmail sent in your name
Set outbound spam limits
Judged: Default. Default allows 500 external recipients an hour, 1000 internal an hour and 1000 a day, then BlockUserForToday.
Technical detailssetting, steps
The setting
Outbound spam policy limits
Microsoft Defender portal → Email & collaboration → Policies & rules → Threat policies → Anti-spam → Anti-spam outbound policy
Now: Meets the standard→Should be: RecipientLimitExternalPerHour ≤ 500; RecipientLimitInternalPerHour ≤ 1000; RecipientLimitPerDay ≤ 1000; ActionWhenThresholdReached = BlockUser
Open in the admin portal ↗PowerShell
Connect-ExchangeOnline Set-HostedOutboundSpamFilterPolicy -Identity Default -RecipientLimitExternalPerHour 500 -RecipientLimitInternalPerHour 1000 -RecipientLimitPerDay 1000 -ActionWhenThresholdReached BlockUser
- In good shapeEmail sent in your name
Restrict inbound mail connectors
No inbound connectors are configured; whether Direct Send is rejected is not readable through Microsoft's snapshots.
Technical detailssetting, steps
The setting
Inbound connectors
Exchange admin center → Mail flow → Connectors
Now: Meets the standard→Should be: Every enabled partner connector is limited by sender IP address or certificate and none accepts every domain; every enabled on-premises connector lists its servers' IP addresses or certificate and does not treat mail as internal
Open in the admin portal ↗Steps
- Open the Exchange admin center and go to Mail flow → Connectors.
- Open each inbound connector named here and note the partner or server it is for.
- Edit it to require the sender's IP addresses or its certificate name, or delete it if nothing uses it.
- For an on-premises connector, turn off TreatMessagesAsInternal unless your on-premises servers do not run Exchange and you have no other way to mark their mail as internal.
PowerShell
Connect-ExchangeOnline Get-InboundConnector | Format-List Name,ConnectorType,SenderDomains,RestrictDomainsToIPAddresses,RestrictDomainsToCertificate,SenderIPAddresses,TlsSenderCertificateName,TreatMessagesAsInternal
- In good shapeEmail sent in your name
Remove risky inbox rules
Scanned 12 mailboxes; no external-forwarding or alert-hiding inbox rules found.
- In good shapeEmail sent in your name
Turn off SMTP AUTH for the organization
SMTP AUTH is off for the organization; individual mailboxes can still turn it on, and that is not read here.
Technical detailssetting, steps
The setting
Turn off SMTP AUTH for the organization
Exchange admin center → Settings → Mail flow → Turn off SMTP AUTH protocol for your organization
Now: SMTP AUTH is off→Should be: SMTP AUTH is off for the organization
Open in the admin portal ↗Steps
- Open the Exchange admin center and go to Settings → Mail flow.
- Select "Turn off SMTP AUTH protocol for your organization" and save.
- If a printer, scanner or application still needs SMTP AUTH, allow it on that one mailbox only.
PowerShell
Connect-ExchangeOnline Set-TransportConfig -SmtpClientAuthenticationDisabled $true
Does not apply (1)
- Does not applyEmail sent in your name
Make sure your MTA-STS policy actually works
No mail-receiving domain publishes an MTA-STS record, so there's no policy file to validate.