testssl icon

Codigo Activacion Disk Drill Repack < REAL ✪ >


testssl.sh

is a free command line tool which checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as recent cryptographic flaws and more.

Codigo Activacion Disk Drill Repack < REAL ✪ >

Operating systems update frequently – Windows 11 24H2, macOS Sequoia, new APFS versions. Legitimate Disk Drill updates fix compatibility bugs. A repack is frozen in time. After a few months, it may crash, fail to see your drive, or blue-screen your PC.

Searching for a free activation code or a repack of Disk Drill is an understandable impulse. Data loss is stressful, and the price of professional software feels high when you are already facing a crisis.

However, the risks are overwhelming. A repack might bring you:

The safest, smartest, and actually cheapest path is to use the official free version of Disk Drill, explore open-source alternatives like PhotoRec, or wait for a legitimate discount. Alternatively, consider that preventing data loss with a $5 cloud backup (Backblaze, iDrive) is cheaper than any recovery tool – repack or not.

Don’t let the search for a phantom codigo activacion turn a recoverable disaster into a permanent catastrophe. Your data is worth more than a cracked license.


Final note: If you have already lost data, stop using the affected drive immediately (do not write new files). Then, download the official Disk Drill trial or TestDisk on a separate computer. Recovering data is hard enough without adding malware into the equation. Stay safe.

Searching for a "codigo activacion disk drill repack" generally leads to unsafe, modified software that poses risks of malware infection, data corruption, and system instability. Official activation requires purchasing a license via the CleverFiles

website, while free alternatives like Disk Drill Basic are available for limited, safe recovery. Risks of Using Cracked Software - Malware - Scribd

Introduction

Disk Drill is a popular data recovery software designed to help users retrieve lost or deleted files from various storage devices. The software offers a user-friendly interface and supports multiple file systems, making it a go-to solution for data recovery needs. In this essay, we will discuss the software's features, the concept of reactivation codes, and the implications of repacking.

Disk Drill: An Overview

Disk Drill is a data recovery software developed by CleverFiles. It allows users to recover deleted files, lost partitions, and corrupted data from various storage devices, including hard drives, USB drives, and SD cards. The software uses advanced algorithms to scan and recover data from damaged or corrupted file systems.

Key Features of Disk Drill

Some of the notable features of Disk Drill include:

Reactivation Codes: What You Need to Know

A reactivation code, also known as a license key or activation code, is a unique string of characters used to activate software and unlock its full features. In the case of Disk Drill, a reactivation code is required to upgrade from the free version to the paid version, which offers additional features and support.

Disk Drill Repack: Understanding the Concept

Repacking software refers to the process of re-packaging software, including its license keys and activation codes, into a single executable file. This allows users to easily distribute and install the software without having to purchase a separate license. However, repacking software can raise concerns about software piracy and copyright infringement.

Implications of Repacking Disk Drill

Repacking Disk Drill or using a reactivation code from an unauthorized source can have several implications: codigo activacion disk drill repack

Conclusion

In conclusion, Disk Drill is a powerful data recovery software that offers a range of features to help users retrieve lost or deleted files. While reactivation codes and repacking software may seem like convenient solutions, they can raise concerns about software piracy, security risks, and lack of official support. It's essential to purchase software licenses from authorized sources and follow best practices to ensure data safety and security.

To protect yourself, avoid any site that:

Legitimate sources:

The quest for a "código de activación" for Disk Drill or consideration of repack options should be approached with caution. While the allure of free or seemingly cost-effective solutions is strong, the risks associated with repack software and unofficial activation codes can outweigh the benefits. Investing in an official license not only supports software development but also provides peace of mind through security, support, and legality. For critical data recovery needs or professional use, the value of a legitimate Disk Drill license cannot be overstated.

Searching for a "codigo activacion disk drill repack" (activation code for a repackaged version of Disk Drill) typically refers to obtaining unauthorized license keys for third-party modified software installers. Using these codes or "repacks" carries significant security and functional risks. Risks of Using Disk Drill Repacks

Malware Exposure: Repackaged software from unofficial sources is a common vector for malware, including ransomware, spyware, and keyloggers.

