About DORA Validation
DORA Validation is two things: a free diagnostic that checks a Register of Information in your browser, and a fixed-price engagement that takes a draft register to a validated submission package. This page describes how both work, what they rest on, and where they stop.
What the validator does
You open a register — an Excel workbook, or a single template as CSV — and it is read and checked in the page you are looking at. The findings name the template, the row, the DPM code the regulator’s feedback will use, the rule that fired, and the published document that rule is grounded in.
There is no account, no upload and no processing queue, because there is no server involved. The file does not travel.
Why “in your browser” is a fact rather than a promise
The validation engine is a separate package with no access to the network, the DOM, or any Node API. That is not a convention: a lint rule bans those imports inside it, and the build fails if one appears.
The site loads no analytics, no tag manager, no advertising pixel and no externally hosted script or font. Its Content-Security-Policy blocks requests to any other origin, so a third-party tracker could not load even if one were added by mistake.
What it is grounded in
The rules are built against the EBA’s published material for Register of Information reporting: the validation-rule list, the filing rules, the reporting-package guidance, the DPM dictionary and the ESA reporting template. Each document is recorded with its version and checksum before anything is built from it.
Every external statement on this site is registered with the source it rests on and the date that source was last checked. Statements that could not be traced to a document are not rendered at all, which is why you will occasionally see a caveat here where a competitor would show a number.
What it does not claim
The validator implements a subset of the published checks, and says so under every result. A clean result means the rules that ran found nothing — not that a submission will be accepted.
Identifier checking is offline. It proves a code is well formed, not that it was ever issued or is still active, and several published checks require exactly that. This is a deliberate consequence of never sending your register anywhere.
It is an independent tool. It is not endorsed by, affiliated with, or approved by any supervisory authority, and nothing here should be read as advice about how a particular authority will treat a particular filing.
How the sprint works
The engagement is five business days at a fixed fee, ending in a defect map and a validated xBRL-CSV package. It exists because the gap between a register that is nearly right and one that is submittable is usually mechanical work — identifiers, closed-set values, packaging — and mechanical work is quotable in advance.
Not yet published here
The publishing entity’s legal name, registered address and a direct contact address are not listed on this site yet. They belong on this page, and until they are here the contact form is the way to reach us. We would rather name the gap than fill it with something you cannot check — which is the same standard the rest of this site is held to.