To check an email spam score, identify the tool and the delivered message it evaluates. Scores are model-specific diagnostics, not universal probabilities that recipients will mark a campaign as spam.
This guide follows Mail-tester’s documented test-message process. It concerns outbound email, separate from Moz’s SEO Spam Score for website research.
Prepare a representative message
Use the sending account and platform you intend to assess. Include representative formatting, links and sender identity, without unnecessary private customer or account information.
A test sent through a different service may not share the authentication or infrastructure of the real campaign. Record the route, message version and date so later comparisons remain meaningful.
Evaluate distinct sending routes separately before assuming one report covers them all.
Follow the current test workflow
Open Mail-tester and use the test address displayed for the session. Its official FAQ describes submitting a message through your email software and checking the resulting report after it arrives.
Review current access conditions and report handling directly. The service documents that a new message to the same test address replaces the previous result, so preserve relevant findings before repeating that workflow.
Anyone with the exact testing address can access the result under the service’s stated availability period. Treat test content and report sharing accordingly rather than uploading a confidential production message casually.
Read the scale and individual findings
Mail-tester uses a scale with 10/10 as its highest result. A higher score there is favourable; it should not be interpreted as the same direction as another filter’s raw spam score.
The report can identify configuration and message findings. Read the explanation behind each result. A score is not a licence to ignore authentication, the mailing list or recipient expectations.
Our tool-selection guide explains why score models and inputs need comparison.
Investigate the actual sending setup
Check the sending identities, relevant DNS records and delivered authentication results. Gmail’s sender guidance documents its applicable requirements, including additional bulk-sender conditions.
Use your provider’s instructions for configuration changes and retest the relevant route. The DNS guide distinguishes record settings from registration ownership.
When changing DNS, retain the previous values and follow current provider instructions. Retest after the relevant records are being served, so the comparison evaluates the corrected configuration rather than an unchanged cached result.
Assess the campaign beyond the test
Review whether recipients expect the message, whether opting out works and what observed sending logs report. For UK electronic marketing, the ICO’s guidance supplies relevant obligations.
A perfect test does not guarantee another provider’s inbox decision. Our assessment checklist adds permission, sending behaviour and outcomes to message diagnostics.
Keep the findings and verified corrections, then review real bounces, deferrals and complaints. The useful result is evidence of specific improvements rather than an assumed universal “safe” score.