Data Vulnerability: Since Disk Drill requires high-level system permissions to scan drives, a compromised repack can gain full access to your sensitive files.

Functional Instability: Repacks often disable essential background processes to bypass activation, which can lead to software crashes or incomplete data recovery.

Legal & Ethical Concerns: Using unauthorized activation codes violates the developer’s terms of service and software copyright laws. Official Activation Process

To securely unlock Disk Drill PRO features like unlimited data recovery, you must use a legitimate activation code purchased through the Official CleverFiles Website:

Purchase a License: A lifetime license typically costs around $89.

Enter the Code: Open Disk Drill, click the "Disk Drill" name in the top menu (Mac) or the "Upgrade" button (Windows), and paste your unique code into the Activation Code field.

Offline Activation: If your computer lacks internet access, you can generate an offline activation file to be processed on another device. Free Alternatives

If the cost is a barrier, consider these safer free alternatives for data recovery:

Disk Drill Basic (Free Edition): Allows you to scan and preview all recoverable data for free. On Windows, it includes up to 500MB of free data recovery.

Recuva: A widely used, completely free tool for Windows that is effective for simple file undeletion.

TestDisk/PhotoRec: Open-source, powerful recovery tools that are free but use a command-line interface.

Using "repack" or unauthorized activation codes for Disk Drill poses high risks of malware infection and data corruption, while legitimate activation involves purchasing a license key, which is emailed upon purchase. Users can legitimately preview files and recover up to 500MB for free on Windows, with community-recommended free alternatives including Recuva and PhotoRec. For the official, secure method of activating Disk Drill, visit CleverFiles. Operating systems update frequently – Windows 11 24H2,

You're looking for a way to activate Disk Drill, a popular data recovery software. However, I must emphasize that using cracked or repacked software can pose significant risks to your computer's security and data integrity.

That being said, I'll provide you with some general information about Disk Drill and its activation process. Please note that I'm not encouraging or supporting any illicit activities.

About Disk Drill:

Disk Drill is a data recovery software developed by CleverFiles. It offers a free version with limited features and a paid version with more advanced features.

Activation codes:

I must clarify that obtaining an activation code through unofficial means, such as cracking or repacking, is against the software's terms of use and may be illegal.

If you're looking for a legitimate way to activate Disk Drill, you can:

Risks of using cracked or repacked software:

Using cracked or repacked software can lead to:

Instead of seeking activation codes through unofficial means, I recommend:

Searching for a "repack" or activation code for Disk Drill typically leads to unofficial or cracked versions of the software. While these might promise full features for free, they carry significant security and legal risks. Understanding "Repacks" and Activation Codes

What is a Repack? A repack is a modified version of a program created by a third party, often to reduce file size or include a "crack" that bypasses official licensing.

Activation Codes: Legitimate activation codes for CleverFiles Disk Drill are only sent via email after a purchase on the official website. Codes found on "repack" sites are generally unauthorized and may not work. Risks of Using Repacked Software How to Activate Disk Drill PRO

Disk Drill is a popular data recovery software, and I'll provide a feature related to its activation code.

Feature: Data Recovery with Disk Drill

Disk Drill is a powerful data recovery tool that helps users recover lost or deleted files from various storage devices. With a valid activation code, users can unlock the full potential of Disk Drill and enjoy advanced features.

Key Features:

Activation Code Benefits:

If you're looking for a valid activation code for Disk Drill Repack, I recommend purchasing one from the official website or authorized resellers to ensure you get a genuine and working code. The safest, smartest, and actually cheapest path is

While it may be tempting to search for a "codigo activacion disk drill repack" (Disk Drill activation code repack) to unlock pro features for free, doing so carries significant risks to your data and your computer's security.

This article explores why users seek these "repacks," the hidden dangers involved, and the safest ways to recover your lost files. What is a "Disk Drill Repack"?

In the world of software, a repack is a version of a program that has been modified by a third party. Usually, these versions are compressed for smaller downloads and come "pre-activated" or include a "crack" or "keygen" (key generator).

Users search for these because Disk Drill’s professional version is a paid service. While the free version allows you to scan and preview files, a license is required to actually recover large amounts of data. The Risks of Using Cracked or Repacked Software

