Bulk Spam Score check for domain lists

The bulk DA, PA and Trust Flow checker retrieves mozSpam together with Moz authority scores, Majestic metrics and Pretty counts. A successful request for one domain costs one credit for that combined response.

The current DomDetailer reference documents mozSpam on a raw 0–17 scale. It is not the current Moz Link Explorer percentage display. Read the Spam Score scale and interpretation guide before building a filter or importing another supplier's thresholds.

This is a paid list-screening workflow. It helps you find questions to investigate; it does not identify Google penalties or issue a clean-domain certificate.

1. Keep the original auction or prospect export.
2. Create a lookup column containing bare hostnames.
3. Remove duplicate domains and blank rows.
4. Count unique inputs and confirm your available credits.
5. Run a small sample and check that the result columns and scale are understood.

If the list is very large, use the Windows bulk domain checker or a controlled domain metrics API integration. Save intermediate results so an interrupted run does not require checking completed domains again.

Keep DA, TF, CF, raw Spam Score, topical categories and referring-domain counts beside each other. Label a concerning combination for manual investigation rather than equating one score with a verdict.

Illustrative data: a raw score of 9 alongside a high DA deserves an explanation. Confirm the scale, look at prior use and inspect actual source pages. Do not convert 9 into a percentage or conclude from it alone that the domain was penalized.

Use the backlink checker on candidates where the links affect your purchase decision. Look at anchor patterns, repeated placements and destination URLs. Record whether evidence supports the intended topic.

1,000 unique successful requests consume 1,000 credits. That is about $0.79–$1.36 in consumed credit value at the current pack rates. Credits are bought in packs: the entry pack is $34 for 25,000 credits. This is not a $0.79 checkout option. Compare the current DomDetailer credit packs.

Backlink review is a separate request. Checking 50 retained candidates consumes another 50 credits when those backlink requests succeed. Credits do not expire, so unused credits from the purchased pack remain available for later work.

A client-side timeout may leave the server outcome uncertain. Save your known results and check the account before resubmitting uncertain rows.

Use column names such as “Moz Spam Score — raw 0–17” and preserve the original response value. Add the lookup date, a review status and a short reason. Keep API errors distinct from returned zero.

If a screening policy uses a cutoff, label it as your own policy and test it on representative data. Revisit it when the task, supplier or metric version changes.

The expired-domain vetting guide shows where this first pass fits between an auction export and a reviewed shortlist.