You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Probe a host through a given ip from the input list #2667
An input line that gives the ip to probe a target through, like curl --resolve: the connection goes to the ip, and the hostname stays in the Host header and SNI. The JSON line nuclei would use for the same thing (https://github.com/orgs/projectdiscovery/discussions/7862) fits, so one list could feed both tools:
Probing a vhost on a given server, an origin behind a CDN, or one host on each of its servers. The vhost,ip input form builds the URL from the ip and sends the vhost only as the Host header, so there is no SNI, and url and host report the ip. -pa probes the ips DNS returns, not given ones, and the way it passes each ip doesn't reach them correctly. With app.test resolving to 127.0.0.1 and 127.0.0.2, a server on each whose title is its address, and redir.test redirecting to other.test, which resolves to 127.0.0.3 (dev at c9148f0):
That value pins every dial made for the request, so a redirect to another host followed with -fr goes to the probed ip.
IPv6 ips are passed in brackets, which fastdialer doesn't accept as an ip, so those probes fail with no ips provided in dialWrap.
The favicon request and the ztls handshake are made with context.Background(), so they drop the ip and reach the host through DNS, and -maxhr counts errors per host:port, so errors on one ip skip the other ips of the host.
Activity
feat(runner): pin a target to an ip with a JSON input line