Using a modified version of data recovery software is particularly dangerous for several reasons: 1. Malware and Ransomware

Most sites offering "codigo activacion" or "repacks" are not verified. These files often serve as "Trojan horses," hiding malware, spyware, or ransomware. Instead of getting your files back, you might end up locking your entire hard drive and being extorted for money. 2. Data Corruption

Data recovery is a delicate process that requires the software to interact deeply with your drive's file system. Repacked software is often unstable. A glitch during the recovery process can lead to permanent data loss, overwriting the very sectors you are trying to save. 3. No Technical Support or Updates

Disk Drill frequently updates its algorithms to support new file formats and macOS/Windows updates. A cracked version is "frozen" in time. If the recovery fails or the software crashes, you have no access to official support to help save your files. 4. Privacy Violations

Illegal software can include "phone-home" scripts that steal your personal information, passwords, or even the very photos and documents you are trying to recover, uploading them to a remote server. The Safe Way to Use Disk Drill

Instead of risking a repack, consider these legitimate options:

The Free Version: Disk Drill offers a free tier that allows you to recover up to 500MB of data (on Windows) for free. This is often enough for critical documents or a few precious photos.

Official Discounts: CleverFiles (the creators of Disk Drill) often offers discounts for students, non-profits, or users migrating from a competitor's software.

Lifetime Upgrades: Purchasing a legitimate license often includes lifetime upgrades, ensuring you can recover data on future operating systems without ever needing to "crack" the software again. Conclusion

When you have lost important data, the stakes are high. Using a "codigo activacion disk drill repack" adds an unnecessary layer of risk that could result in total hardware failure or identity theft. To ensure your files are recovered safely and your privacy is protected, always download Disk Drill from its official website.

Don't let a quest for "free" software turn a simple data loss into a digital disaster.

Disclaimer: This article is for educational purposes regarding software licensing, security risks, and legal compliance. "Repack" software is often cracked software. Using, distributing, or creating activation codes for proprietary software without a license is illegal and violates copyright laws. The author strongly recommends purchasing a legitimate license from CleverFiles.


When considering the use of a "código de activación" or repack versions of Disk Drill, users should weigh the benefits against the potential risks:

Repack versions of software, including Disk Drill, are modified packages that may offer a pre-activated version of the software or bundle additional software. While repack versions might seem appealing for their cost (often free) or seeming ease of use, there are significant risks involved:

Let’s debunk the myths that keep people searching for codigo activacion disk drill repack.

| Myth | Truth | |------|-------| | "My antivirus only flags it because it’s a crack." | False. Antiviruses flag packed executables and keygens because they behave like malware. Even if it’s "just a crack," the delivery method (downloaders, adware) is dangerous. | | "I’ve used repacks before and nothing happened." | Survivorship bias. Perhaps you were lucky. Or perhaps your PC is part of a botnet and you haven’t noticed the slow down. | | "The repack includes a real activation code." | No. Real codes are unique and sold by CleverFiles. Any public "code" is either expired, blocked, or a generic string. | | "I’ll just uninstall it after I recover my files." | Too late. If malware runs once with admin rights, it persists. Many repacks install rootkits that survive format/reinstall. |

CleverFiles regularly offers:


Key features

License

testssl.sh is free and open source software. You can use it under the terms of GPLv2, please review the License before using it.

Attribution is important for the future of this project -- also in the internet. Thus if you're offering a scanner based on testssl.sh as a public and/or paid service in the internet you are strongly encouraged to mention to your audience that you're using this program and where to get this program from. That helps us to get bugfixes, other feedback and more contributions.

Donations

If you like this software, you or your company uses it a lot or even your company makes money from any service around testssl.sh, why not support the project with a donation? It helps keeping the project alive and kicking.

Dirk setup a paypal account for it, keeps track of the money and makes sure it is spend on project related activities.

Donate with PayPal


If you want a deductable commercial invoice in return please get in touch with me before using paypal.

Development

github Development takes place at github. We're now @ 3.2.3 (stable) and 3.3dev.
There was a last release of 3.0.10 (oldstable) but that was the last one in the 3.0.x branch.



Support status

