This IP address has been reported a total of
20
times from
15 distinct
sources.
121.124.60.50 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 8
reports;
Czechia
with 2
reports;
France
with 2
reports.
The most common categories in these recent reports were:
Brute-Force
10
times;
Web App Attack
6
times;
Bad Web Bot
5
times;
Port Scan
4
times;
Exploited Host
3
times;
Other
5
times.
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.
Oct 7 19:31:06 canopus postfix/smtpd[3753118]: NOQUEUE: reject: RCPT from unknown[121.124.60.50]: 5 ...
show moreOct 7 19:31:06 canopus postfix/smtpd[3753118]: NOQUEUE: reject: RCPT from unknown[121.124.60.50]: 554 5.7.1 Service unavailable; Client host [121.124.60.50] blocked using zen.spamhaus.org; Listed by CSS, see https://check.spamhaus.org/query/ip/121.124.60.50 / Listed by XBL, see https://check.spamhaus.org/query/ip/121.124.60.50; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<45.74.31.47>
Oct 7 20:26:43 canopus postfix/smtpd[3758005]: NOQUEUE: reject: RCPT from unknown[121.124.60.50]: 554 5.7.1 Service unavailable; Client host [121.124.60.50] blocked using zen.spamhaus.org; Listed by CSS, see https://check.spamhaus.org/query/ip/121.124.60.50 / Listed by XBL, see https://check.spamhaus.org/query/ip/121.124.60.50; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<45.74.31.50>
Oct 8 00:58:35 canopus postfix/smtpd[3776051]: NOQUEUE: reject: RCPT from unknown[121.124.60.50]: 554 5.7.1 Service unavailable; Client host [121.124.60.50] blocked u
...
show less
Not following 301 redirects โ wasted requests | method: GET | path: / | ua: Mozilla/5.0 (Windows NT ...
show moreNot following 301 redirects โ wasted requests | method: GET | path: / | ua: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36 | 2026-10-07 14:37 UTC
show less
Email account brute force: 1 attempts were recorded from 121.124.60.50
2026-10-07T10:25:13+02:00 war ...
show moreEmail account brute force: 1 attempts were recorded from 121.124.60.50
2026-10-07T10:25:13+02:00 warning: unknown[121.124.60.50]: SASL PLAIN authentication failed: authentication failure, [email protected]show less
Not following 301 redirects โ wasted requests | method: GET | path: /wp-json/ | ua: Mozilla/5.0 (Win ...
show moreNot following 301 redirects โ wasted requests | method: GET | path: /wp-json/ | ua: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36 | 2026-10-06 23:21 UTC
show less
This address requested our sites, was answered with a redirect (HTTP 301 โ to https, to www, or to t ...
show moreThis address requested our sites, was answered with a redirect (HTTP 301 โ to https, to www, or to the page's current address) and never followed it, nor read any page that day. A browser follows a redirect within the second; a scanner enumerating hosts never does. Such requests are not as harmless as they seem: millions of addresses make them, they came close to half of all the requests our servers received, and they are a real waste of resources โ human time, log storage, CPU and network โ so we apply a zero-tolerance policy: one unfollowed redirect with no page read is enough to be blocked. Please take this seriously and stop the process behind these useless requests. | method: POST | path: /api/graphql | ua: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
show less
Bad Web Bot
Anonymous
Web probing (2 hits in 24h) on default-vhost,limburgsekunstkring.nl: sensitive-path scans and/or 404 ...
show moreWeb probing (2 hits in 24h) on default-vhost,limburgsekunstkring.nl: sensitive-path scans and/or 404 bursts. Reported by CRMON.
show less
Honeypot trap triggered: unsolicited TCP connection(s) to unused port(s) 23 on a host running no suc ...
show moreHoneypot trap triggered: unsolicited TCP connection(s) to unused port(s) 23 on a host running no such service. There is no legitimate reason to connect to these ports.
Observed 3 connection(s) from 2026-10-04T20:27:49Z to 2026-10-04T20:27:54Z UTC.
2026-10-04T20:27:49Z tcp/23 connect, no payload (bare TCP probe)
2026-10-04T20:27:53Z tcp/23 connect, no payload (bare TCP probe)
2026-10-04T20:27:54Z tcp/23 connect, no payload (bare TCP probe)
Connection was blocked automatically at the firewall. Reported by an automated honeypot.
show less