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.107
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20286
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.152.52.107. IN A
;; AUTHORITY SECTION:
. 531 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020702 1800 900 604800 86400
;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 11:54:45 CST 2022
;; MSG SIZE rcvd: 107107.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:
107.52.152.104.in-addr.arpa name = internettl.org.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 168.90.89.35 | attackspambots | SSH Attack |
2020-07-06 14:21:31 |
| 27.3.178.159 | attackspambots | 20/7/5@23:53:07: FAIL: IoT-Telnet address from=27.3.178.159 ... |
2020-07-06 14:06:38 |
| 192.144.230.221 | attackbotsspam | 2020-07-06T03:49:46.527662abusebot-6.cloudsearch.cf sshd[6413]: Invalid user dennis from 192.144.230.221 port 44560 2020-07-06T03:49:46.533477abusebot-6.cloudsearch.cf sshd[6413]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.230.221 2020-07-06T03:49:46.527662abusebot-6.cloudsearch.cf sshd[6413]: Invalid user dennis from 192.144.230.221 port 44560 2020-07-06T03:49:48.662554abusebot-6.cloudsearch.cf sshd[6413]: Failed password for invalid user dennis from 192.144.230.221 port 44560 ssh2 2020-07-06T03:52:53.293414abusebot-6.cloudsearch.cf sshd[6434]: Invalid user jader from 192.144.230.221 port 46412 2020-07-06T03:52:53.298774abusebot-6.cloudsearch.cf sshd[6434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.230.221 2020-07-06T03:52:53.293414abusebot-6.cloudsearch.cf sshd[6434]: Invalid user jader from 192.144.230.221 port 46412 2020-07-06T03:52:55.432862abusebot-6.cloudsearch.cf sshd[6434 ... |
2020-07-06 14:22:49 |
| 95.187.138.216 | attackbots | Unauthorized connection attempt from IP address 95.187.138.216 on Port 445(SMB) |
2020-07-06 14:39:26 |
| 92.241.145.72 | attack | Jul 6 06:23:32 vpn01 sshd[5245]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.241.145.72 Jul 6 06:23:34 vpn01 sshd[5245]: Failed password for invalid user lilei from 92.241.145.72 port 37652 ssh2 ... |
2020-07-06 14:36:02 |
| 164.132.196.98 | attackspambots | (sshd) Failed SSH login from 164.132.196.98 (FR/France/98.ip-164-132-196.eu): 5 in the last 3600 secs |
2020-07-06 14:09:30 |
| 134.209.197.218 | attackspambots | $f2bV_matches |
2020-07-06 14:47:49 |
| 186.250.193.222 | attackbotsspam | (smtpauth) Failed SMTP AUTH login from 186.250.193.222 (BR/Brazil/186-250-193-222.ibl.com.br): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-07-06 08:22:32 plain authenticator failed for ([186.250.193.222]) [186.250.193.222]: 535 Incorrect authentication data (set_id=ar.davoudi) |
2020-07-06 14:41:43 |
| 91.185.153.193 | attack | 1594007603 - 07/06/2020 05:53:23 Host: 91.185.153.193/91.185.153.193 Port: 445 TCP Blocked |
2020-07-06 14:04:02 |
| 213.174.10.58 | attackbots | VNC brute force attack detected by fail2ban |
2020-07-06 14:07:08 |
| 5.196.67.41 | attack | Jul 6 10:04:05 gw1 sshd[5184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.67.41 Jul 6 10:04:08 gw1 sshd[5184]: Failed password for invalid user mfa from 5.196.67.41 port 49144 ssh2 ... |
2020-07-06 14:04:15 |
| 159.89.153.54 | attackspam | 2020-07-06T07:54:07.695750ks3355764 sshd[23542]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.153.54 user=root 2020-07-06T07:54:09.422817ks3355764 sshd[23542]: Failed password for root from 159.89.153.54 port 33640 ssh2 ... |
2020-07-06 14:46:37 |
| 54.235.65.168 | attackspambots | 5x Failed Password |
2020-07-06 14:11:36 |
| 211.179.124.162 | attack | Jul 6 02:26:58 NPSTNNYC01T sshd[5646]: Failed password for root from 211.179.124.162 port 54392 ssh2 Jul 6 02:29:12 NPSTNNYC01T sshd[5897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.179.124.162 Jul 6 02:29:14 NPSTNNYC01T sshd[5897]: Failed password for invalid user ubuntu from 211.179.124.162 port 57586 ssh2 ... |
2020-07-06 14:37:34 |
| 14.229.228.189 | attackspambots | Jul 6 05:52:51 vps647732 sshd[18882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.229.228.189 Jul 6 05:52:53 vps647732 sshd[18882]: Failed password for invalid user admina from 14.229.228.189 port 50411 ssh2 ... |
2020-07-06 14:31:33 |