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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;146.13.120.140.			IN	A

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

;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Aug 21 08:51:45 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 140.120.13.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 140.120.13.146.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
128.199.186.65 attackspambots
Jul 21 19:28:45 ms-srv sshd[12065]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.186.65
Jul 21 19:28:47 ms-srv sshd[12065]: Failed password for invalid user mysql from 128.199.186.65 port 33512 ssh2
2019-07-22 03:50:52
172.91.168.95 attackspambots
Jul 21 21:43:00 yabzik sshd[21077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.91.168.95
Jul 21 21:43:02 yabzik sshd[21077]: Failed password for invalid user tftp from 172.91.168.95 port 46810 ssh2
Jul 21 21:47:46 yabzik sshd[22578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.91.168.95
2019-07-22 03:15:44
191.97.54.35 attackspam
Autoban   191.97.54.35 AUTH/CONNECT
2019-07-22 03:21:13
191.53.58.100 attack
Autoban   191.53.58.100 AUTH/CONNECT
2019-07-22 03:37:31
59.153.232.226 attackspam
Sun, 21 Jul 2019 18:29:01 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:13:13
192.145.122.39 attackspam
Autoban   192.145.122.39 AUTH/CONNECT
2019-07-22 03:11:23
196.74.143.178 attackspambots
Sun, 21 Jul 2019 18:28:48 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:52:22
191.53.251.84 attack
Autoban   191.53.251.84 AUTH/CONNECT
2019-07-22 03:45:53
203.81.91.85 attackbots
Sun, 21 Jul 2019 18:28:55 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:31:41
191.92.212.251 attackspam
Autoban   191.92.212.251 AUTH/CONNECT
2019-07-22 03:22:09
191.6.16.238 attackspambots
Autoban   191.6.16.238 AUTH/CONNECT
2019-07-22 03:32:30
93.177.131.150 attackspam
Sun, 21 Jul 2019 18:28:51 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:45:05
43.250.80.220 attack
Sun, 21 Jul 2019 18:28:49 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:52:03
91.231.40.134 attackbotsspam
Sun, 21 Jul 2019 18:28:49 +0000 likely compromised host or open proxy. ddos rate spidering
2019-07-22 03:51:10
191.53.253.184 attack
Autoban   191.53.253.184 AUTH/CONNECT
2019-07-22 03:45:27

Recently Reported IPs

160.152.243.66 99.231.112.23 123.75.218.89 187.17.142.117
79.74.212.171 151.14.110.163 179.25.212.207 187.36.231.42
118.38.89.127 124.200.85.40 83.85.198.50 121.13.229.99
142.180.20.105 49.251.65.201 44.225.23.66 68.192.249.55
173.70.10.89 107.79.47.82 45.103.2.145 47.137.156.65