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.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5411
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.152.52.2. IN A
;; AUTHORITY SECTION:
. 290 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030300 1800 900 604800 86400
;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 01:02:55 CST 2022
;; MSG SIZE rcvd: 105
2.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:
2.52.152.104.in-addr.arpa name = internettl.org.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 106.12.186.74 | attackspam | Mar 1 06:56:01 gw1 sshd[28068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.186.74 Mar 1 06:56:03 gw1 sshd[28068]: Failed password for invalid user miaohaoran from 106.12.186.74 port 35286 ssh2 ... |
2020-03-01 10:01:06 |
| 180.250.115.121 | attackspambots | $f2bV_matches |
2020-03-01 13:02:46 |
| 85.239.42.180 | attack | Postfix RBL failed |
2020-03-01 10:08:55 |
| 45.33.70.146 | attackbotsspam | Unauthorized connection attempt detected from IP address 45.33.70.146 to port 22 [J] |
2020-03-01 10:08:01 |
| 108.59.8.70 | attackspambots | Automatic report - Banned IP Access |
2020-03-01 09:38:42 |
| 49.235.91.92 | attack | Lines containing failures of 49.235.91.92 Feb 25 12:35:07 install sshd[11148]: Invalid user pms from 49.235.91.92 port 48562 Feb 25 12:35:07 install sshd[11148]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.91.92 Feb 25 12:35:10 install sshd[11148]: Failed password for invalid user pms from 49.235.91.92 port 48562 ssh2 Feb 25 12:35:10 install sshd[11148]: Received disconnect from 49.235.91.92 port 48562:11: Bye Bye [preauth] Feb 25 12:35:10 install sshd[11148]: Disconnected from invalid user pms 49.235.91.92 port 48562 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.235.91.92 |
2020-03-01 09:39:04 |
| 70.31.200.12 | attackspambots | Automatic report - Port Scan Attack |
2020-03-01 09:40:09 |
| 175.6.108.125 | attack | SSH brute force |
2020-03-01 10:01:49 |
| 185.143.223.166 | attackspambots | Mar 1 02:25:36 grey postfix/smtpd\[19873\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.166\]: 554 5.7.1 Service unavailable\; Client host \[185.143.223.166\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[185.143.223.166\]\; from=\<36t5a1c62kbb@jmb-production.fr\> to=\ |
2020-03-01 09:39:47 |
| 46.60.1.10 | attack | 20/2/29@17:47:10: FAIL: Alarm-Intrusion address from=46.60.1.10 ... |
2020-03-01 09:44:43 |
| 222.254.25.239 | attackspambots | Brute force attempt |
2020-03-01 09:35:39 |
| 59.127.1.12 | attackspambots | Feb 29 18:58:04 NPSTNNYC01T sshd[13599]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.127.1.12 Feb 29 18:58:06 NPSTNNYC01T sshd[13599]: Failed password for invalid user ubuntu from 59.127.1.12 port 35012 ssh2 Feb 29 19:04:24 NPSTNNYC01T sshd[14009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.127.1.12 ... |
2020-03-01 09:50:21 |
| 202.51.110.214 | attack | Mar 1 06:28:14 gw1 sshd[25702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.51.110.214 Mar 1 06:28:16 gw1 sshd[25702]: Failed password for invalid user cron from 202.51.110.214 port 51540 ssh2 ... |
2020-03-01 09:43:31 |
| 112.134.129.187 | attack | *Port Scan* detected from 112.134.129.187 (LK/Sri Lanka/-). 7 hits in the last 220 seconds |
2020-03-01 10:04:51 |
| 201.242.216.164 | attack | Feb 29 15:47:32 kapalua sshd\[520\]: Invalid user test from 201.242.216.164 Feb 29 15:47:32 kapalua sshd\[520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.242.216.164 Feb 29 15:47:34 kapalua sshd\[520\]: Failed password for invalid user test from 201.242.216.164 port 36772 ssh2 Feb 29 15:53:04 kapalua sshd\[935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.242.216.164 user=mysql Feb 29 15:53:07 kapalua sshd\[935\]: Failed password for mysql from 201.242.216.164 port 49765 ssh2 |
2020-03-01 09:58:19 |