Logs for the probe: ts=2026-06-23T10:08:14.459646299Z caller=main.go:118 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Beginning probe" probe=http timeout_seconds=9.5 ts=2026-06-23T10:08:14.472790231Z caller=utils.go:42 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Resolving target address" preferred_ip_protocol=ip6 ts=2026-06-23T10:08:14.988951681Z caller=utils.go:52 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=warn msg="Resolution with preferred IP protocol failed, attempting fallback protocol" fallback_protocol=ip4 err="address d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online: no suitable address found" ts=2026-06-23T10:08:15.515339925Z caller=utils.go:65 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Resolved target address" ip=178.128.87.9 ts=2026-06-23T10:08:15.519670003Z caller=http.go:281 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Making HTTP request" url=http://[178.128.87.9] host=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online ts=2026-06-23T10:08:15.970277015Z caller=http.go:300 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Received HTTP response" status_code=200 ts=2026-06-23T10:08:15.970415216Z caller=http.go:367 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-06-23T17:08:15.526213235+07:00 dnsDone=2026-06-23T17:08:15.526213235+07:00 connectDone=2026-06-23T17:08:15.747859583+07:00 gotConn=2026-06-23T17:08:15.747880554+07:00 responseStart=2026-06-23T17:08:15.970197749+07:00 end=2026-06-23T17:08:15.970399202+07:00 ts=2026-06-23T10:08:15.970473646Z caller=main.go:129 module=http_2xx target=d8t5lkk9f2eob1lf7gpgfshq7xkbumjdg.oast.online level=info msg="Probe succeeded" duration_seconds=1.5005969860000001 Metrics that would have been returned: # HELP probe_dns_lookup_time_seconds Returns the time taken for probe dns lookup in seconds # TYPE probe_dns_lookup_time_seconds gauge probe_dns_lookup_time_seconds 1.042564852 # HELP probe_duration_seconds Returns how long the probe took to complete in seconds # TYPE probe_duration_seconds gauge probe_duration_seconds 1.5005969860000001 # HELP probe_failed_due_to_regex Indicates if probe failed due to regex # TYPE probe_failed_due_to_regex gauge probe_failed_due_to_regex 0 # HELP probe_http_content_length Length of http content response # TYPE probe_http_content_length gauge probe_http_content_length 72 # HELP probe_http_duration_seconds Duration of http request by phase, summed over all redirects # TYPE probe_http_duration_seconds gauge probe_http_duration_seconds{phase="connect"} 0.221667319 probe_http_duration_seconds{phase="processing"} 0.222317273 probe_http_duration_seconds{phase="resolve"} 1.042564852 probe_http_duration_seconds{phase="tls"} 0 probe_http_duration_seconds{phase="transfer"} 0.000201418 # HELP probe_http_redirects The number of redirects # TYPE probe_http_redirects gauge probe_http_redirects 0 # HELP probe_http_ssl Indicates if SSL was used for the final redirect # TYPE probe_http_ssl gauge probe_http_ssl 0 # HELP probe_http_status_code Response HTTP status code # TYPE probe_http_status_code gauge probe_http_status_code 200 # HELP probe_http_version Returns the version of HTTP of the probe response # TYPE probe_http_version gauge probe_http_version 1.1 # HELP probe_ip_protocol Specifies whether probe ip protocol is IP4 or IP6 # TYPE probe_ip_protocol gauge probe_ip_protocol 4 # HELP probe_success Displays whether or not the probe was a success # TYPE probe_success gauge probe_success 1 Module configuration: prober: http