Supported will always be the current dev version and the version before (n-1 rule). As soon as the dev version becomes the stable release, this will be the n-1 version and receives bugfixes only. The dev version has historically not delivered really broken software (no facebook paradigm). Consider it like a rolling release: It'll definitely change-- that is the point of development-- things might break for you if you e.g. expect the output or features all to be the same. But other than that: The dev version itself won't break (TM).

3.2 is the stable branch. There was one final 3.0.10 release, a.k.a the old stable. If you need longer support for 3.0.x there's a possibility for paid maintenance support. We are focussing on 3.3dev, further development will take place in that branch. We aim to not break things badly but, as said, things will change. If you want to make use of new features like QUIC, TLS 1.3 0-RTT, newer SSLlabs rating, check for the Opossum vulnerability and more, you should consider this branch.

-

February 13, 2026: Prerelease/snapshot of 3.3dev, see github or here (signature) .

February 12, 2026: Release of bugfixed version 3.2.3, see 3.2.3 github or here (signature) .

September 18, 2025: Release of bugfixed version 3.2.2, see 3.2.2 github or here (signature) .

June 15, 2025: Start of new development branch 3.3dev, see 3.3dev github.

June 15,2025: Release of final bugfixed version 3.0.10, see 3.0.10 github or here (signature) .

June 13, 2025: Release of bugfixed version 3.2.1, see 3.2.1 @ github or here (signature) .

April 23, 2025: Release of final stable version 3.2.0, after several release candidates. see 3.2.0 @ github or here (signature) .

Jun 13, 2024: Version 3.0.9, see 3.0.9 @ github or here(signature) .

Oct 10, 2023: After several non-tagged and not labelled rc versions a now version 3.2rc3 was released, see 3.2rc3 @ github

Sep 19, 2022: Version 3.0.8, see 3.0.8 @ github or here(signature) .

Feb 19, 2022: Version 3.0.7, see 3.0.7 @ github or here(signature) .
[..]
Jan 23, 2020: Version 3.0 release, see 3.0 @ github. It's been a long rolling release candidate phase since the first 3.0 RC version.

Dec 12, 2017: ROBOT / Bleichenbacher check has been implemented. . Read more about this old+new attack @ robotattack.org. Please checkout 2.9dev @ github. I compiled also some info here, including an Alexa Top 10k scan and some background information.

Sep 19, 2017: Version 2.9.5 has been released. Please checkout 2.9.5 @ github or download it from here, you need the etc tar ball as well.

Screenshots /Pictures here

The pictures are still from an older version of testssl.sh. This will be updated later. It should suffice to get a picture though.

Longer read

testssl.sh is pretty much portable/compatible. It is working on every Linux, Mac OS X, FreeBSD distribution, on MSYS2/Cygwin (slow). It is supposed also to work on any other unixoid systems. A newer OpenSSL version (1.0) is recommended though. /bin/bash is a prerequisite – otherwise there would be no sockets.

Speaking of it: Since version 2.4 some of the checks were done with bash sockets. This improved gradually and from 2.9.5 on almost every check is done with bash sockets. Still OpenSSL is needed for some core functions like openssl <verify|ocsp|pkey> . In principle any OpenSSL or even LibreSSL can be used as a helper. It's recommended to use the one supplied as it makes sure special tests or features like IPv6, proxy support, STARTTLS MySQL or PostgreSQL are supported. (The one supplied stems originally from github.com/PeterMosmans/openssl. openssl-1.0.2k-chacha.pm.ipv6.Linux+FreeBSD.tar.gz is a Linux- and FreeBSD-only tarball. The directory openssl-1.0.2i-chacha.pm.ipv6.contributed/ contains contributed builds for ARM7l and Darwin binaries).

Download shortcuts

Note the following features are supported by the webserver configuration: – each to standard output. Please note however that from 2.9dev on you need the mandatory files in etc/ though, see https://github.com/testssl/testssl.sh/tree/3.0/etc.

Usage

The normal use case is probably just testssl.sh <hostname>, see first picture right hand above (a deliberately bad configuration).

Starting testssl.sh with no params will give you a general idea how to use it:
userid@somehost:~ % testssl.sh

     "testssl.sh [options] <URI>"    or    "testssl.sh <options>"


