-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with tls connection #278
Comments
related - #51 |
You can use my website for testing
|
@hktalent This is because of the missing sni value. this works
This doesn't echo 172.67.210.144 | tlsx -silent This works:
same goes for the host from Shodan as well. |
@ehsandeep Thank you very much Until we can solve the problem of losing important information during SSL 1.3 based IP scanning Any security scanning tool (tlsx, nuclei, etc.) will face such issues Unable to scan directly through IP Before scanning, it is necessary to accurately convert the IP address into a domain name, and then install a secure scanning facility In order to achieve the final desired result At the same time, another question arises, whether there are other domains and Subdomain using the same ip, and whether the current scanning task is completed for these "other domain names" facilities |
Anything else?
SSL data from shodan - https://www.shodan.io/host/172.67.210.144#443
Curl:
Netcat
The text was updated successfully, but these errors were encountered: