Skip to content
xovris.ai · 5 of 5 fine
Join early access
Menu

Free website check – no sign-up, nothing to install

Find what broke. Fix it. Prove it.

Xovris looks after everything you run – websites, apps, domains, email, code and security – tells you the moment something breaks and works out why, then fixes it with your permission and proves the fix with the same test that failed.

Connects to 14,525 services
Search them all

Runs in your browser – nothing is saved to an account.

What the check keeps

The check runs from your browser and nothing is saved to an account. To keep it free and fair, Xovris counts checks for 25 hours without keeping the readable address and holds a result for 60 seconds; your browser remembers the last address you checked. What the check keeps, and fair use: Privacy · Terms

Connect your app:

xovris.ai – our own domain

Recorded when this page was built, 2 October 2026 at 04:12 UTC. Enter your own address to check it now.

  1. RegistrationFineRegistered until 1 October 2028.2028-10-01Cloudflare, Inc
  2. Name serversFine2 name servers at Cloudflare.ben.ns.cloudflare.combristol.ns.cloudflare.com
  3. DNSSECFineSigned and validated: forged DNS answers are rejected.
  4. Email protectionFineEmail that pretends to come from this domain is stopped (DMARC p=quarantine).Microsoft 365SPF -allDMARC p=quarantine
  5. Certificate rulesFineOnly the certificate authorities named here may issue its certificates.comodoca.comdigicert.comletsencrypt.orgpki.googssl.com

0 to fix · 0 to improve · 5 fine · 0 not confirmed

Proof you can check, not logos

Xovris has no customers to show yet, so this is what it has done on its own estate. Every figure names the run that produced it.

Checks on xovris.ai that answered fine
5/5
Run from this page's build, 2 October 2026 at 04:12 UTC
Command typed to connect a Next.js app – no key copied by hand
1
Recorded wizard run on 1 October 2026, commit fdc8aa0

Works with

Ready-made connections

  • Next.js(beta)
  • React on Vite(beta)
  • Node.js(beta)
  • GitHub(beta)
  • Vercel(beta)
  • Cloudflare DNS(beta)
  • Email(beta)
  • Slack(beta)
  • Webhooks(beta)
  • OpenTelemetry(beta)
  • Sentry(beta)
  • Datadog(beta)
  • New Relic(beta)
  • Claude Code(beta)
  • Codex(beta)
  • Gemini CLI(beta)
  • GitHub Copilot CLI(beta)
  • VS Code(beta)
  • Cursor(beta)
  • LM Studio(beta)
  • Goose(beta)
  • Windsurf(beta)
  • ChatGPT(beta)
  • Claude(beta)
  • Any MCP client(beta)
  • and more through OpenTelemetry and signed webhooks

beta · If a service has an API, a command line or an MCP server, Xovris can connect to it – asking your consent at each step.

Every integration, its state and its permissions

Xovris connects it for you

You sign in and approve. Xovris writes the configuration, proves the first event arrived and moves each rung only on stored evidence. The command line is there if you prefer it.

Setup says done only when it has seen the evidence

Each connection shows where it stands – connected, data arriving, alerts reaching you, fixes allowed – and moves only when Xovris has really received each one.

  1. Connected

    Your credentials were checked with the provider and the answer was read back.

  2. Telemetry received

    The first record – a check result or an event – is stored, not just accepted at the door.

  3. Monitoring verified

    A real event from your deployed app, or a full round of checks, is stored. A test event alone never counts.

  4. Repair authorisedOptional

    When you choose it: a write grant you read scope by scope, covering each zone or project you want Xovris to fix.

Xovris opens the pull request Beta

From the first release, you install the Xovris GitHub App on one repository. Once you agree to the exact words below, Xovris makes the setup change on a new branch and opens a pull request that lists every change – you review it and merge it.

What you agree to, word for word
Xovris may read the files it needs from the repository you choose – package manifests and the files that start your app – and open one pull request on a new branch. Nothing is pushed to its default branch. No file is sent to an AI model.

Changed your mind? Close the pull request and its branch is deleted.

With the first release, Xovris opens this pull request through its GitHub App.

Alerts you have seen arrive before anything breaks

Alerts reach your own email from the first minute – one press on Alerts adds your verified address, nothing to set up. When you add Slack, a test alert shows Slack's own acceptance – and if a channel fails, Xovris says which and sends the alert by email instead.

