Logs for the probe:
ts=2026-04-15T06:44:56.384393771Z caller=main.go:118 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Beginning probe" probe=http timeout_seconds=9.5
ts=2026-04-15T06:44:56.39537102Z caller=utils.go:42 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Resolving target address" preferred_ip_protocol=ip6
ts=2026-04-15T06:44:56.658569587Z caller=utils.go:52 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=warn msg="Resolution with preferred IP protocol failed, attempting fallback protocol" fallback_protocol=ip4 err="address d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online: no suitable address found"
ts=2026-04-15T06:44:56.911289468Z caller=utils.go:65 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Resolved target address" ip=178.128.87.9
ts=2026-04-15T06:44:56.916060659Z caller=http.go:281 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Making HTTP request" url=http://[178.128.87.9] host=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online
ts=2026-04-15T06:44:57.393712846Z caller=http.go:300 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Received HTTP response" status_code=200
ts=2026-04-15T06:44:57.393812786Z caller=http.go:367 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Response timings for roundtrip" roundtrip=0 start=2026-04-15T13:44:56.922604731+07:00 dnsDone=2026-04-15T13:44:56.922604731+07:00 connectDone=2026-04-15T13:44:57.157307238+07:00 gotConn=2026-04-15T13:44:57.157333921+07:00 responseStart=2026-04-15T13:44:57.393647237+07:00 end=2026-04-15T13:44:57.393801209+07:00
ts=2026-04-15T06:44:57.393850961Z caller=main.go:129 module=http_2xx target=d7fj7oaikr7reh86u1p0jxmcocu7jc88k.oast.online level=info msg="Probe succeeded" duration_seconds=1.001150058



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 0.515926841
# HELP probe_duration_seconds Returns how long the probe took to complete in seconds
# TYPE probe_duration_seconds gauge
probe_duration_seconds 1.001150058
# 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.234729186
probe_http_duration_seconds{phase="processing"} 0.236313342
probe_http_duration_seconds{phase="resolve"} 0.515926841
probe_http_duration_seconds{phase="tls"} 0
probe_http_duration_seconds{phase="transfer"} 0.000153946
# 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