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 of America (the)

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
104.52.29.49 attackbots
Unauthorized connection attempt detected from IP address 104.52.29.49 to port 4567 [J]
2020-01-27 15:44:03
104.52.29.49 attackspam
Unauthorized connection attempt detected from IP address 104.52.29.49 to port 4567 [J]
2020-01-22 08:12:21
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.52.2.157
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32451
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.52.2.157.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 14 07:17:54 CST 2025
;; MSG SIZE  rcvd: 105
Host info
157.2.52.104.in-addr.arpa domain name pointer 104-52-2-157.lightspeed.sntcca.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
157.2.52.104.in-addr.arpa	name = 104-52-2-157.lightspeed.sntcca.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
189.142.4.114 attackspambots
" "
2019-11-06 07:24:19
91.219.237.244 attack
Automatic report - XMLRPC Attack
2019-11-06 07:05:10
222.186.173.215 attackbots
Tried sshing with brute force.
2019-11-06 07:21:11
118.24.54.178 attackbots
Nov  5 04:01:18 server sshd\[27826\]: Failed password for invalid user public from 118.24.54.178 port 34462 ssh2
Nov  6 01:17:39 server sshd\[27127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.54.178  user=root
Nov  6 01:17:41 server sshd\[27127\]: Failed password for root from 118.24.54.178 port 48908 ssh2
Nov  6 01:39:05 server sshd\[32225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.54.178  user=root
Nov  6 01:39:07 server sshd\[32225\]: Failed password for root from 118.24.54.178 port 33545 ssh2
...
2019-11-06 06:59:57
111.231.137.158 attack
Nov  5 23:38:02 SilenceServices sshd[13841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.137.158
Nov  5 23:38:04 SilenceServices sshd[13841]: Failed password for invalid user cms from 111.231.137.158 port 41698 ssh2
Nov  5 23:42:13 SilenceServices sshd[16651]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.137.158
2019-11-06 06:57:49
218.92.0.207 attackbotsspam
Nov  6 00:00:28 eventyay sshd[4904]: Failed password for root from 218.92.0.207 port 37450 ssh2
Nov  6 00:01:12 eventyay sshd[4907]: Failed password for root from 218.92.0.207 port 33400 ssh2
...
2019-11-06 07:11:38
81.22.45.83 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-06 07:04:56
123.215.174.101 attack
(sshd) Failed SSH login from 123.215.174.101 (KR/South Korea/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Nov  5 22:09:00 andromeda sshd[28677]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.215.174.101  user=root
Nov  5 22:09:01 andromeda sshd[28677]: Failed password for root from 123.215.174.101 port 54296 ssh2
Nov  5 22:39:01 andromeda sshd[32340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.215.174.101  user=root
2019-11-06 07:02:49
83.15.183.137 attackspam
Nov  5 23:42:03 MK-Soft-VM7 sshd[22432]: Failed password for root from 83.15.183.137 port 42082 ssh2
...
2019-11-06 07:13:38
125.135.97.216 attack
Unauthorised access (Nov  6) SRC=125.135.97.216 LEN=40 TTL=52 ID=23141 TCP DPT=23 WINDOW=6888 SYN
2019-11-06 07:09:13
110.164.189.53 attackbots
$f2bV_matches
2019-11-06 07:15:58
210.120.63.89 attackbotsspam
Nov  5 12:34:55 web1 sshd\[9188\]: Invalid user week from 210.120.63.89
Nov  5 12:34:55 web1 sshd\[9188\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.120.63.89
Nov  5 12:34:57 web1 sshd\[9188\]: Failed password for invalid user week from 210.120.63.89 port 43762 ssh2
Nov  5 12:39:25 web1 sshd\[9651\]: Invalid user Fenetre1@3 from 210.120.63.89
Nov  5 12:39:25 web1 sshd\[9651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.120.63.89
2019-11-06 06:50:05
106.13.195.84 attack
Nov  5 23:38:59 vps01 sshd[24532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.195.84
Nov  5 23:39:01 vps01 sshd[24532]: Failed password for invalid user Bonjour123 from 106.13.195.84 port 60578 ssh2
2019-11-06 07:03:13
210.56.20.181 attackbotsspam
2019-11-05T22:39:12.720235abusebot-5.cloudsearch.cf sshd\[31709\]: Invalid user deployer from 210.56.20.181 port 60508
2019-11-06 06:57:09
45.141.84.20 attackspambots
RDP Bruteforce
2019-11-06 07:00:57

Recently Reported IPs

186.91.109.95 101.142.198.106 177.148.94.177 222.208.153.147
128.236.238.62 246.55.128.32 87.248.93.48 18.104.163.215
3.211.122.106 161.91.217.216 124.52.227.250 25.228.156.236
212.39.88.22 36.236.229.244 138.155.87.234 248.141.72.5
187.158.232.190 185.64.203.235 200.189.22.226 50.44.104.69