D
Scanned 3 hours ago. Re-scan for a fresh result after a fix.
Issues to fix
- failNo MX host resolves to an A/AAAA address, mail cannot be delivered.→
- failNo DMARC record: receivers have no policy for handling unauthenticated mail.→
- warnSPF does not include Microsoft 365's sending hosts (spf.protection.outlook.com), so Microsoft 365 mail may fail SPF.→
- warnMicrosoft 365 DKIM is not published for this domain (common for unconfigured custom domains).→
- warnPartial bulk-sender setup, missing DKIM, DMARC. Gmail/Yahoo and Microsoft require all three for 5,000+ messages/day.→
- warnDeep include chain (nested includes are hard to audit and can push you toward the 10-lookup limit).→
- warnNo TLS-RPT reporting address. TLS delivery failures go unreported.→
Results
01Mail exchangers (MX)C
pass
1 MX record(s) found.
records
| preference | exchange | ttl |
|---|---|---|
| 0 | brightsmiledental-com02i.mail.protection.outlook.com | 3600 |
fail
No MX host resolves to an A/AAAA address, mail cannot be delivered.
hosts brightsmiledental-com02i.mail.protection.outlook.com
info
Only one MX host, a secondary MX adds delivery resilience.
02Mail providerC
info
Mail provider: Microsoft 365.
provider microsoft365
warn
SPF does not include Microsoft 365's sending hosts (spf.protection.outlook.com), so Microsoft 365 mail may fail SPF.
expected spf.protection.outlook.com
warn
Microsoft 365 DKIM is not published for this domain (common for unconfigured custom domains).
selectors selector1, selector2
03SPFA
pass
SPF record present.
record v=spf1 include:secureserver.net -all
pass
SPF uses 3 of the 10 permitted DNS lookups.
lookups 3
warn
Deep include chain (nested includes are hard to audit and can push you toward the 10-lookup limit).
depth 3
pass
-all default policy.
04DKIMA
info
No DKIM selector found via common probes (no _domainkey subtree exists), the domain may use a custom selector.
05DMARCC
fail
No DMARC record: receivers have no policy for handling unauthenticated mail.
06DNS healthA
07BlacklistsA
pass
brightsmile-dental.com is not listed on Spamhaus ZRD.
target brightsmile-dental.com
list Spamhaus ZRD
pass
brightsmile-dental.com is not listed on Spamhaus DBL.
target brightsmile-dental.com
list Spamhaus DBL
08Bulk sending readinessA
warn
Partial bulk-sender setup, missing DKIM, DMARC. Gmail/Yahoo and Microsoft require all three for 5,000+ messages/day.
spf true
dkim false
dmarc false
threshold 5,000 messages/day
info
One-click List-Unsubscribe is a message-level header. Verify by sending a test message.
09TLSA
info
No DANE/TLSA records. DANE is not deployed for these mail servers.
hosts brightsmiledental-com02i.mail.protection.outlook.com
10MTA-STSA
11BIMIA
info
No BIMI record. No brand logo is published for inboxes with BIMI support.
BIMI draft
12Email Verification Protocol
info
No Email Verification Protocol record. Browsers cannot verify addresses at this domain without sending an email.
EVP draft
About this report
This report grades the email and DNS setup of brightsmile-dental.com against the relevant RFCs. Each check links to the standard behind the rule. A high grade means the common causes of spoofing and poor deliverability are covered. A grade is not a guarantee that every message reaches the inbox.
Frequently asked questions
What does the grade mean?
The grade summarizes how completely the domain implements the core email authentication and DNS standards. A and B mean the main protections (SPF, DKIM, DMARC, valid MX) are in place. Lower grades flag gaps that make spoofing easier or hurt deliverability. A missing MX record caps the grade at F, a weak SPF all-qualifier caps at D, and no DMARC caps at C.
How fresh is this report?
A report is a snapshot from when it was last scanned, kept as a shareable link. If you are fixing your setup, use the Re-scan button to run every check live again.
Why is the SMTP section still loading?
The live SMTP probe connects to the mail servers from a dedicated prober, which takes a few seconds and runs separately from the DNS checks. The results stream in when ready. If SMTP was not requested for this report, that section stays empty.
I own this domain and want to stop scan.mx checking it.
Domain owners can block scanning by publishing a DNS TXT record; see the opt-out page.