npx xovris inita recorded run

  1. Xovris – connect your app
  2. Found Next.js, using npm.
  3. Sign in
  4. Your browser opened to approve this sign-in.
  5. Check the browser shows the same code: FVVG-XSWG
  6. Waiting for you to approve in the browser
  7. Signed in to acme
  8. Creating an ingestion key for this app
  9. Created an ingestion-only key
  10. 4 changes in ~/acme-web
  11. install @xovris/next with npm – The Xovris layer over OpenTelemetry for this stack.
  12. create instrumentation.ts – Starts Xovris on the server and reports request errors (Next.js instrumentation hook).
  13. + // Added by npx xovris init - remove with npx xovris remove
  14. + export async function register() {
  15. + if (process.env.NEXT_RUNTIME === 'nodejs') await import('@xovris/next/register');
  16. + }
  17. +
  18. + export { onRequestError } from '@xovris/next';
  19. +
  20. create instrumentation-client.ts – Reports browser errors and unhandled rejections (Next.js 15.3+ client instrumentation).
  21. + // Added by npx xovris init - remove with npx xovris remove
  22. + import '@xovris/next/client';
  23. +
  24. set XOVRIS_INGEST_URL, XOVRIS_INGEST_KEY, NEXT_PUBLIC_XOVRIS_INGEST_URL, NEXT_PUBLIC_XOVRIS_INGEST_KEY in .env.local – The ingest address and an ingestion-only key. The key can only send events.
  25. + XOVRIS_INGEST_URL=https://ingest.test/api/conn1
  26. + XOVRIS_INGEST_KEY=[hidden]
  27. + NEXT_PUBLIC_XOVRIS_INGEST_URL=https://ingest.test/api/conn1
  28. + NEXT_PUBLIC_XOVRIS_INGEST_KEY=[hidden]
  29. Make these changes? Yes
  30. Writing the configuration
  31. Wrote 4 changes; each is listed in .xovris/manifest.json
  32. Sending a labelled test event from this machine
  33. Telemetry received – stored 2026-10-01T19:20:09.213Z
  34. Next
  35. Deploy this change. Monitoring is verified when the first real event from your deployed app is stored.
  36. Follow it live: https://acme.xovris.ai/
  37. Xovris is installed. Remove it any time with npx xovris remove.

Reached in this run:✔ Connected✔ Telemetry received

A real run of the wizard on the Next.js test project in Xovris's install suite, recorded on 1 October 2026 at commit fdc8aa0. Your own run prints the same steps for your project.

What every fix gives you

What broke, what changed and the same test that failed, passing again – in a plain report you keep. Until that test passes, the issue stays open and you pay nothing for it.

Fix report · Resolved: fixed and verified

example.com stopped answering

Sample data
What broke
A DNS record on the path changed.
What changed
example.com (A)Now: 198.51.100.66After: 203.0.113.10
The same test, before and after
The same test, before and afterBeforeAfter
The site answers over HTTPS0 of 3 locations passed3 of 3 locations passed
The checkout page loads0 of 3 locations passed3 of 3 locations passed
Your guarantee
You pay nothing for a fix until the test that failed passes. Until then the issue stays open and Xovris keeps working on it.

Recorded from the product itself on a test domain, example.com. No customer was involved.

Three things to know before you start

What will Xovris change on my systems?

Whatever you allow it to fix. Watching needs no access at all; each connection you grant extends what Xovris can fix, and every fix runs inside what you granted, as the exact change you approved, with its undo written down first.

Every permission, scope by scope

What does it cost me?

Watching is free – 50 monitors, for good. Personal adds fixing: Xovris fixes and proves issues for £34.99 a month, and an issue counts only once it is fixed and proven.Watching is free – 50 monitors, for good. Personal adds fixing: Xovris fixes and proves issues, and an issue counts only once it is fixed and proven. Its price is being set and shows here in your currency.Watching is free – 50 monitors, for good. Personal adds fixing: Xovris fixes and proves issues for US$46.99 a month, and an issue counts only once it is fixed and proven.

Pricing, in full

How do I undo it?

Everything setup changes is recorded, and one command reverses all of it and revokes the key.

How removal works

Let Xovris look after everything you run

Join early access and Xovris starts on everything you run the day accounts open – it keeps checking, alerts you on the channel you choose and shows every fix as it is proven.

Join early access
  1. Join early access with your email address – nothing else is asked.
  2. The day accounts open you get one email, and your workspace is ready.
  3. Enter your website address and Xovris starts checking it – there is nothing to install.