Analyze domain spam signals and get a risk assessment with actionable fixes.
Enter a domain above to check its spam score
We analyze DNS records, email authentication, domain age, and more
DNS data via Google Public DNS and domain data via RDAP
A spam score is a numerical rating that estimates how likely a domain is to be associated with spam. It considers multiple factors including domain age, DNS configuration, email authentication records, and naming patterns. A lower score means the domain appears more trustworthy, while a higher score indicates potential spam risk.
Spam scores are used by email providers, search engines, and security tools to filter malicious or low-quality content. Understanding your domain's spam score helps you identify issues that may be hurting your email deliverability, search rankings, or overall online reputation.
Domain age is one of the strongest signals in spam detection. Newly registered domains are frequently used for spam campaigns, phishing attacks, and other malicious activities because they are cheap to acquire and easy to abandon.
Domains less than 30 days old carry the highest risk. Between 30 days and 6 months, the risk decreases but remains elevated. After one year of consistent legitimate use, a domain has typically established enough history to be considered trustworthy. This is why buying aged domains is a common tactic in SEO and email marketing.
Email authentication records are critical for preventing spam and phishing. SPF (Sender Policy Framework) specifies which mail servers are authorized to send email for your domain. Without an SPF record, anyone can send emails pretending to be from your domain.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) builds on SPF and DKIM to provide a policy for handling unauthenticated emails. It tells receiving mail servers what to do when an email fails authentication checks. Missing DMARC records leave your domain vulnerable to spoofing and can significantly hurt your email deliverability.
Your domain's DNS configuration reveals important trust signals. A records show that the domain resolves to an actual server, indicating active use. MX records show the domain is set up for email, which is expected for legitimate businesses.
Missing DNS records can indicate an abandoned, parked, or newly set up domain. Spam domains often lack proper DNS infrastructure because they are designed for short-term use. Ensuring your domain has complete DNS configuration is a straightforward way to improve its trust profile.
The spam score ranges from 0 to 100, where lower is better. A score of 0-20 indicates low risk with minimal spam signals. A score of 21-40 indicates medium risk with some areas to improve. A score of 41-60 means high risk with multiple issues that need attention. A score of 61-100 indicates critical risk and the domain may be flagged by spam filters.
Focus on the failed checks shown in your results. The most impactful fixes are typically adding SPF and DMARC records for email authentication, ensuring MX records are configured, and building domain age over time. Each failed check includes a specific recommendation for how to resolve it.
Newly registered domains are disproportionately used for spam. Studies show that a large percentage of spam emails come from domains less than one day old. Email providers and search engines use domain age as one factor in determining trust. Domains over one year old with consistent legitimate activity are generally considered more trustworthy.
SPF (Sender Policy Framework) is a DNS TXT record that lists which mail servers are authorized to send email for your domain. DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a DNS TXT record at _dmarc.yourdomain.com that tells receiving servers how to handle emails that fail authentication. Both are essential for email deliverability and preventing spoofing.
Yes, this tool is free to use. It queries Google Public DNS and RDAP (Registration Data Access Protocol) to analyze domain information. There are daily usage limits to prevent abuse, but the tool itself requires no payment or API key.
