This IP address has been reported a total of
5
times from
5 distinct
sources.
170.23.3.63 was first reported on
, and the most recent report was
.
Recent Reports:
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
L7 DDoS: distributed flood on a shop's faceted search โ automated requests to search/sort URLs, one ...
show moreL7 DDoS: distributed flood on a shop's faceted search โ automated requests to search/sort URLs, one or two per address from thousands of addresses, no page assets loaded | path: /18-velo-route | query: q=Stock+magasin-Cycling+H%C3%A9nin%5C-Beaumont-Cycling+Montpellier/Taille-M-XL-55/Famille-Speedster&resultsPerPage=12&order=prod | 2026-08-26 22:11 UTC
show less
Blocked abusive HTTP application-layer DoS / botnet traffic from 170.23.3.63: traffic from this addr ...
show moreBlocked abusive HTTP application-layer DoS / botnet traffic from 170.23.3.63: traffic from this address continues high-cost dynamic page and feed requests at abusive rates via TCP/HTTPS despite edge block responses. Likely compromised end-user host.
show less
Triggered by FP Score: 4 (Chrome on Linux without desktop environment (possible headless); Chrome wi ...
show moreTriggered by FP Score: 4 (Chrome on Linux without desktop environment (possible headless); Chrome with zero-patch version 149.0.0.0 (automated); Suspicious ASN: 'Servers.com, Inc.'; Invalid rDNS on hosting network; WebGL Software Renderer detected: ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver); Score reduced: single-axis anomaly (likely human); UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36) / reCAPTCHA challenge timed out
show less
Coordinated application-layer DDoS against git.mills.io (self-hosted Gitea), 2026-06-12 ~20:30-21:10 ...
show moreCoordinated application-layer DDoS against git.mills.io (self-hosted Gitea), 2026-06-12 ~20:30-21:10 UTC. Deliberately expensive multi-label Gitea issue-search queries (/issues?type=all&state=closed&sort=...&labels=<multiple IDs>, ~60-113s CPU each) flooded the backend via proxy/hosting networks. ~36,700 source IPs, ~1 request per IP, identical TLS fingerprint (TLS1.3 0x1301) and one spoofed Chrome UA = single automated tool.
show less