Does curl have a –no-check-certificate option like wget?

I am trying to make a curl request to one of our local development servers running a dev site with a self-signed SSL cert. I am using curl from the command line.

I saw some blog posts mentioning that you can add to the list of certificates or specify a specific (self signed) certificate as valid, but is there a catch-all way of saying “don’t verify” the ssl cert – like the --no-check-certificate that wget has?

Asked By: cwd


Yes. From the manpage:

-k, –insecure

(TLS) By default, every SSL connection curl makes is verified to be
secure. This option allows curl to proceed and operate even for server
connections otherwise considered insecure.

The server connection is verified by making sure the server’s
certificate contains the right name and verifies successfully using
the cert store.

See this online resource for further details:

See also –proxy-insecure and –cacert.

The reference mentioned in that manpage entry describes some of the specific behaviors of -k .

These behaviors can be observed with curl requests to test pages from

curl -X GET
curl: (51) SSL: no alternative certificate subject name matches target host name ''

curl -k -X GET
..returns HTML content...
Answered By: Freiheit

You may use the following command to apply the changes for all connections:

$ echo insecure >> ~/.curlrc

On Windows just create _curlrc text file with ‘insecure’ text in it in your %HOME%, %CURL_HOME%, %APPDATA%, %USERPROFILE% or %USERPROFILE%Application Data directory.

Advantage of using above solution is that it works for all curl commands, but it is not recommended since it may introduce MITM attacks by connecting to insecure and untrusted hosts.

Answered By: kenorb

You are using a self-signed cert. Why don’t you appended the CA to your trusted CA bundle (Linux) or add to the trusted Certificate store (windows)? Or simply use --cacert /Path/to/file with the contents of your trusted self-signed cert file.

The other answers are answering the question based on the wget comparable. However the true ask is how do I maintain a trusted connection with a self-signed cert using curl. Based on many comments security is the top concern in any one of these answers, and the best answer would be to trust the self-signed cert and leave curls security checks intact.

Answered By: user3258557

Adding to user3258557 ‘s answer, let’s say that you need to test some fake server of your own with your own root CA etc. And you just don’t want to use curl’s -k option.

First, let’s create a RSA key for your Root CA:

openssl genrsa -des3 -out rootCA.key 4096

Then, using that key, let’s sign a certificate for our own CA:

openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 1024 -out rootCA.crt

Now, you have a Root CA with private Key and Certificate.

Let’s now generate keys and certificates for our own websites:

openssl genrsa -out 2048

Now, before creating the certificate, we will need a Certificate Signing Request (CSR) first. Then our Root CA will "sign" the CSR and generate the certificate for our website.

openssl req -new -key -out

Let’s finally create the certificate for our website:

openssl x509 -req -in -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out -days 500 -sha256

For ease of use, let’s generate a .pem file using our .crt and .key files as:

cat >

Now, you can run a simple server with this .pem file. Say this server is running at

For curl request, you can just do this:

curl --cacert "rootCA.crt"

Going a step further, if you want to host multiple sites on a port using SNI, you can generate the key for each site, sign the CSR’s and use a curl request like below:

curl --resolve -X GET --cacert "rootCA.crt" --cert "" --key ""
Answered By: Rahul Bharadwaj
Categories: Answers Tags: ,
Answers are sorted by their score. The answer accepted by the question owner as the best is marked with
at the top-right corner.