Frequently Asked Questions

Yes, and the Encryption tool itself is encrypted. Which means, no one gets to see how it works.

You'll be licensed to use it on your own private hosts for a specific period of time. And after that period of time expires, the Encryption tool will no longer work. However, the scripts that were encrypted with the Encryption tool during the period when the Encryption tool license was valid, will continue to work for as long as they were configured to be.

To renew your license for the Encryption tool so you can continue to protect additional scripts, click the "Pricing" link located at the top right-hand corner of your screen.

Yes. Your encrypted scripts will work on Macs and any Unix OS. Initially, our Encryption tool (and all the scripts it produced) was compatible with only Mac, Linux & AIX operating systems. However, due to high demand from Windows users, we have now incorporated the Windows Operating system into the list of compatible OSes.

As of July 26th, 2020, you can now use Pyinstaller to convert protected python scripts into an executable. This enables you to bundle your python app into one file and distribute it as you wish. It also removes the dependency of having to install the Python interpreter.
Suppose the following zip file contains your freshly encrypted python script:

After you unzip/extract the zip file, you'll see a directory similar to:
  • enScryption_Jul30-2235PDT-2020

Go into this directory, confirm your encrypted script is working as expected:
  • cd enScryption_Jul30-2235PDT-2020
  • python

To convert your encrypted script to an executable on Windows:
  1. Utilize the included automation script to quickly test your freshly encrypted python script:
    • Double-click the 'fast-eScriptAccess.bat' batch script
  2. To automatically CONVERT your freshly encrypted python script to an executable (.exe) using pyinstaller
    • Double-click the 'autoconvertToexe.bat' batch script
      • This bundles into one file everything you need (python interpreter, imported modules, the encrypted script)
        • This means your users will not have to install or configure anything.
Suppose the following zip file contains your freshly encrypted python script:

After you unzip/extract the zip file, you'll see a directory similar to:
  • enScryption_Jul30-2235PDT-2020

Go into this directory, confirm your encrypted script is working as expected:
  • cd enScryption_Jul30-2235PDT-2020
  • python

To convert your encrypted script to a binary on Linux:
  1. Double-click/run the 'autoconvertTobin' bash script
    • This bundles into one file everything you need (python interpreter, imported modules, the encrypted script)
      • This means your users will not have to install or configure anything.
  1. Credit Card (Visa/Mastercard/Maestro-Laser/Amex)
  2. Paypal (Discover cards are accepted by Paypal)
  3. EUR/USD Cheque/Check
  4. Wire/Bank Transfer
  5. Bitcoin 2 PayPal :
All protected scripts are designed to send out notifications by default in the event of a hack attempt. Notifications will NOT be sent out IF the user runs the protected script as "expected" and "does not" try to figure out how it works!

Why are notifications sent out to begin with?

Think of it as an alarm system. The reason you're on this site is because you want to keep your source code hidden and secure. If attempts are made to crack your home security system, wouldn't you like to know the identities of the perpetrators?

If you do not wish to allow notifications to be sent out to us whenever your encrypted scripts are tampered with, simply create/touch a "notracking" file in the encryption directory. Whenever you encrypt a script, if the encryption tool finds the "notracking" file in the encryption directory, it will NOT insert any tracking code in the script being encrypted.
    As of April 10th, 2021 - our pricing options have changed. Subscription based purchases are no longer necessary. Users can now choose to purchase access to submit scripts for encryption whenever access is needed. There will no automatical renewal of subscriptions.

    Visit "Source Code Encryption & Obfuscation" for more information.

For licenses, upon payment verification, the latest version of the Encryption tool will be automatically generated and the download link for it will be sent to you. You'll receive it within 30 to 60 seconds of payment completion. If you do not receive it within 5 minutes, shoot us an email at

Unless requested otherwise, the download link will be sent to the email address of the account that payment was made with.

For online submission accesses, after payment is confirmed, an email will be sent to you with the login details needed to access the web interface for uploadingscripts.
No. You do not need to encrypt the scripts on the server or host they will run on. There's no need to encrypt your scripts for each OS.

You can encrypt a script on any Mac, Ubuntu or Red Hat system and then be able to run the encrypted script on other Unix or Windows systems. So far, scripts that were encrypted by us have been tested and verified to work on Ubuntu, Red Hat, CentOS, Windows, AIX and Embedded (watered-down) Unix systems...i.e. busybox or Android.

There is two main reasons an encrypted script wouldn't work:

  1. It has either expired or had its name changed to a name different from the name given to it during encryption.
    • Once a script is encrypted, you cannot rename the encrypted script. If you do, it will not function.
    • Once a script expires, to regain the functionaility it provides, you must re-encrypt it and be mindful of the expiration date.

  2. An attempt was made to tamper with it in order to figure out how it works.
    • We are quite aware that our encryption methodology is unique and there is absolutely nothing like it anywhere else on the internet. For this reason, there will be many hackers who will try to break it apart in an effort to replicate it or for some other nefarious reason.
    • To successfully combat this, a series of sensitivity checks are included in all protected scripts. What that means is, whenever our encryption mechanism detects that a user is attempting to do things with an encrypted script that he shouldn't be doing, we will automatically cause the script to self destruct.
    • We take the security of every script encrypted with us very seriously and we do not tolerate any hack attempts to figure out how it works.

    If your script self-destructs, the only way to get it working again is to re-unzip the zip package and re-install it.
Contact us at [ ] if you need additional help. In your email, make sure to provide a copy and paste of all the steps (and their results) that you performed.
There is no "install". Yes, it is safe to use an protected script on your system.

Yes. After encryption, you can expect your script to behave exactly as it was before it was encrypted. Only difference will be, after encryption, no one will be able to view the actual code.

No. Once encrypted, it cannot be decrypted. We recommend creating backups of your original un-encrypted script.
Currently, our encryption algorithm can be used to protect shell, perl, ruby, python, rcode, command line nodejs and php scripts. Those were the most commonly requested languages for encryption.

If the script you wish to encrypt and obfuscate is written in a different unlisted language, no worries. Feel free to contact us at [ ] and provide the following information:

    • The name of the interpreted language your script is written in
    • A sample code written in this interpreted language
    • How you normally go about running the script from the command line
    • The Unix OS(es) you intend to run the protected/encrypted scripts on
  1. Date Management - Assign expiration dates to your scripts
  2. License Management - Regulate the redistribution of all your scripts
  3. User Management - Restrict usage of your scripts to specific Users
  4. Host Management - Restrict usage of your scripts to specific Hosts
  5. Duplication Prevention - Prevent multiple copies of your scripts on a system
  6. Instance Management - Restrict simultaneous or multiple running instances of your scripts
  7. Tamper Resistance - Auto self-destructs whenever a user tries to figure out how it works
    • a) Ensures an encrypted script does not function if it detects that a necessary tool on the system has been altered
          Some users may build a modified version of a binary and then try to use that version to investigate our encryption/obfuscation algorithm.
            - The tamper resistance feature will detect this and will stop the script from working!
      b) Ensures that a protected script never works if the user is doing anything other than running it.
        - There are many interesting ways users can attempt to break a protected script.
        • We monitor for this and we block them at every turn.
      c) Ensures it is impossible for any user to modify a protected script
  8. Access Management - Remotely disable script usage if user is found to be in violation of licensing terms.
    1. Some users have nefarious intentions when they purchase online software. Upon purchasing a software, these users typically request a refund immediately after. And after the refund is given, they continue to use the software.
      • puts an end to this. Our customers have the option to make their script require internet connectivity.
          • If a customer opts to make her script require internet connection, then users of the script will NOT be able to run the script if they're not connected to the internet.
              - This provides script owners control of their commercial scripts in case a user misbehaves.
  9. Report Generator - Get color coded excel spreadsheets detailing where your script(s) are being used.
    • a). Know when your script is being illegally used
      • If your script was meant to be used at the office in San Francisco but you find out it is now being used in France as well, you might want to know how that happened.

Yes. We offer a 60-Day Money Back Guarantee. Refunds will be granted only under 1 condition:

    • If you are actually able to successfully unlock any of our encrypted scripts in under 60 days.
      • Under this scenario, to qualify for the refund, we'll need to see proof.
