Dettogni Control Framework

Most businesses own their website.
Far fewer control it.

The website exists.
The control often doesn't.

A business commissions a website. A provider manages the hosting, the domain, the backups, the email routing. Everything works, until a provider disappears, a subscription lapses, or a platform shuts down. The business then discovers it never actually held the pieces it assumed it did.

Most businesses cannot confidently answer who controls their domain, who controls DNS, or whether they could recover the website independently. The Dettogni Control Framework exists to answer one question: does this business actually control the website it depends on, not just own it.

Three steps.
One recommendation.

The framework produces findings and a recommendation. Here is how it is applied.

i

Start here

What can be seen from outside

Domain records, DNS and TLS show part of the picture from the outside. Some dimensions cannot be judged from a URL alone; the framework says exactly which.

ii

If it is worth investigating

What only a conversation shows

Backup ownership, recovery testing, who is actually accountable. These need the people involved.

iii

Whatever it finds

A clear next step

If control is reasonable, nothing needs to change. If the site is rebuilt on Keep’s setup, Keep can look after it. If real gaps exist, Foundation takes responsibility for it. Either way, the recommendation is grounded in evidence, not built to justify a sale.

Not theory.
A pattern seen enough times to name.

The same pattern kept recurring. A business would commission a website. Everything worked, until it didn't, and the business discovered it couldn't answer simple questions: who owns the domain, who controls DNS, who can recover the website, who is responsible when something breaks.

The problem was rarely technical. It was operational. The website existed. The control did not. Existing audits did not address this well: website audits focus on design, SEO audits focus on rankings, security audits focus on vulnerabilities. None of them ask whether the organisation controls the website it depends on.

The framework was written by Alex Ulfeldt, a security engineer. Read the full background →

The way in

Most businesses
find out the hard way.
You don't have to.

A twenty-minute call covers what the framework would find on your website, and whether Keep, Foundation, or nothing at all is the right next step.

No charge. No obligation. If the honest answer is that nothing needs to change, that will be the outcome of the call.

Request a discovery call

Dettogni Control Framework · United Kingdom