The Domain Trust Score is a composite rating from 0 to 100 that reflects how trustworthy and well-configured a domain appears to email servers, security tools, and web browsers. It’s the same type of signal that email providers and security scanners use to make filtering decisions.
The Six Signal Groups
1. Blacklist Status (High Impact)
Checked against 130+ blocklists across four categories:
- IP reputation lists (mail server IPs)
- Domain reputation lists
- Phishing and malware databases
- Policy block lists
Scoring impact: A critical listing (Spamhaus, Google Safe Browsing) can drop the score by 30–40 points alone. Multiple listings compound the penalty.
Fix: Identify and resolve the root cause, then request removal from each list. See how to check domain blacklists.
2. Email Authentication (High Impact)
Checks for SPF, DMARC, and DKIM records and evaluates their configuration strength.
| Record | What It Does | Score Impact |
|---|---|---|
| SPF | Authorizes which servers can send email for your domain | Missing = −10 pts |
| DMARC | Policy enforcement + reporting for SPF/DKIM failures | Missing = −15 pts |
| DKIM | Cryptographic signing to verify email wasn’t modified | Missing = −5 pts |
| BIMI | Brand logo display in supported inboxes | Bonus when present |
The biggest gap: Most domains with low scores are missing DMARC entirely or have p=none (monitor mode, no enforcement). Without DMARC enforcement, your domain can be freely used in phishing campaigns.
Fix: Add a DMARC record and fix SPF failures.
3. SSL / TLS Configuration (Medium Impact)
Evaluates the SSL certificate and server configuration:
- Certificate validity: Is it current, from a trusted CA, and correctly chained?
- Certificate type: DV vs OV vs EV (stronger validation = higher trust signal)
- Protocol support: Does it allow obsolete protocols (TLS 1.0, 1.1)? SSL 3.0?
- Cipher strength: Are weak or deprecated ciphers enabled?
- HSTS: Does the server enforce HTTPS via the Strict-Transport-Security header?
Score impact: An expired certificate drops the score significantly. Allowing TLS 1.0/1.1 or weak ciphers causes moderate deductions. Perfect SSL/TLS adds up to 15 points.
Fix: Renew certificates before expiry, disable obsolete protocols in your server config, and add HSTS.
4. DNS Health (Medium Impact)
Checks that the domain’s DNS configuration is complete and consistent:
- NS records: Are authoritative nameservers responding and consistent?
- SOA record: Is the zone properly configured?
- MX records: If email is expected, are mail servers correctly configured?
- Response times: Are nameservers responding within acceptable latency?
- DNSSEC: Is DNS signing enabled to prevent spoofing of DNS responses?
Score impact: Misconfigured or missing records cause moderate deductions. DNSSEC adds a small bonus.
5. Domain Age and Registration (Lower Impact)
Newer domains inherently carry lower trust because fraudulent sites are typically short-lived.
| Age | Trust Signal |
|---|---|
| < 3 months | Very low — new or recently re-registered |
| 3–12 months | Low — recently established |
| 1–3 years | Medium — established |
| 3–5 years | Good |
| 5+ years | Strong — long-standing domain |
This component can’t be improved — domain age accumulates with time. If you’re running a new legitimate business, other signal groups are more important to optimize.
6. Traffic and Reputation Signals (Lower Impact)
Estimated organic traffic and web presence are used as supporting signals:
- Domains with consistent organic traffic have demonstrated web presence
- Zero traffic on a domain claiming significant activity raises suspicion
- Traffic from high-risk regions or known proxy networks can negatively signal
This component uses aggregated traffic data — the exact values are less important than the directional signal.
Understanding Your Trust Grade
| Score | Grade | Interpretation |
|---|---|---|
| 85–100 | A | Excellent — well-configured, clean reputation |
| 70–84 | B | Good — minor issues, worth investigating |
| 55–69 | C | Fair — one or more significant gaps |
| 40–54 | D | Poor — active issues affecting email or reputation |
| 0–39 | F | Critical — blacklisted or severely misconfigured |
What the AI Recommendations Tell You
After running a Trust Score check, DomainScan’s AI analysis lists specific, prioritized recommendations. Each recommendation includes:
- What’s wrong: The specific misconfiguration or missing element
- Why it matters: Impact on deliverability, security, or reputation
- How to fix it: Concrete steps to resolve the issue
The recommendations are ordered by impact — fix the top items first for the fastest score improvement.
Common Low-Score Patterns
Score: 30–50 with email issues
Usually means: blacklisted mail server IP + no DMARC enforcement + weak SPF. Fix order: (1) resolve blacklist, (2) strengthen SPF, (3) add DMARC p=reject.
Score: 50–65 with SSL issues
Usually means: valid certificate but weak TLS configuration (outdated protocols, missing HSTS). Fix: update server TLS config, add HSTS header.
Score: 60–70 on a new domain
Usually means: domain age penalty + missing DKIM/DMARC. Fix: add full email authentication stack — you can’t speed up domain age, but authentication adds immediate points.
Score: 75–85 but email still going to spam
Trust Score doesn’t capture everything. Spam filtering also considers content, sending reputation, and list hygiene. Use DomainScan’s email authentication checker for a deeper email-specific analysis.
Improving Your Score: Priority Order
- Resolve any blacklist listings (biggest impact, up to 40 pts)
- Add/fix DMARC with enforcement (
p=quarantineorp=reject) (+15 pts) - Fix SPF record — ensure
~allor-allsoftfail/hardfail (+10 pts) - Add DKIM for all sending sources (+5 pts)
- Fix SSL issues — renew, disable weak protocols, add HSTS (+10 pts)
- Fix DNS misconfigurations — ensure NS/MX/SOA are correct (+5 pts)
- Enable DNSSEC at your registrar/DNS provider (+3 pts)
A domain with clean blacklists and full email authentication will reach 75–85 regardless of age. From there, SSL and DNS optimization pushes it higher.
Common Questions
My Trust Score is low but my site seems fine. Should I be worried?
Yes — many of the factors the Trust Score measures are invisible to visitors but affect email deliverability, search engine trust, and security tool ratings. A low score despite a 'working' site often means missing email authentication (your domain can be spoofed), outdated SSL configuration, or blacklist listings that are silently filtering your email.
How often does the Trust Score update?
DomainScan fetches fresh data on every check — there's no cached score. The underlying data sources (blacklists, DNS resolvers, SSL) are queried in real time. Run another check after making changes; improvements usually show within minutes for DNS/SSL and up to 48 hours for blacklist removals.
Can competitors hurt my Trust Score?
Indirectly, yes. If someone uses your domain in a phishing campaign (spoofing), your domain may appear on phishing databases. DMARC with p=reject is the only reliable defense — it tells receiving servers to reject email that fails your authentication, preventing your domain from being used in spoofed campaigns.
What's the fastest way to raise a low Trust Score?
It depends on what's dragging it down. DNS and SSL issues fix instantly. Email authentication (SPF, DMARC) takes effect within minutes of DNS propagation. Blacklist removals take 24–48 hours. Domain age can't be changed. Run the Trust Score check and look at the AI recommendations — they're prioritized by impact.