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: None

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.119.52.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6045
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.119.52.92.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 03:55:41 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 92.52.119.134.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 92.52.119.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.176.27.194 attackspam
Port scan: Attack repeated for 24 hours
2019-11-27 08:26:20
183.161.33.80 attack
Fail2Ban Ban Triggered
2019-11-27 08:17:21
51.79.52.224 attack
2019-11-27T00:09:38.584586abusebot-7.cloudsearch.cf sshd\[24880\]: Invalid user myh0540 from 51.79.52.224 port 43410
2019-11-27 08:14:22
52.240.142.141 attackbotsspam
Bruteforce on SSH Honeypot
2019-11-27 08:13:19
66.249.64.159 attack
404 NOT FOUND
2019-11-27 08:39:09
60.161.21.60 attackspam
2019-11-27T09:55:47.069248luisaranguren sshd[370000]: Connection from 60.161.21.60 port 56248 on 10.10.10.6 port 22 rdomain ""
2019-11-27T09:55:49.256968luisaranguren sshd[370000]: Invalid user pi from 60.161.21.60 port 56248
2019-11-27T09:55:47.070588luisaranguren sshd[370001]: Connection from 60.161.21.60 port 56246 on 10.10.10.6 port 22 rdomain ""
2019-11-27T09:55:49.362395luisaranguren sshd[370001]: Invalid user pi from 60.161.21.60 port 56246
...
2019-11-27 08:10:21
185.173.35.61 attackspambots
Nov 26 23:55:23 : SSH login attempts with invalid user
2019-11-27 08:40:14
51.79.18.171 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.18.171  user=daemon
Failed password for daemon from 51.79.18.171 port 56804 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.18.171  user=daemon
Failed password for daemon from 51.79.18.171 port 56864 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.18.171  user=bin
2019-11-27 08:29:19
170.130.187.26 attackbotsspam
Attack Signature
Audit: Possible RDP Scan Attempt 2
Targeted Application
C:\WINDOWS\SYSTEM32\SVCHOST.EXE
2019-11-27 08:16:10
192.34.61.49 attack
Nov 26 23:48:30 ns382633 sshd\[9638\]: Invalid user ts3ovh from 192.34.61.49 port 43653
Nov 26 23:48:30 ns382633 sshd\[9638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.34.61.49
Nov 26 23:48:33 ns382633 sshd\[9638\]: Failed password for invalid user ts3ovh from 192.34.61.49 port 43653 ssh2
Nov 26 23:55:05 ns382633 sshd\[10973\]: Invalid user samdra from 192.34.61.49 port 34005
Nov 26 23:55:05 ns382633 sshd\[10973\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.34.61.49
2019-11-27 08:42:26
115.231.73.154 attackspambots
Nov 27 01:55:51 debian sshd\[21943\]: Invalid user admin from 115.231.73.154 port 57211
Nov 27 01:55:51 debian sshd\[21943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.231.73.154
Nov 27 01:55:54 debian sshd\[21943\]: Failed password for invalid user admin from 115.231.73.154 port 57211 ssh2
...
2019-11-27 08:08:08
54.37.136.87 attackbotsspam
Nov 27 02:32:05 server sshd\[26303\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.ip-54-37-136.eu  user=root
Nov 27 02:32:07 server sshd\[26303\]: Failed password for root from 54.37.136.87 port 34902 ssh2
Nov 27 02:49:41 server sshd\[30315\]: Invalid user www from 54.37.136.87
Nov 27 02:49:41 server sshd\[30315\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.ip-54-37-136.eu 
Nov 27 02:49:43 server sshd\[30315\]: Failed password for invalid user www from 54.37.136.87 port 42708 ssh2
...
2019-11-27 08:07:40
190.144.135.118 attack
2019-11-26T23:47:22.906952shield sshd\[21334\]: Invalid user test from 190.144.135.118 port 49596
2019-11-26T23:47:22.911140shield sshd\[21334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.144.135.118
2019-11-26T23:47:25.295028shield sshd\[21334\]: Failed password for invalid user test from 190.144.135.118 port 49596 ssh2
2019-11-26T23:50:46.004039shield sshd\[22002\]: Invalid user webmaster from 190.144.135.118 port 38791
2019-11-26T23:50:46.008072shield sshd\[22002\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.144.135.118
2019-11-27 08:12:22
222.186.175.169 attackbots
Nov 27 01:00:31 tux-35-217 sshd\[13488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.169  user=root
Nov 27 01:00:32 tux-35-217 sshd\[13488\]: Failed password for root from 222.186.175.169 port 12076 ssh2
Nov 27 01:00:35 tux-35-217 sshd\[13488\]: Failed password for root from 222.186.175.169 port 12076 ssh2
Nov 27 01:00:39 tux-35-217 sshd\[13488\]: Failed password for root from 222.186.175.169 port 12076 ssh2
...
2019-11-27 08:04:34
88.22.100.14 attack
Automatic report - SSH Brute-Force Attack
2019-11-27 08:48:02

Recently Reported IPs

134.119.45.87 134.119.58.12 134.119.62.95 134.119.5.216
134.119.65.230 134.122.101.16 134.122.104.55 134.122.105.223
134.119.73.74 134.122.112.125 134.119.86.103 134.119.86.135
134.119.86.145 134.119.86.136 134.119.86.62 134.119.86.98
134.122.115.234 134.122.124.35 134.122.137.163 134.122.25.14