I tried to dnsspoof the victim machine for say "www.imdb.com" (with the help of setoolkit and ettercap). But the site is ssl https, so I read here that dnsspoof won't work for https sites. As quoted in the link provided :

As part of the SSL handshake process, your server will need to send a valid certificate for securesite.com which contains the public key.

At this point, you have 2 options.

1) Send the legitimate certificate. This will check out since the certificate is signed by a trusted CA. The client will then encrypt the master secret using the public key. It breaks down at this point, because without the private key, you cannot decrypt the master secret and thus you can't finish the connection setup.

Is there a way to "send the legitimate certificate" ?

  • 1
    if this would work, we wouldn't call HTTPS 'secure'.
    – Lukas
    Commented Oct 26, 2017 at 13:26
  • I tried sslstrip2 , it worked on Firefox , but not on chrome Commented Oct 26, 2017 at 13:32

1 Answer 1


Is there a way to "send the legitimate certificate" ?

If you are the owner of the site you want to spoof then you can get a legitimate certificate from a CA trusted by the browser.

If you are not the legitimate owner you will hopefully not be able to get such a certificate. If you want to create something for internal tests only then you can create your own CA and use this CA to issue your own certificates. Of course you have to add this CA as trusted in each client you want to spoof in order to be treated as a legitimate certificate.

For more see Does https prevent man in the middle attacks by proxy server?

  • What about sslstrip2 and sslstrip with dns2proxy? Commented Oct 26, 2017 at 13:33
  • 1
    @AmanGrover: your question was about sending a legitimate certificate. With sslstrip no kind of certificate is sent to the client and thus the legitimacy of a certificate is irrelevant. Commented Oct 26, 2017 at 13:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .