Encrypt | Secrets | Decrypt
This service offers a seamless solution for securely managing sensitive information. Whether you need to encrypt or decrypt data, it provides reliable protection for your digital secrets. With robust encryption algorithms and on-demand functionality, safeguarding your information has never been easier.
Generate RSA keys and optionally specify a callback URL to receive the keys.
curl -X POST https://encrypto.reverse.rocks/api/generate/ \
-H "Content-Type: application/json" \
-d '{
"size": 2048,
"callback_url": "http://example.com/callback"
}'
Return private and public keys, also send it to the callback if exists.
{
"callback_status": "success",
"public_key": "-----BEGIN PUBLIC KEY-----\n...",
"private_key": "-----BEGIN PRIVATE KEY-----\n..."
}
Read More...
The size of the RSA key to generate. (512, 1024, 2048, 4096)
The URL to which the public and private keys will be sent as a JSON payload.
FAQ
Q: What is Encrypto?
A: This service provides secure encryption and decryption of data using RSA keys. Users can generate RSA keys, encrypt messages with a public key, and decrypt messages with a private key. The service ensures data protection with SSL encryption and never saves or analyzes the data sent.
Q: What are the valid key sizes for generating keys?
A: The service supports key sizes of 512, 1024, 2048, 4096 bits.
Q: What is the maximum length of the message that can be encrypted or decrypted?
A: The maximum length for the message that can be encrypted or decrypted is 500 characters.
Q: How does rate limiting work for this service?
A: Rate limiting is set to 3 requests per minute per IP address for key generation, encryption, and decryption operations. If the rate limit is exceeded, further requests will be blocked until the rate limit interval resets.
Q: How is the callback URL used in key generation?
A: When generating keys, the service sends both the public and private keys to the specified callback URL as a JSON payload.
Q: How is data protected during transmission?
A: All data transmitted to and from the service is protected using SSL encryption. The service does not analyze or store the data sent by users.
Encrpyt message using RSA public key.
curl -X POST https://encrypto.reverse.rocks/api/encrypt/ \
-H "Content-Type: application/json" \
-d '{
"public_key": "-----BEGIN PUBLIC KEY-----\n...",
"message": "Hello, World!",
"callback_url": "http://example.com/callback"
}'
Return encrypted message and callback status.
{
"callback_status": "success",
"encrypted_message": "U2FsdGVkX1/3AXc4Q1iZ2m5cbkblz/lCgAeMZDVRz7M="
}
FAQ
Q: What format should the public key be in?
A: The public key should be in PEM format and passed as a string.
Q: Can I receive a notification after the message is encrypted?
A: Yes, if you provide a callback_url, the service will send the client IP address to this URL after the encryption process is completed.
Q: Is there a rate limit for using the encrypt function?
A: Yes, the function is rate-limited to 3 requests per minute per IP address. If the limit is exceeded, the service will return a 429 error.
Q: What format is the encrypted message returned in?
A: The encrypted message is returned as a base64-encoded string, which is suitable for transmission over text-based protocols like HTTP.
Q: Is the message or the encryption key stored on the server?
A: No, neither the message nor the encryption key is stored on the server. The service processes the encryption request in memory and immediately returns the result.
Decrypt message using RSA private key.
curl -X POST https://encrypto.reverse.rocks/api/encrypt/ \
-H "Content-Type: application/json" \
-d '{
"private_key": "-----BEGIN PRIVATE KEY-----",
"encrypted_message": "U2FsdGVkX1/3AXc4Q1iZ2m5cbkblz/lCgAeMZDVRz7M=",
"callback_url": "http://example.com/callback"
}'
Return encrypted message and callback status.
{
"callback_status": "success",
"decrypted_message": "Hello, World!"
}
FAQ
Q: What format should the private key be in?
A: The private key should be in PEM format and passed as a string.
Q: What format should the encrypted message be in?
A: The encrypted message should be a base64-encoded string, which is the output from the encryption process.
Q: Can I receive a notification after the message is decrypted?
A: Yes, if you provide a callback_url, the service will send the client IP address to this URL after the decryption process is completed.
Q: What format is the decrypted message returned in?
A: The decrypted message is returned as a plaintext string.
Q: Is the message or the decryption key stored on the server?
A: No, neither the message nor the encryption key is stored on the server. The service processes the encryption request in memory and immediately returns the result.
Business Support
For those looking to integrate this encryption service into their in-house systems, RudeNet offers fully tailored solutions. We provide comprehensive support for secure and private implementations, with no limitations on customization. Our in-house solutions are designed to protect your data with the highest security standards, ensuring that all encryption processes remain confidential and secure.
Contact RudeNet to explore how we can seamlessly integrate advanced encryption technology into your infrastructure while maintaining top-level security and privacy.