Contact us at [ ] if you have any questions.
It is highly unlikely for that to happen. One of the many unique attributes which makes our Encryption tool secure is the fact that it is strenghtened on a very frequent basis and the frequency with which it is updated is based solely on the discovery or detection of newly developed hacking tactics.

Since the inception of our website, many users have attempted to break our encryption algorithm. In the very early stages of our tool, some were actually able to crack open a few doors, and once that happened, we detected it and promptly closed the associated loopholes. Given the continous implementations of several countermeasures similar to this, we feel confident that our encryption tool as it stands right now and going forward, is strong enough to ensure access to your most sensitive scripts is well guarded!

If you want more assurance that our Encryption is as strong as we claim it to be, email us a sample script. We'll encrypt it for you and provide you with the encrypted copy. You can then test it out and see if you can crack it. Take your time. Give it to the most experienced hackers you know. Let them take a stab at it. If they can't get to the source code, well, there goes your answer.

Yes, it is very easy to do.

We provide several automation options. Some are built into the encryption tool. Others can be custom developed, at no additional cost, for licensed on-prem users.

If you intend to make a purchase, simply shoot us an email with one or two sample scripts. We'll encrypt them for you and will send you the encrypted copies so you can test them and verify they work exactly as the originals.

Yes. Along with other security measures, we allow users to specify how long a script is to be valid for. After the user specified date, the script will no longer function. If you do not wish for an encrypted script to expire, simply specify 7000d for the expiration. 7000d equals approximately 19+ years.
  1. Protect sensitive information and intellectual property
  2. Eliminate the ability of others to keep tabs on you, if you work in a lab-like environment where everyone has root access
      - Our encryption tool ensures even those with root privileges cant view your scripts
  3. Hide passwords from public view, make it impossible for anyone to access them
  4. Sell your scripts to a third party without giving away any proprietary information
  5. Get alert notifications - Create records of attempts of intellectual thievery
      - Our encryption tool ensures even those with root privileges cant view your scripts
      • Every script obfuscated and encrypted by is protected under the premise that those who run it are simply to run it. When a user of an encrypted script tries to break it apart to see how it works, a record of the attempt will be logged.
        • - This record can then be used (by the script owner) as evidence in a court of law if necessary.
Yes. We can encrypt Shell scripts, Powershell (.ps1), Perl, Ruby scripts, Python scripts, CLI/Web PHP scripts and Rcode scripts.
During submission of your scripts, you may specify how long the encrypted version should be valid for. Examples: 1d (1day), 2w (2weeks), 4mo(4months), 7000d (for 19+ years).

You can:

Purchase and download your own personalized (and encrypted) version of our Encryption tool
  • This option will enable you to avoid submitting any extremely sensitive scripts to our website
    • It allows you to encrypt as many scripts as you need, right from your own private host.

Here are your realistic options:

  1. Rely on permissions/ownership (chmods/chowns) as your only means of protection
  2. Use an open-source obfuscation method - which makes your scripts more likely to be successfully hacked!
  3. Or use our unique, always-evolving encryption algorithm that ensures no one can unveil your protected code
Yes. If you are interested in this particular language, shoot us an email at [ ]. Help us understand your need so we can better customize the enScryption tool to fit your preferences.

There are quite a number of different methods a determined hacker can use to attempt to hack a protected script. One of such ways is altering the binary files of the programming language your script is written in. is aware of these types of tactics and steps have been taken to combat them effectively.

Whenever an protected script is run on a system (unix/linux/windows), it does a variety of checks simulteneously. These checks confirm the validity of all necessary tools needed to run the protected script. If the algorithm senses any of the critical tools it needs have been tampered with or simply aren't in the state it expects them to be in, it will refuse to run the protected script and will abort immediately.

If you're not trying to hack the script, or figure out how our algorithm works, feel free to shoot us an email. In your email, please provide a copy and paste of the exact error messages you encountered and the name of the Operating System your script was run on.
Yes. Your encrypted scripts can run under Android systems. During encryption of the scripts, simply specify "android" instead of "autogenerate" or "embedded" at the command line. To run an encrypted script on an android machine, you can utilize the apps known as "Termux", "Terminal Emulator", "Root Browser".