Platform
Show what you actually check, not what you claim
A Trust Profile is a page you publish that lists evidence Nivaronix already holds about your infrastructure — verified domain ownership, monitoring history, uptime over the last 30 days, and credentials earned from checks that ran. Every line on it is re-derived from the underlying record each time the page loads, so it cannot say something your account stopped supporting.
What this is — and what it is not
Nivaronix issues evidence of checks it ran on your account. That is the whole claim. A Nivaronix credential is not a certification, not an audit, not a compliance attestation, and not a statement that your systems are secure. It records something specific and checkable — that a domain proved ownership, that a scan reached a particular score, that monitoring ran for a particular stretch — and it links to a page where anyone can read the exact rule behind it.
- Nothing here is hand-issued. Awards are written by the evaluator alone; there is no operator grant path and no way to self-assert a credential.
- There are no referral badges, no share-to-earn badges, and no counters for scans run or days logged in — those would measure usage, not anything about your infrastructure.
- No badge is keyed to your own uptime record, which would mean taking a badge away on the day you had an outage — the very event the product exists to catch.
How a Trust Profile works
A profile starts private on a placeholder address, and nothing is public until you publish it. You choose the address, choose what goes on it from four kinds of item you own, and control both the order and the off switch — the full mechanics are under “Go deeper” below.
Exactly what a published profile shows
A published profile returns the name and short description on the profile, a category you typed in yourself (shown labelled as self-described, because that is what it is), and one status line per item you added. Nothing else about your account is reachable through it.
| Item you add | What the public page shows |
|---|---|
| Verified domain | The domain name and the date its ownership was verified. If the asset is no longer verified, the line says verification is unavailable rather than quietly disappearing. |
| Public badge | The date monitoring on that asset began, and the badge type. If the badge is revoked or switched off, the line says so. |
| Credential | The credential's public identifier, which resolves to its own verification page. Revoked or withdrawn credentials read as no longer active. |
| Monitor uptime | A single uptime percentage over the last 30 days, from the same calculation the dashboard uses. If there is not enough data, it says so instead of estimating. |
What is never on it
- No incident history, no failing checks, no findings, no scores, and no live up/down signal.
- No internal identifiers, no asset ids, no email addresses, and no team member names.
- An unpublished profile and a slug that never existed return the identical response, so nobody can use the address to test whether an organization is a customer.
No status is stored on the profile itself. Every line is recomputed from the source record on each request, so a revoked verification or a disabled badge stops showing the moment it changes — not on the next refresh of something cached.
Renaming does not break a link you already shared
When you change your slug, the old one is kept permanently as an alias pointing at the profile, and it can never be claimed by another organization. Anyone who follows the old address is redirected to the current one with a real permanent redirect from the server, before any page is rendered.
Branding
A profile renders in one of two modes: the default Nivaronix presentation, or your own. Custom Trust Profile branding starts on the Studio plan, and is also included on the contact-sales Scale plan. The gate is presentational only — the evidence on the page, and how it is derived, is identical on every plan.
Compare plansHow a credential is earned
Credentials are awarded automatically, by evaluating your own account data against a published rule. You cannot request one, buy one, or assert one — and neither can we hand you one.
What a third party sees when they check one
Every credential resolves to its own page at /credential/<id>, served by Nivaronix, rendered from live data rather than a stored image. Anyone with the link can open it — no account, no login.
Badges you can embed on your own site
A published profile can issue a badge image that links back to it, and a verified asset can carry a monitoring badge. Both are deliberately restrained about what they say.
Go deeper
Everything above is the whole story at a glance. Open any of these for the detail behind it.