Home / Knowledge base / Tools and integrations / Domain Trust Check

Domain Trust Check

Tools and integrations 2 min read Updated 18.10.2026
What is included in the domain summary assessment, why it is needed when buying a site and analyzing a platform, and why other metrics are more important for donors.

The trust check consolidates into one assessment what is usually checked manually across several services: HTTPS and the certificate, security headers, robots.txt and sitemap, the basic markup a maintained site has, and mail DNS records. It's convenient when you need to quickly understand what kind of site you are dealing with. The tool is domain trust assessment.

What is included in the assessment

GroupWhat is checked
ConnectionHTTPS, SSL certificate validity
SecurityHSTS, X-Frame-Options, Content-Security-Policy, X-Content-Type-Options — see analysis
Crawlingrobots.txt, sitemap.xml, canonical
MarkupFavicon, Open Graph, Schema.org, the lang attribute, viewport
MailDNS MX records

Domain age and registration data are a separate check — see domain age. Antivirus and spam blocklists are not part of this score.

Why this is needed in practice

  • Before buying a domain or site — a quick filter for obviously problematic options.
  • Before placing with a partner — to understand what kind of platform offers a link.
  • When analyzing a competitor — to see how it differs technically.
  • For your own site — to find simple oversights: expiring certificate, missing headers.
The assessment does not replace a substantive check
A technically flawless site can be a shell for links, while a live project may have misconfigured headers. Therefore, for donors, other factors are more important: whether their pages are indexed and whether links pass weight — see how we select platforms.

What the assessment does not show

No automated analysis can see the main thing: whether there are real people and an actual audience on the site. A domain with a flawless technical map may turn out to be abandoned, while a site with an expired certificate may be a functioning business that just hasn't gotten around to it. Therefore, the assessment is used as a filter at the entrance, and decisions are made by looking at the site with human eyes.

What to do with a low score on your site

  1. Start with the certificate and redirects — this can be fixed quickly: SSL, redirects.
  2. Add basic security headers.
  3. If email matters to you, check the MX, SPF and DMARC records — see DNS records.
  4. For a complete picture, run a technical audit and security check.

FAQ

What does the trust score show?
A summary of technical signals: HTTPS and the certificate, security headers, robots.txt and sitemap, canonical, basic markup (favicon, Open Graph, Schema.org, lang, viewport) and MX records.
Does it check domain age or blocklists?
No. Domain age is a separate WHOIS check, and antivirus or spam blocklists are not part of this score.
What should be fixed first with a low score?
The certificate and redirects — these can be fixed quickly, then the basic security headers.
Was this article helpful?
Try it on your project Everything described in the article is available in the dashboard — the registration bonus is already in your balance.
Open dashboard