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:
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 <<>> 146.122.1.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3172
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;146.122.1.50.			IN	A

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

;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 07 08:42:18 CST 2023
;; MSG SIZE  rcvd: 105
Host info
Host 50.1.122.146.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 50.1.122.146.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.76.183.99 attack
Feb  1 22:59:49 ns381471 sshd[24302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.183.99
Feb  1 22:59:50 ns381471 sshd[24302]: Failed password for invalid user git_user from 180.76.183.99 port 34928 ssh2
2020-02-02 06:10:59
170.82.150.108 attackbotsspam
Feb  2 00:59:48 server sshd\[16512\]: Invalid user pi from 170.82.150.108
Feb  2 00:59:48 server sshd\[16511\]: Invalid user pi from 170.82.150.108
Feb  2 00:59:48 server sshd\[16512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.82.150.108 
Feb  2 00:59:48 server sshd\[16511\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.82.150.108 
Feb  2 00:59:50 server sshd\[16512\]: Failed password for invalid user pi from 170.82.150.108 port 52818 ssh2
...
2020-02-02 06:10:18
186.123.107.34 attack
Unauthorized connection attempt detected from IP address 186.123.107.34 to port 2220 [J]
2020-02-02 06:03:48
103.214.65.243 attack
$f2bV_matches
2020-02-02 06:06:00
140.143.183.71 attackspambots
Dec 14 10:33:22 v22018076590370373 sshd[27851]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.183.71 
...
2020-02-02 05:55:49
103.68.33.34 attack
2020-2-1 2:33:00 PM: failed ssh attempt
2020-02-02 05:43:10
140.143.230.161 attack
Unauthorized connection attempt detected from IP address 140.143.230.161 to port 2220 [J]
2020-02-02 05:41:31
140.143.193.52 attack
$f2bV_matches
2020-02-02 05:53:34
222.186.175.183 attackbots
Feb  1 23:09:44 MK-Soft-VM4 sshd[28099]: Failed password for root from 222.186.175.183 port 61324 ssh2
Feb  1 23:09:49 MK-Soft-VM4 sshd[28099]: Failed password for root from 222.186.175.183 port 61324 ssh2
Feb  1 23:09:53 MK-Soft-VM4 sshd[28099]: Failed password for root from 222.186.175.183 port 61324 ssh2
Feb  1 23:09:59 MK-Soft-VM4 sshd[28099]: Failed password for root from 222.186.175.183 port 61324 ssh2
Feb  1 23:10:04 MK-Soft-VM4 sshd[28099]: Failed password for root from 222.186.175.183 port 61324 ssh2
Feb  1 23:10:06 MK-Soft-VM4 sshd[28099]: error: maximum authentication attempts exceeded for root from 222.186.175.183 port 61324 ssh2 [preauth]
Feb  1 23:10:20 MK-Soft-VM4 sshd[28332]: Failed password for root from 222.186.175.183 port 15032 ssh2
Feb  1 23:10:28 MK-Soft-VM4 sshd[28332]: Failed password for root from 222.186.175.183 port 15032 ssh2
Feb  1 23:10:33 MK-Soft-VM4 sshd[28332]: Failed password for root from 222.186.175.183 port 15032 ssh2
Feb  1 23:10:35 MK-Soft-VM4 sshd[28332]: Failed passwor
2020-02-02 06:13:22
45.134.179.15 attackbots
02/01/2020-16:59:47.008194 45.134.179.15 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-02-02 06:13:45
140.143.207.57 attackbotsspam
Dec 14 10:18:12 v22018076590370373 sshd[27364]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.207.57 
...
2020-02-02 05:45:34
85.154.5.213 attackbotsspam
SMTP-sasl brute force
...
2020-02-02 06:09:39
151.213.6.241 attackbotsspam
Unauthorized connection attempt detected from IP address 151.213.6.241 to port 2220 [J]
2020-02-02 05:55:21
185.234.219.68 attack
Feb  1 22:40:39 srv01 postfix/smtpd\[11776\]: warning: unknown\[185.234.219.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  1 22:41:48 srv01 postfix/smtpd\[11776\]: warning: unknown\[185.234.219.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  1 22:41:54 srv01 postfix/smtpd\[11776\]: warning: unknown\[185.234.219.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  1 22:42:04 srv01 postfix/smtpd\[11776\]: warning: unknown\[185.234.219.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  1 22:59:49 srv01 postfix/smtpd\[20645\]: warning: unknown\[185.234.219.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-02-02 06:10:43
140.143.2.228 attackbots
Unauthorized connection attempt detected from IP address 140.143.2.228 to port 2220 [J]
2020-02-02 05:48:20

Recently Reported IPs

11.227.157.130 169.94.66.48 251.68.67.158 169.156.106.141
104.25.196.146 69.163.156.60 149.253.246.194 129.178.3.137
10.93.199.130 151.153.243.138 166.22.22.232 67.158.199.234
11.92.74.5 130.230.184.244 124.59.195.138 157.99.127.228
139.184.63.179 85.141.176.186 165.116.174.50 13.139.20.119