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

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

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

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

;; Query time: 112 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 18 15:59:56 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 40.50.145.53.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 40.50.145.53.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
184.66.225.102 attackbots
2019-11-25T18:42:32.178929abusebot.cloudsearch.cf sshd\[17119\]: Failed password for invalid user siegel from 184.66.225.102 port 51076 ssh2
2019-11-26 02:44:34
148.70.99.154 attackspam
Invalid user g04w4y from 148.70.99.154 port 60105
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.99.154
Failed password for invalid user g04w4y from 148.70.99.154 port 60105 ssh2
Invalid user guarnera from 148.70.99.154 port 50156
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.99.154
2019-11-26 02:47:53
118.126.105.120 attackspambots
Nov 25 11:22:37 server sshd\[10107\]: Failed password for invalid user smmsp from 118.126.105.120 port 39792 ssh2
Nov 25 17:25:22 server sshd\[7828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.105.120  user=root
Nov 25 17:25:24 server sshd\[7828\]: Failed password for root from 118.126.105.120 port 59686 ssh2
Nov 25 17:34:35 server sshd\[9867\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.105.120  user=root
Nov 25 17:34:37 server sshd\[9867\]: Failed password for root from 118.126.105.120 port 43718 ssh2
...
2019-11-26 03:09:58
89.221.205.18 attackspambots
Port scan on 1 port(s): 139
2019-11-26 02:51:38
188.247.73.225 attackbots
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-26 02:54:32
78.128.113.130 attackbots
Nov 25 19:28:06 dedicated sshd[24712]: Invalid user admin from 78.128.113.130 port 51200
2019-11-26 02:59:35
162.144.200.40 attackbotsspam
fail2ban honeypot
2019-11-26 02:59:56
46.38.144.57 attackspambots
Nov 25 20:04:21 vmanager6029 postfix/smtpd\[28229\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 25 20:05:09 vmanager6029 postfix/smtpd\[28229\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-26 03:11:28
222.186.175.150 attack
2019-11-25T18:53:41.018962hub.schaetter.us sshd\[14516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.150  user=root
2019-11-25T18:53:42.994393hub.schaetter.us sshd\[14516\]: Failed password for root from 222.186.175.150 port 7914 ssh2
2019-11-25T18:53:46.716989hub.schaetter.us sshd\[14516\]: Failed password for root from 222.186.175.150 port 7914 ssh2
2019-11-25T18:53:49.518431hub.schaetter.us sshd\[14516\]: Failed password for root from 222.186.175.150 port 7914 ssh2
2019-11-25T18:53:52.739980hub.schaetter.us sshd\[14516\]: Failed password for root from 222.186.175.150 port 7914 ssh2
...
2019-11-26 02:56:59
49.88.112.54 attack
Nov2519:55:35server2sshd[16665]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2519:55:36server2sshd[16666]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2519:55:36server2sshd[16667]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2519:55:36server2sshd[16668]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2520:17:48server2sshd[22268]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2520:17:48server2sshd[22269]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2520:17:48server2sshd[22270]:refusedconnectfrom49.88.112.54\(49.88.112.54\)Nov2520:17:48server2sshd[22271]:refusedconnectfrom49.88.112.54\(49.88.112.54\)
2019-11-26 03:18:29
78.97.94.94 attackbots
Web Probe / Attack
2019-11-26 03:07:21
77.211.163.162 attackspam
Automatic report - Port Scan Attack
2019-11-26 03:10:56
221.228.130.152 attackbotsspam
Nov 25 15:34:28 host proftpd[34129]: 0.0.0.0 (221.228.130.152[221.228.130.152]) - USER anonymous: no such user found from 221.228.130.152 [221.228.130.152] to 62.210.146.38:21
...
2019-11-26 03:17:20
182.76.206.194 attack
$f2bV_matches
2019-11-26 03:15:32
186.67.248.8 attack
Nov 25 12:22:25 Tower sshd[33536]: Connection from 186.67.248.8 port 53409 on 192.168.10.220 port 22
Nov 25 12:22:26 Tower sshd[33536]: Invalid user kateland from 186.67.248.8 port 53409
Nov 25 12:22:26 Tower sshd[33536]: error: Could not get shadow information for NOUSER
Nov 25 12:22:26 Tower sshd[33536]: Failed password for invalid user kateland from 186.67.248.8 port 53409 ssh2
Nov 25 12:22:26 Tower sshd[33536]: Received disconnect from 186.67.248.8 port 53409:11: Bye Bye [preauth]
Nov 25 12:22:26 Tower sshd[33536]: Disconnected from invalid user kateland 186.67.248.8 port 53409 [preauth]
2019-11-26 02:54:58

Recently Reported IPs

187.5.184.178 186.79.184.13 183.80.197.35 181.49.0.178
177.97.132.149 151.70.191.242 146.120.86.101 125.227.9.108
123.8.252.69 116.48.57.61 113.245.41.186 113.102.142.167
111.229.110.107 94.60.81.210 91.216.66.68 88.247.132.197
84.241.41.40 76.167.233.54 69.29.8.49 68.205.106.84