Supported provider
deSEC DNS, in the same place as everything else.
Does DNSMentor support deSEC?
Yes. DNSMentor manages deSEC DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every deSEC change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting deSEC
- Create the credential in deSEC desec.io → log in → Token Management → Create Token. The 28-character secret is shown once, at creation, and cannot be retrieved afterwards. A fresh token has every permission switched off and full access to every domain: tick 'Can create domains' / 'Can delete domains' only if you want DNSMentor to be able to, and add a token policy per domain to scope it down. The same screen takes an 'allowed subnets' list — restrict it to this platform's egress addresses, because an unrestricted token is the whole DNS account.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose deSEC, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the deSEC account holds and imports every record in them. This is a read operation — nothing is written to any zone.
- Group by client and start working Assign the imported domains to client portfolios, and the estate view, health scoring, checks and audit trail apply from that point on.
What deSEC asks you for
The exact fields DNSMentor needs, and where in deSEC to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
API Token secret desec.io → log in → Token Management → Create Token. The 28-character secret is shown once, at creation, and cannot be retrieved afterwards. A fresh token has every permission switched off and full access to every domain: tick 'Can create domains' / 'Can delete domains' only if you want DNSMentor to be able to, and add a token policy per domain to scope it down. The same screen takes an 'allowed subnets' list — restrict it to this platform's egress addresses, because an unrestricted token is the whole DNS account.
The sharp edge in deSEC's API
Every provider API has one behaviour that catches integrations out. This is deSEC's, and DNSMentor's adapter is written around it — the sort of thing you would otherwise discover during a migration.
What you get on top of the deSEC console
One estate, not one provider
deSEC zones sit beside every other provider your clients came with, grouped by the client who pays for them and searchable in one place.
56 checks before apply
The deSEC console will accept a second SPF record or an MX pointing at an address without comment. DNSMentor will not.
Approval and audit
A second pair of eyes where policy requires it, and a hash-chained record of who changed what — neither of which a provider console offers.
deSEC questions
Can I manage deSEC DNS alongside my other providers?
Yes. DNSMentor connects deSEC through its API and shows its zones in the same estate view as every other provider you connect — 26 are supported in total. Your engineers work in one interface instead of switching between provider portals, and the same checks, approval policy and audit trail apply regardless of which provider a domain happens to be with.
What credentials does DNSMentor need for deSEC?
DNSMentor needs API Token for deSEC. desec.io → log in → Token Management → Create Token. The 28-character secret is shown once, at creation, and cannot be retrieved afterwards. A fresh token has every permission switched off and full access to every domain: tick 'Can create domains' / 'Can delete domains' only if you want DNSMentor to be able to, and add a token policy per domain to scope it down. The same screen takes an 'allowed subnets' list — restrict it to this platform's egress addresses, because an unrestricted token is the whole DNS account.
Does DNSMentor move my zones away from deSEC?
No. Your zones stay hosted at deSEC and remain authoritative there. DNSMentor reads and writes through the deSEC API, so nothing about your resolution path changes, and if you stop using DNSMentor the zones carry on exactly as they are.
Does DNSMentor validate deSEC changes before applying them?
Yes. All 56 checks run against the zone as it would exist after the change, whichever provider hosts it. The change is then simulated, routed for approval if policy requires it, written through the deSEC API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect deSEC in about five minutes.
Paste one credential, sync, and see every zone in that account. It is a read operation — nothing is written until somebody presses apply.
No card. No trial clock. UK-hosted, and we will tell you which providers we have actually proven before you ask.
Last updated