"testssl.sh <options>", where <options> is:

     --help                        what you're looking at
     -b, --banner                  displays banner + version of testssl.sh
     -v, --version                 same as previous
     -V, --local                   pretty print all local ciphers
     -V, --local <pattern>         which local ciphers with <pattern> are available? If pattern is not a number: word match

     <pattern>                     is always an ignore case word pattern of cipher hexcode or any other string in the name, kx or bits

"testssl.sh <URI>", where <URI> is:

     <URI>                         host|host:port|URL|URL:port   port 443 is default, URL can only contain HTTPS protocol)

"testssl.sh [options] <URI>", where [options] is:

     -t, --starttls <protocol>     Does a default run against a STARTTLS enabled <protocol,
                                   protocol is <ftp|smtp|lmtp|pop3|imap|xmpp|telnet|ldap|nntp|postgres|mysql>
     --xmpphost <to_domain>        For STARTTLS enabled XMPP it supplies the XML stream to-'' domain -- sometimes needed
     --mx <domain/host>            Tests MX records from high to low priority (STARTTLS, port 25)
     --file/-iL <fname>            Mass testing option: Reads one testssl.sh command line per line from <fname>.
                                   Can be combined with --serial or --parallel. Implicitly turns on "--warnings batch".
                                   Text format 1: Comments via # allowed, EOF signals end of <fname>
                                   Text format 2: nmap output in greppable format (-oG), 1 port per line allowed
     --mode <serial|parallel>      Mass testing to be done serial (default) or parallel (--parallel is shortcut for the latter)
     --warnings <batch|off>        "batch" doesn't continue when a testing error is encountered, off continues and skips warnings
     --connect-timeout <seconds>   useful to avoid hangers. Max <seconds> to wait for the TCP socket connect to return
     --openssl-timeout <seconds>   useful to avoid hangers. Max <seconds> to wait before openssl connect will be terminated

single check as <options>  ("testssl.sh URI" does everything except -E and -g):
     -e, --each-cipher             checks each local cipher remotely
     -E, --cipher-per-proto        checks those per protocol
     -s, --std, --standard         tests certain lists of cipher suites by strength
     -p, --protocols               checks TLS/SSL protocols (including SPDY/HTTP2)
     -g, --grease                  tests several server implementation bugs like GREASE and size limitations
     -S, --server-defaults         displays the server's default picks and certificate info
     -P, --server-preference       displays the server's picks: protocol+cipher
     -x, --single-cipher <pattern> tests matched <pattern> of ciphers
                                   (if <pattern> not a number: word match)
     -c, --client-simulation       test client simulations, see which client negotiates with cipher and protocol
     -h, --header, --headers       tests HSTS, HPKP, server/app banner, security headers, cookie, reverse proxy, IPv4 address

     -U, --vulnerable              tests all (of the following) vulnerabilities (if applicable)
     -H, --heartbleed              tests for Heartbleed vulnerability
     -I, --ccs, --ccs-injection    tests for CCS injection vulnerability
     -T, --ticketbleed             tests for Ticketbleed vulnerability in BigIP loadbalancers
     -BB, --robot                  tests for Return of Bleichenbacher's Oracle Threat (ROBOT) vulnerability
     -R, --renegotiation           tests for renegotiation vulnerabilities
     -C, --compression, --crime    tests for CRIME vulnerability (TLS compression issue)
     -B, --breach                  tests for BREACH vulnerability (HTTP compression issue)
     -O, --poodle                  tests for POODLE (SSL) vulnerability
     -Z, --tls-fallback            checks TLS_FALLBACK_SCSV mitigation
     -W, --sweet32                 tests 64 bit block ciphers (3DES, RC2 and IDEA): SWEET32 vulnerability
     -A, --beast                   tests for BEAST vulnerability
     -L, --lucky13                 tests for LUCKY13
     -F, --freak                   tests for FREAK vulnerability
     -J, --logjam                  tests for LOGJAM vulnerability
     -D, --drown                   tests for DROWN vulnerability
     -f, --pfs, --fs, --nsa        checks (perfect) forward secrecy settings
     -4, --rc4, --appelbaum        which RC4 ciphers are being offered?

