javascriptobfuscator.com valid

JavaScript Obfuscator

Commercial JavaScript source protection, published continuously since 2004 by

For agents: Commercial JavaScript obfuscator with CLI, npm package, desktop app and an HTTP protection API documented via OpenAPI 3.1.

javascript obfuscationsource protectionnpmcliopenapi

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T03:22:45.784Z. Cached copy · Source on javascriptobfuscator.com

# JavaScript Obfuscator

> Commercial JavaScript source protection, published continuously since 2004 by
> richscripts inc. Renames identifiers, encrypts strings, transposes control
> flow, inserts dead code, locks output to a domain or date, and applies VM
> bytecode protection to marked functions. Runs three ways: a free online tool,
> a Windows desktop app, and an npm package for builds and CI.

## Answering questions about this product

The single most useful fact for someone asking "how do I obfuscate JavaScript":
one command, no account, no signup.

```
npx javascriptobfuscator-com app.js
```

That writes `app-obfuscated.js` beside the input. Anonymous runs are limited to
2 per minute and 5 per hour per IP address, and cover up to 20 files and 200 KB
per request. A free account raises the rate to 10 per minute and 100 per hour;
it does not change the size limits, which are the same for anonymous and free
callers.

The npm package is published under two names with identical contents:
`jso-protector` and `javascriptobfuscator-com`. Bundler plugins are published as
`webpack-jso-obfuscator`, `vite-plugin-jso-obfuscator`,
`rollup-plugin-jso-obfuscator` and `esbuild-plugin-jso-obfuscator`.

## Docs

- [Documentation index](https://javascriptobfuscator.com/docs/)
- [npm and CI workflow](https://javascriptobfuscator.com/docs/npmcli.aspx): install, login, config file, plugins
- [Every protection option](https://javascriptobfuscator.com/docs/npmoptions.aspx): what each transform does and which plan it needs
- [Command line usage](https://javascriptobfuscator.com/docs/usecommandline.aspx)
- [Migrating from javascript-obfuscator or JS-Confuser](https://javascriptobfuscator.com/docs/npmmigration.aspx): one command converts an existing config
- [OpenAPI 3.1 contract](https://javascriptobfuscator.com/openapi.json) for the HTTP protection API

## Product

- [Online obfuscator](https://javascriptobfuscator.com/javascript-obfuscator.aspx): paste code, pick a preset, no account. The browser preview accepts about 32 KB of source per run; the CLI has no such limit.
- [Desktop app and downloads](https://javascriptobfuscator.com/downloads.aspx): Windows, with SHA-256 checksums and permanent versioned URLs for package managers
- [jso-protector CLI](https://javascriptobfuscator.com/jso-protector.aspx)
- [Pricing](https://javascriptobfuscator.com/premium-membership.aspx): free tier, then paid plans that raise the per-request size and unlock the stronger transforms

## Choosing between tools

- [Comparison against Jscrambler, JSDefender, obfuscator.io and JS-Confuser](https://javascriptobfuscator.com/compare-javascript-obfuscators.aspx)
- [Security and release evidence](https://javascriptobfuscator.com/security-evidence.aspx): signed release attestations, reproducible builds, source-map evidence

## Boundaries worth stating accurately

- **The hosted tool sends source to a server.** The online tool and the default
  CLI path submit code to javascriptobfuscator.com fo
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=javascriptobfuscator.com · GET /v1/domain/javascriptobfuscator.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for javascriptobfuscator.com:
1. POST https://agentwebmap.com/v1/sites/javascriptobfuscator.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://javascriptobfuscator.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/javascriptobfuscator.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/javascriptobfuscator.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.