Know which Spam Score you are reading
DomDetailer's current API reference documents mozSpam on the legacy 0–17 raw scale. Export the field as a raw value and retain that scale in the column heading. Do not add a percent sign or apply percentage thresholds to it.
Current Moz Link Explorer help describes Spam Score as a percentage derived from sites with similar features that were penalized or banned. That is a different presentation and model. Dividing the DomDetailer value by 17 does not establish equivalence.
When importing a score from another tool, keep the supplier, metric version, scale and lookup date with it. If the incoming scale is unclear or contradicts the documented response, pause automatic filtering and ask support rather than silently converting it.
Treat the score as a review signal
A concerning score can direct attention to a domain. It does not prove that Google has penalized that domain or that all its links are harmful. A low score also cannot certify a clean history.
Review current content and prior use, relevant referring pages, anchor patterns and destination URLs. A small site or an unusual extension deserves context, rather than automatic rejection based on a single feature.
For an expired-domain shortlist, write a short explanation next to each decision: relevant references remain, previous use conflicts with the new project, source pages cannot be verified, or more investigation is needed. Those notes preserve the reasoning that a raw score cannot contain.
An illustrative screening example
Suppose your export contains raw mozSpam values 1, 5 and 9 for three candidates. Treat those as three raw observations. A column labelled “Spam Score %” would misstate the data, and a formula converting 9 to approximately 53% would add a meaning the API does not provide.
Review the candidate with 9 alongside its DA, TF, categories and backlinks. You may keep it for a relevant name with a plan to build fresh content, or reject it when the link history does not support your purpose. The decision depends on the evidence and the task.
Keep rows with failed requests distinct from numeric zero. Returning an empty result into a default zero cell can make an unmeasured domain appear reassuring in a sorted sheet.
Build a transparent bulk check
The bulk Spam Score workflow covers list preparation, costs and shortlist review. The domain metrics checker retrieves the raw Moz value with DA, PA, TF and CF in a successful one-credit request per domain.
For integrations, preserve the original mozSpam field from the domain metrics API reference. Apply any internal review policy only after confirming the field type and scale.
Questions
Is a raw mozSpam value of 8 the same as 8%?
No. The DomDetailer reference documents a raw 0–17 scale. The current Moz percentage presentation should not be treated as the same field or calculated by dividing the raw value by 17.
Does Spam Score tell me that Google penalized a domain?
No. It is a provider risk signal. Review the domain and its evidence before drawing conclusions about its history or links.