Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
Type Details Datetime
proxy
VPN boot fraud
2023-06-13 20:34:07
Comments on same subnet:
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
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.152.52.108
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25204
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.152.52.108.			IN	A

;; AUTHORITY SECTION:
.			572	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022021202 1800 900 604800 86400

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 13:11:27 CST 2022
;; MSG SIZE  rcvd: 107
Host info
108.52.152.104.in-addr.arpa domain name pointer internettl.org.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
108.52.152.104.in-addr.arpa	name = internettl.org.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.185.54 attackbotsspam
Invalid user hgw from 106.12.185.54 port 46942
2020-05-22 17:23:21
195.54.167.17 attackbots
May 22 10:43:34 debian-2gb-nbg1-2 kernel: \[12395832.391056\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=195.54.167.17 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=26256 PROTO=TCP SPT=44313 DPT=30786 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-22 17:00:17
91.193.172.154 attack
1590119536 - 05/22/2020 05:52:16 Host: 91.193.172.154/91.193.172.154 Port: 445 TCP Blocked
2020-05-22 16:56:36
192.99.4.63 attack
Flask-IPban - exploit URL requested:/wp-login.php
2020-05-22 17:32:27
186.177.64.26 attack
Unauthorized connection attempt from IP address 186.177.64.26 on Port 445(SMB)
2020-05-22 17:24:16
110.8.67.146 attackspambots
May 21 23:05:19 web1 sshd\[620\]: Invalid user ukd from 110.8.67.146
May 21 23:05:19 web1 sshd\[620\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.8.67.146
May 21 23:05:21 web1 sshd\[620\]: Failed password for invalid user ukd from 110.8.67.146 port 60762 ssh2
May 21 23:09:22 web1 sshd\[1122\]: Invalid user uxe from 110.8.67.146
May 21 23:09:22 web1 sshd\[1122\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.8.67.146
2020-05-22 17:11:22
117.35.118.42 attackbots
May 22 07:53:28 jane sshd[32409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.35.118.42 
May 22 07:53:30 jane sshd[32409]: Failed password for invalid user newuser from 117.35.118.42 port 47428 ssh2
...
2020-05-22 17:09:26
95.217.121.163 attackspambots
slow and persistent scanner
2020-05-22 17:10:03
92.63.98.59 attack
23 attempts against mh-misbehave-ban on tree
2020-05-22 16:57:08
118.69.65.4 attackspambots
May 22 10:43:39 host sshd[24026]: Invalid user pbk from 118.69.65.4 port 55011
...
2020-05-22 17:03:28
222.186.175.23 attack
May 22 11:29:59 *host* sshd\[7936\]: User *user* from 222.186.175.23 not allowed because none of user's groups are listed in AllowGroups
2020-05-22 17:30:12
134.175.121.80 attackbots
SSH Brute-Force reported by Fail2Ban
2020-05-22 16:56:18
186.84.172.25 attackbots
May 22 01:08:39 mockhub sshd[25017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.84.172.25
May 22 01:08:42 mockhub sshd[25017]: Failed password for invalid user kid from 186.84.172.25 port 42378 ssh2
...
2020-05-22 17:19:49
138.197.5.191 attack
Invalid user paf from 138.197.5.191 port 44738
2020-05-22 17:00:54
162.243.139.107 attack
Connection by 162.243.139.107 on port: 2222 got caught by honeypot at 5/22/2020 7:59:00 AM
2020-05-22 17:05:29

Recently Reported IPs

104.149.159.141 104.152.52.116 104.152.52.130 104.149.145.29
104.152.52.139 104.152.52.134 104.152.52.138 104.152.52.119
104.152.52.111 104.149.204.15 104.152.52.167 104.152.52.185
104.152.52.73 104.152.52.159 104.152.52.168 104.152.57.149
104.152.52.165 104.154.104.47 104.152.52.177 104.152.52.55