trustcertia.Documentation
Dashboard
Get started

A trust profile in five steps

From your exact public hostname to a checkable public record.

Verified checks, owner statements, and community opinions have distinct assurance levels. Preserve those labels in every integration.

Create a workspace

Use an email and a password of at least ten characters. Add the exact hostname you control. A free workspace supports one website; Pro supports multiple websites billed per site.

Verify ownership

Install the generated DNS TXT token at _trustcert.<hostname>, add the homepage meta tag, or publish the well-known verification file. Keep the token installed so scheduled checks can reverify control.

Run the guided analysis

The Full analysis wizard shows server-reported scan progress. HTTPS reachability, a trusted TLS certificate with at least fourteen days remaining, and HTTP-to-HTTPS redirection are required. Other checks surface warnings.

Confirm disclosures

AI use, data hosting, framework, public repository, and compliance programs are owner statements. Confirm their accuracy before publishing. These statements are visibly self-attested regardless of the selected compliance status.

Publish and embed

Publish the independent certificate, copy the badge script, and add a discovery pointer for AI readers. A certificate is valid for ninety days and renews after required checks and ownership pass.

EXAMPLE
/.well-known/trustcert-verification.txt
/.well-known/trustcert.json
/llms.txt