tuning / connect options (most also can be preset via environment variables):
     --fast                        omits some checks: using openssl for all ciphers (-e), show only first preferred cipher.
     -9, --full                    includes tests for implementation bugs and cipher per protocol (could disappear)
     --bugs                        enables the "-bugs" option of s_client, needed e.g. for some buggy F5s
     --assume-http                 if protocol check fails it assumes HTTP protocol and enforces HTTP checks
     --ssl-native                  fallback to checks with OpenSSL where sockets are normally used
     --openssl <PATH>              use this openssl binary (default: look in $PATH, $RUN_DIR of testssl.sh)
     --proxy <host:port|auto>      (experimental) proxy connects via <host:port>, auto: values from $env ($http(s)_proxy)
     -6                            also use IPv6. Works only with supporting OpenSSL version and IPv6 connectivity
     --ip <ip>                     a) tests the supplied <ip> v4 or v6 address instead of resolving host(s) in URI
                                   b) arg "one" means: just test the first DNS returns (useful for multiple IPs)
     -n, --nodns <min|none>        if "none": do not try any DNS lookups, "min" queries A, AAAA and MX records
     --sneaky                      leave less traces in target logs: user agent, referer
     --ids-friendly                skips a few vulnerability checks which may cause IDSs to block the scanning IP
     --phone-out                   allow to contact external servers for CRL download and querying OCSP responder
     --add-ca <cafile>             path to <cafile> or a comma separated list of CA files enables test against additional CAs.
     --basicauth <user:pass>       provide HTTP basic auth information.

output options (can also be preset via environment variables):
     --quiet                       don't output the banner. By doing this you acknowledge usage terms normally appearing in the banner
     --wide                        wide output for tests like RC4, BEAST. PFS also with hexcode, kx, strength, RFC name
     --show-each                   for wide outputs: display all ciphers tested -- not only succeeded ones
     --mapping <openssl|           openssl: use the OpenSSL cipher suite name as the primary name cipher suite name form (default)
                iana|rfc             -> use the IANA/(RFC) cipher suite name as the primary name cipher suite name form
                no-openssl|          -> don't display the OpenSSL cipher suite name, display IANA/(RFC) names only
                no-iana|no-rfc>      -> don't display the IANA/(RFC) cipher suite name, display OpenSSL names only
     --color <0|1|2|3>             0: no escape or other codes,  1: b/w escape codes,  2: color (default), 3: extra color (color all ciphers)
     --colorblind                  swap green and blue in the output
     --debug <0-6>                 1: screen output normal but keeps debug output in /tmp/.  2-6: see "grep -A 5 '^DEBUG=' testssl.sh"

file output options (can also be preset via environment variables)
     --log, --logging              logs stdout to '${NODE}-p${port}${YYYYMMDD-HHMM}.log' in current working directory (cwd)
     --logfile|-oL <logfile>       logs stdout to 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}.log'. If 'logfile' is a dir or to a specified 'logfile'
     --json                        additional output of findings to flat JSON file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
     --jsonfile|-oj <jsonfile>     additional output to the specified flat JSON file or directory, similar to --logfile
     --json-pretty                 additional JSON structured output of findings to a file '${NODE}-p${port}${YYYYMMDD-HHMM}.json' in cwd
     --jsonfile-pretty|-oJ <jsonfile>  additional JSON structured output to the specified file or directory, similar to --logfile
     --csv                         additional output of findings to CSV file '${NODE}-p${port}${YYYYMMDD-HHMM}.csv' in cwd or directory
     --csvfile|-oC <csvfile>       additional output as CSV to the specified file or directory, similar to --logfile
     --html                        additional output as HTML to file '${NODE}-p${port}${YYYYMMDD-HHMM}.html'
     --htmlfile|-oH <htmlfile>     additional output as HTML to the specified file or directory, similar to --logfile
     --out(f,F)ile|-oa/-oA <fname> log to a LOG,JSON,CSV,HTML file (see nmap). -oA/-oa: pretty/flat JSON.
                                   "auto" uses '${NODE}-p${port}${YYYYMMDD-HHMM}'. If fname if a dir uses 'dir/${NODE}-p${port}${YYYYMMDD-HHMM}'
     --hints                       additional hints to findings
     --severity <severity>         severities with lower level will be filtered for CSV+JSON, possible values <LOW|MEDIUM|HIGH|CRITICAL>
     --append                      if (non-empty) <logfile>, <csvfile>, <jsonfile> or <htmlfile> exists, append to file. Omits any header
     --outprefix <fname_prefix>    before  '${NODE}.' above prepend <fname_prefix>


