This IP address has been reported a total of
7
times from
7 distinct
sources.
142.147.179.205 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 1
report;
United Kingdom of Great Britain and Northern Ireland
with 1
report;
Italy
with 1
report.
The most common categories in these recent reports were:
Bad Web Bot
2
times;
Exploited Host
1
time;
Web App Attack
1
time;
DDoS Attack
1
time.
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.
Fail2Ban: 142.147.179.205 was banned for Aggressive Bad Bot detected by Nginx/Fail2Ban. UA: Mozilla/ ...
show moreFail2Ban: 142.147.179.205 was banned for Aggressive Bad Bot detected by Nginx/Fail2Ban. UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36
show less
Bad Web Bot
Anonymous
Distributed web crawl botnet attack (like Mellowtel), likely illicit scraping of AI training data to ...
show moreDistributed web crawl botnet attack (like Mellowtel), likely illicit scraping of AI training data to bypass firewall/robots.txt restrictions in thread-skip.asp
show less
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/Marque-Scott/Famille-Addict&resultsPerPage=24&order=product.r
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
