Skip to content

Connect Cloudflare DNS

Every domain is watched from outside with no connection at all: its registration, its name servers, DNSSEC and its records, as anyone on the internet sees them. Connecting Cloudflare adds two things – Xovris keeps every verified version of your records, so a change can be explained in plain words, and, only if you allow it, puts a changed record back and proves the fix with the same check that failed. Every other record is left exactly as it was.

Terminal window
# Cloudflare serves the zone when its name servers end in ns.cloudflare.comdig +short NS yourdomain.com
Connect it

This works in Xovris today. Start free and it is yours from your first sign-in.

Xovris does the setup for you. In the command centre, open Connections, enter your domain and press Sign in with Cloudflare: Cloudflare’s own sign-in opens, you approve the access listed below and choose the zones Xovris may see, and Xovris takes it from there – it reads your zones back, keeps the first verified copy of your records and starts watching. Signing in and approving stay yours, because only the account’s owner may grant access; Xovris waits while you do and carries on the moment it has what it needs. The connection counts as connected only once Xovris has read your zones back – where each connection stands shows it.

Do it yourself instead. Press Do it yourself instead beside the sign-in button: Xovris opens Cloudflare’s token page with Zone Read and DNS Read already chosen, you limit it to your domain, create it and paste it in. Xovris shows exactly what the token can reach before anything is saved, seals it and never shows it again.

What Cloudflare DNS lets Xovris fix

  • Only if you allow repairs: to put a changed record back to its last verified version under your standing policy.

Can read

  • See your zones and their settings – To find the zone you chose and confirm its name servers.
  • Read DNS records – To keep every verified version of your records, so a change can be explained and undone.

Can change

  • Change DNS records – Only if you allow repairs: to put a changed record back to its last verified version under your standing policy.

To take it back: Do it yourself instead: revoke the Xovris grant in your Cloudflare profile; Xovris notices the revocation and stops offering repairs.

Watching needs no permission to change anything. When you allow repairs, a record that changed away from its last verified version can be put back under the standing policy you set. The check that failed runs again afterwards: if it does not pass, the change is put back as it was and the next approach starts – the incident stays open, and you pay nothing for it until a fix is proven.

Domains at any other DNS provider are watched from outside in the same way today; repairs through their own access are added provider by provider. The integrations directory shows each one’s state.

Press Disconnect on the connection and Xovris removes itself: it stops using the grant at once, revokes it at Cloudflare and confirms it is gone – nothing it held can be used again – then keeps watching the domain from outside. Do it yourself instead: revoke the Xovris grant in your Cloudflare profile; Xovris notices the revocation, stops offering repairs and keeps watching the domain from outside.

Ask Xovris

Open the full page

Your data is never used to train our AI. How your data is kept

A problem is called fixed only once it works again. How each fix is checked

XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.