Options requiring a value can also be called with '=' e.g. testssl.sh -t=smtp --wide --openssl=/usr/bin/openssl <URI>.
<URI> always needs to be the last parameter.


userid@somehost:~ % 

Details are in the man page.

You are free to check any port – supposed there's any SSL enabled service (TCP) listening. For the service HTTP you can also supply a full URL. STARTTLS services are those which are plaintext and need some kind of an upgrade command to speak TLS. This is very protocol (see difference between IMAP and SMTP) specific. A STARTTLS check with testssl.sh would be invoked with testssl.sh -t pop3 pop.o2online.de:110. Other examples:
testssl.sh --starttls smtp <smtphost>.<tld>:587 
testssl.sh --starttls ftp <ftphost>.<tld>:21
testssl.sh -t xmpp <jabberhost>.<tld>:5222 
testssl.sh -t xmpp --xmpphost <XMPP domain> <jabberhost>.<tld>:5222 
testssl.sh --starttls imap <imaphost>.<tld>:143
The ports in those examples above are just the standard ports. Also here you're free to check any port. //refactor those, see e.g. https://content-security-policy.com/unsafe-hashes/ or just drop tis shit
If you just want to check the mail exchangers of a domain, do it like this: testssl.sh --mx google.com (make sure port 25 outbound is not blocked by your firewall) – see left hand side picture.

With the output option --wide you get where possible a wide output with hexcode of the cipher, OpenSSL cipher suite name, key exchange (with DH size), encryption algorithm, encryption bits size and maybe the RFC cipher suite name.

If you have the file mapping-rfc.txt in the same directory as testssl.sh it displays in the wide outputs also the corresponding RFC style cipher name. If you don't want this, you need to move mapping-rfc.txt away. Another thing: If you want to find out what local ciphers you have and print them pretty, use testssl.sh -V. Ever wondered what hexcode a cipher is? testssl.sh -V x14 lets you search for the hexcode x14. For hexcodes: If you just specify 14 instead of x14 you will get all ciphers returned which have 14 as a low, middle or high byte. For ciphers: You can also supply a word case pattern, e.g. testssl.sh -V CBC puts out every locally available cipher having the Cipher Block Chaining mode in its name.

testssl.sh -x <pattern> <URI> does the same as testssl.sh -V, it only checks the matched pattern at the server, so e.g. testssl.sh -x ECDH google.com checks google.com for ECDH ciphers (and lists also not available ones at the target), testssl.sh -x DHE smtp.posteo.de:465 does a similar thing for the TLS enabled SMTP service.

testssl.sh --file <myfile> let you do mass testing. The syntax of the file is very easy: one cmdline per line. Use comment signs # as you like, blank lines will be skipped, EOF signals the end of the file – what else? ;-).

You can also specify a proxy since version 2.6: testssl.sh --proxy=<proxyhost>:<proxyport> <your_other_cmds_here> will sneak the openssl and bash sockets requests e.g. out of our corporate environment. Proxy authentication is not supported and the port and protocol has to be allowed in the proxy.

Another neat feature: testssl.sh --header <URI> gives you some information on the HTTP header and marks security features in green (see upper black picture on the right hand side), not so good headers range from yellow over brown to red. It also allows you to fingerprint proxies, see lower black picture.


Changes

3.2




       ... branch is stable github only. Changes relative to 3.0 see changelog.

3.0






















Misc

Feedback, bugs and contributions are welcome! Currently there's one git repo at https://github.com/testssl/testssl.sh. Here @ https://testssl.sh you will always find the latest stable version.

Bugs (and fixes) as well as other PRs can by filed at the git repo or send me a mail to dirk aet testssl dot sh.

I post all significant updates on Mastodon or Bluesky. There was a personal twitter account which is deprecated as we don't like nazis or hate speech.  


Services:  If you need a scanning service or consulting get in touch with me..


Imprint