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.221
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24957
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.152.52.221. IN A
;; AUTHORITY SECTION:
. 249 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022100700 1800 900 604800 86400
;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 08 00:23:21 CST 2022
;; MSG SIZE rcvd: 107221.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:
221.52.152.104.in-addr.arpa name = internettl.org.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 151.80.144.255 | attackbotsspam | $f2bV_matches |
2019-11-01 01:18:43 |
| 68.183.127.93 | attackspambots | Oct 31 04:31:25 tdfoods sshd\[12888\]: Invalid user Passw0rd_1 from 68.183.127.93 Oct 31 04:31:25 tdfoods sshd\[12888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.127.93 Oct 31 04:31:27 tdfoods sshd\[12888\]: Failed password for invalid user Passw0rd_1 from 68.183.127.93 port 41360 ssh2 Oct 31 04:35:27 tdfoods sshd\[13188\]: Invalid user murai from 68.183.127.93 Oct 31 04:35:27 tdfoods sshd\[13188\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.127.93 |
2019-11-01 00:43:33 |
| 51.77.145.82 | attackbotsspam | Oct 31 15:27:02 vps691689 sshd[2459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.145.82 Oct 31 15:27:05 vps691689 sshd[2459]: Failed password for invalid user !QAZxsw23 from 51.77.145.82 port 47536 ssh2 ... |
2019-11-01 01:00:13 |
| 129.204.90.220 | attack | Oct 31 17:20:13 vps sshd[2651]: Failed password for root from 129.204.90.220 port 49376 ssh2 Oct 31 17:38:36 vps sshd[3432]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.90.220 Oct 31 17:38:38 vps sshd[3432]: Failed password for invalid user computerunabh\303\244ngig from 129.204.90.220 port 35694 ssh2 ... |
2019-11-01 00:57:41 |
| 118.244.213.168 | attackspambots | fail2ban honeypot |
2019-11-01 00:48:02 |
| 2.81.172.237 | attackbotsspam | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/2.81.172.237/ PT - 1H : (12) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : PT NAME ASN : ASN3243 IP : 2.81.172.237 CIDR : 2.80.0.0/14 PREFIX COUNT : 14 UNIQUE IP COUNT : 1704960 ATTACKS DETECTED ASN3243 : 1H - 1 3H - 2 6H - 4 12H - 6 24H - 7 DateTime : 2019-10-31 13:02:19 INFO : Port SSH 22 Scan Detected and Blocked by ADMIN - data recovery |
2019-11-01 00:54:51 |
| 142.44.184.79 | attackbotsspam | Oct 31 15:00:19 dedicated sshd[20218]: Invalid user test01 from 142.44.184.79 port 56678 |
2019-11-01 00:39:07 |
| 94.29.124.106 | attackspambots | Unauthorized connection attempt from IP address 94.29.124.106 on Port 445(SMB) |
2019-11-01 00:55:10 |
| 222.186.169.192 | attackbots | Brute force attempt |
2019-11-01 01:00:37 |
| 45.136.110.47 | attackbots | Oct 31 17:17:42 mc1 kernel: \[3824981.433590\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=49593 PROTO=TCP SPT=54723 DPT=6701 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 31 17:18:16 mc1 kernel: \[3825015.354208\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=60250 PROTO=TCP SPT=54723 DPT=6974 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 31 17:20:32 mc1 kernel: \[3825151.739574\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.110.47 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=54080 PROTO=TCP SPT=54723 DPT=7469 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2019-11-01 00:49:44 |
| 66.110.234.108 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/66.110.234.108/ US - 1H : (247) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : US NAME ASN : ASN22709 IP : 66.110.234.108 CIDR : 66.110.224.0/20 PREFIX COUNT : 18 UNIQUE IP COUNT : 60416 ATTACKS DETECTED ASN22709 : 1H - 1 3H - 1 6H - 1 12H - 1 24H - 1 DateTime : 2019-10-31 13:02:04 INFO : Port Scan TELNET Detected and Blocked by ADMIN - data recovery |
2019-11-01 01:05:43 |
| 106.13.67.54 | attackbots | Oct 31 19:28:30 server sshd\[5265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.67.54 user=root Oct 31 19:28:32 server sshd\[5265\]: Failed password for root from 106.13.67.54 port 43190 ssh2 Oct 31 19:38:56 server sshd\[7834\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.67.54 user=root Oct 31 19:38:58 server sshd\[7834\]: Failed password for root from 106.13.67.54 port 45384 ssh2 Oct 31 19:44:24 server sshd\[9219\]: Invalid user 22 from 106.13.67.54 Oct 31 19:44:24 server sshd\[9219\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.67.54 ... |
2019-11-01 01:09:43 |
| 85.110.114.68 | attack | Unauthorized connection attempt from IP address 85.110.114.68 on Port 445(SMB) |
2019-11-01 00:50:05 |
| 106.12.203.177 | attackbots | Oct 31 03:50:35 php1 sshd\[24720\]: Invalid user ubuntu from 106.12.203.177 Oct 31 03:50:35 php1 sshd\[24720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.203.177 Oct 31 03:50:37 php1 sshd\[24720\]: Failed password for invalid user ubuntu from 106.12.203.177 port 35096 ssh2 Oct 31 03:57:24 php1 sshd\[25379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.203.177 user=root Oct 31 03:57:26 php1 sshd\[25379\]: Failed password for root from 106.12.203.177 port 47140 ssh2 |
2019-11-01 00:38:07 |
| 45.83.8.117 | attack | Fail2Ban Ban Triggered |
2019-11-01 00:51:46 |