first of all thanks for this great tool, add support for file with Ips so as not to scan a whole range.
taking advantage of showing or saving only desired results
thanks and regards

Introduction

Add ability to scan CDN address using http format: GET / HTTP/1.1. Can be usefull when scanning CloudFront Addresses with bug-domain reserved as proxy: bug:80 instead of using scheme:// restriction.

Background

The behind idea for this is: cdn-ssl with defined custom payloads; are unable to replicate 101 codes for CloudFront target CDN:

bugscanner-go scan cdn-ssl --proxy bug.com --port 80 --target cloudfront.net --payloads "GET / HTTP/1.1[crlf]Host: cloudfront.net[crlf]Connection: Upgrade[crlf]Upgrade: websocket[crlf][crlf]"

Implementation

Could be integrated as a new module cdn-proxy or merged to cdn-ssl with script revision. If it's still possible trough cdn-ssl with some little work-around; please kindly to let me know :)

There is a default payload using HEAD, how do I change it, for example, use GET or PUT or change the whole payload format?

Introduction

Often check for Internet failure, when fails, the script will temporarily stop until checkers giving go signal. This helps to prevent result losses as well maintain a stable scan.

Implementation

Best to integrate it directly instead of new param. Altho it can such as: -check.

How can I save the full results I get from scanning subdomain list. It only saves results which use cloudflare sever to output file . As I'm using termux.
I normally use following command:-
bugscanner-go scan direct -f subdomain.txt -o scanned.txt

Introduction

Currently, the tools only highligh 101 statuses, which, other status code are ignored from the result. It would be helpful if users able to specify status code. For example: 200 or 301 is often usefull to detect domain-frontable. Also, since bugscanner grabs the server name from the header, it is possible to specify what server that would be saved into result. This helps for users to find domain related to CDN such as CloudFront, cloudflare and Akamai.

Implementation

Can be reserved as a new parameter

--server cloudflare --server CloudFront
-server ['cloudflare', 'CloudFront']

--status-code 200 --status-code 301
--status [ 200, 301 ]