City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 104.152.52.231 | botsattackproxy | Bot attacker IP |
2025-03-25 13:44:38 |
| 104.152.52.145 | botsattackproxy | Vulnerability Scanner |
2025-03-20 13:41:36 |
| 104.152.52.100 | spamattackproxy | VoIP blacklist IP |
2025-03-14 22:09:59 |
| 104.152.52.139 | attack | Brute-force attacker IP |
2025-03-10 13:45:36 |
| 104.152.52.219 | botsattackproxy | Bot attacker IP |
2025-03-04 13:55:48 |
| 104.152.52.124 | botsattackproxy | Vulnerability Scanner |
2025-02-26 17:12:59 |
| 104.152.52.146 | botsattackproxy | Bot attacker IP |
2025-02-21 12:31:03 |
| 104.152.52.161 | botsattackproxy | Vulnerability Scanner |
2025-02-05 14:00:57 |
| 104.152.52.176 | botsattackproxy | Botnet DB Scanner |
2025-01-20 14:03:26 |
| 104.152.52.141 | botsattack | Vulnerability Scanner |
2025-01-09 22:45:15 |
| 104.152.52.165 | botsattackproxy | Bot attacker IP |
2024-09-24 16:44:08 |
| 104.152.52.226 | botsattackproxy | Vulnerability Scanner |
2024-08-28 12:46:53 |
| 104.152.52.142 | spambotsattack | Vulnerability Scanner |
2024-08-26 12:47:13 |
| 104.152.52.116 | spamattack | Compromised IP |
2024-07-06 14:07:26 |
| 104.152.52.204 | attack | Bad IP |
2024-07-01 12:36:27 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.152.52.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46555
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.152.52.212. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022100602 1800 900 604800 86400
;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 07 05:57:51 CST 2022
;; MSG SIZE rcvd: 107212.52.152.104.in-addr.arpa domain name pointer internettl.org.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
212.52.152.104.in-addr.arpa name = internettl.org.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 122.152.210.156 | attack | SSH bruteforce (Triggered fail2ban) |
2020-03-27 19:57:41 |
| 49.232.140.146 | attackspam | Mar 27 13:04:06 pkdns2 sshd\[61151\]: Invalid user ygw from 49.232.140.146Mar 27 13:04:08 pkdns2 sshd\[61151\]: Failed password for invalid user ygw from 49.232.140.146 port 58386 ssh2Mar 27 13:05:29 pkdns2 sshd\[61243\]: Invalid user fnr from 49.232.140.146Mar 27 13:05:30 pkdns2 sshd\[61243\]: Failed password for invalid user fnr from 49.232.140.146 port 50402 ssh2Mar 27 13:06:50 pkdns2 sshd\[61271\]: Invalid user ynr from 49.232.140.146Mar 27 13:06:52 pkdns2 sshd\[61271\]: Failed password for invalid user ynr from 49.232.140.146 port 42408 ssh2 ... |
2020-03-27 19:24:21 |
| 189.126.72.41 | attackspambots | Mar 27 12:01:51 ewelt sshd[17995]: Invalid user cxd from 189.126.72.41 port 33807 Mar 27 12:01:51 ewelt sshd[17995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.126.72.41 Mar 27 12:01:51 ewelt sshd[17995]: Invalid user cxd from 189.126.72.41 port 33807 Mar 27 12:01:53 ewelt sshd[17995]: Failed password for invalid user cxd from 189.126.72.41 port 33807 ssh2 ... |
2020-03-27 19:30:59 |
| 188.212.173.2 | attack | port scan and connect, tcp 80 (http) |
2020-03-27 19:56:19 |
| 188.166.246.46 | attackbots | Invalid user e from 188.166.246.46 port 37962 |
2020-03-27 19:45:26 |
| 137.74.166.77 | attack | 2020-03-27T11:35:08.268598abusebot-7.cloudsearch.cf sshd[16497]: Invalid user jocelyne from 137.74.166.77 port 52388 2020-03-27T11:35:08.272716abusebot-7.cloudsearch.cf sshd[16497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.ip-137-74-166.eu 2020-03-27T11:35:08.268598abusebot-7.cloudsearch.cf sshd[16497]: Invalid user jocelyne from 137.74.166.77 port 52388 2020-03-27T11:35:10.541326abusebot-7.cloudsearch.cf sshd[16497]: Failed password for invalid user jocelyne from 137.74.166.77 port 52388 ssh2 2020-03-27T11:44:12.689933abusebot-7.cloudsearch.cf sshd[17203]: Invalid user cmh from 137.74.166.77 port 35026 2020-03-27T11:44:12.697017abusebot-7.cloudsearch.cf sshd[17203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.ip-137-74-166.eu 2020-03-27T11:44:12.689933abusebot-7.cloudsearch.cf sshd[17203]: Invalid user cmh from 137.74.166.77 port 35026 2020-03-27T11:44:14.644800abusebot-7.cloudsearch.cf ss ... |
2020-03-27 20:03:26 |
| 79.137.34.248 | attack | Mar 27 06:46:07 XXXXXX sshd[36731]: Invalid user h from 79.137.34.248 port 48478 |
2020-03-27 19:52:01 |
| 122.51.21.208 | attackspambots | Invalid user bitnami from 122.51.21.208 port 55988 |
2020-03-27 19:21:21 |
| 106.13.228.62 | attackspambots | Mar 27 07:26:03 vps sshd[13493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.228.62 Mar 27 07:26:04 vps sshd[13493]: Failed password for invalid user orm from 106.13.228.62 port 59892 ssh2 Mar 27 07:34:01 vps sshd[13945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.228.62 ... |
2020-03-27 20:01:23 |
| 163.172.220.189 | attackspam | SSH Brute Force |
2020-03-27 19:41:58 |
| 95.133.6.255 | attack | Unauthorized connection attempt detected, IP banned. |
2020-03-27 19:30:06 |
| 169.55.166.76 | attackspam | Invalid user alex from 169.55.166.76 port 51534 |
2020-03-27 19:22:09 |
| 212.64.7.134 | attack | k+ssh-bruteforce |
2020-03-27 19:44:51 |
| 167.71.128.144 | attackbotsspam | Mar 27 12:22:58 srv-ubuntu-dev3 sshd[54882]: Invalid user lhy from 167.71.128.144 Mar 27 12:22:58 srv-ubuntu-dev3 sshd[54882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.128.144 Mar 27 12:22:58 srv-ubuntu-dev3 sshd[54882]: Invalid user lhy from 167.71.128.144 Mar 27 12:23:00 srv-ubuntu-dev3 sshd[54882]: Failed password for invalid user lhy from 167.71.128.144 port 51102 ssh2 Mar 27 12:26:28 srv-ubuntu-dev3 sshd[55418]: Invalid user vyo from 167.71.128.144 Mar 27 12:26:28 srv-ubuntu-dev3 sshd[55418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.128.144 Mar 27 12:26:28 srv-ubuntu-dev3 sshd[55418]: Invalid user vyo from 167.71.128.144 Mar 27 12:26:30 srv-ubuntu-dev3 sshd[55418]: Failed password for invalid user vyo from 167.71.128.144 port 36532 ssh2 Mar 27 12:29:57 srv-ubuntu-dev3 sshd[55974]: Invalid user vvt from 167.71.128.144 ... |
2020-03-27 19:35:28 |
| 181.48.155.149 | attack | Mar 27 03:22:11 server1 sshd\[2490\]: Failed password for invalid user admin from 181.48.155.149 port 38262 ssh2 Mar 27 03:22:11 server1 sshd\[2491\]: Failed password for invalid user admin from 181.48.155.149 port 38264 ssh2 Mar 27 03:26:28 server1 sshd\[4279\]: Invalid user vdi from 181.48.155.149 Mar 27 03:26:28 server1 sshd\[4279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.155.149 Mar 27 03:26:28 server1 sshd\[4280\]: Invalid user vdi from 181.48.155.149 ... |
2020-03-27 19:53:31 |