LDAP DN escaper
This LDAP DN escaper converts a plain attribute value into the escaped form required by RFC 4514 string representations of distinguished names, and it reverses the same mapping when you paste an escaped component back into ordinary characters.
Run — free
Encoding rewrites commas, plus signs, double quotes, backslashes, angle brackets, and semicolons so a hand-built common name, organization unit, or filter fragment can sit inside an RDN without splitting the surrounding DN. Leading number signs and leading or trailing ASCII spaces also receive a backslash so directory servers do not treat them as hex markers or insignificant padding. Decoding accepts both the special-character form and two-digit hex pairs such as backslash-two-C for a comma, and it fails loudly on a lone trailing backslash, a half-finished hex digit, or an illegal escape letter so typos never silently survive into bind DNs or migration scripts. The path is fully deterministic: the same text and mode always produce the same result, with no network calls, no random salts, and no date-dependent shortcuts. Small checks include encoding a surname that contains a comma into backslash-comma form, and decoding a quoted nickname that uses backslash-quote pairs back into real quotation marks. Use it free in the browser for DN hygiene and fixture cleanup, or call the API at $0.002 per successful request when pipelines need reproducible RFC 4514 transforms in CI and directory tooling.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/enc/ldap-dn-escape \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Smith, John"}'const res = await fetch("https://api.kit.forhosting.com/enc/ldap-dn-escape", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Smith, John"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/enc/ldap-dn-escape",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Smith, John"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/enc/ldap-dn-escape", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Smith, John"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Smith, John"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/enc/ldap-dn-escape", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Smith, John"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "enc.ldap_dn_escape",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |