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

;; QUESTION SECTION:
;16.159.53.44.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 17:43:11 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 44.53.159.16.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 44.53.159.16.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
54.38.190.48 attack
Apr  4 09:10:51 [HOSTNAME] sshd[24075]: User **removed** from 54.38.190.48 not allowed because not listed in AllowUsers
Apr  4 09:10:51 [HOSTNAME] sshd[24075]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.190.48  user=**removed**
Apr  4 09:10:52 [HOSTNAME] sshd[24075]: Failed password for invalid user **removed** from 54.38.190.48 port 49946 ssh2
...
2020-04-04 21:36:55
212.95.137.164 attackbotsspam
Invalid user kuv from 212.95.137.164 port 41068
2020-04-04 21:28:06
180.168.141.246 attackbots
Apr  4 15:39:47 lock-38 sshd[553890]: Failed password for root from 180.168.141.246 port 51514 ssh2
Apr  4 15:41:13 lock-38 sshd[553948]: Failed password for root from 180.168.141.246 port 41960 ssh2
Apr  4 15:42:19 lock-38 sshd[553984]: Failed password for root from 180.168.141.246 port 56734 ssh2
Apr  4 15:43:17 lock-38 sshd[554017]: Failed password for root from 180.168.141.246 port 43276 ssh2
Apr  4 15:44:19 lock-38 sshd[554040]: Failed password for root from 180.168.141.246 port 58050 ssh2
...
2020-04-04 22:09:32
141.98.80.95 attack
20 attempts against mh-misbehave-ban on creek
2020-04-04 22:25:39
203.172.66.227 attackspambots
Apr  4 15:53:46 OPSO sshd\[545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.172.66.227  user=root
Apr  4 15:53:49 OPSO sshd\[545\]: Failed password for root from 203.172.66.227 port 43304 ssh2
Apr  4 15:57:08 OPSO sshd\[1229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.172.66.227  user=root
Apr  4 15:57:09 OPSO sshd\[1229\]: Failed password for root from 203.172.66.227 port 36054 ssh2
Apr  4 16:00:20 OPSO sshd\[1680\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.172.66.227  user=root
2020-04-04 22:24:58
78.134.90.84 attackbots
Apr  4 15:14:31 vpn01 sshd[11692]: Failed password for root from 78.134.90.84 port 47432 ssh2
...
2020-04-04 22:07:38
23.108.50.55 attack
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across brinkchiro.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www.talkwi
2020-04-04 21:30:40
122.51.221.184 attack
Apr  4 07:13:39 ny01 sshd[5942]: Failed password for root from 122.51.221.184 port 57390 ssh2
Apr  4 07:19:48 ny01 sshd[6578]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.221.184
Apr  4 07:19:50 ny01 sshd[6578]: Failed password for invalid user web from 122.51.221.184 port 36292 ssh2
2020-04-04 21:26:25
46.185.214.92 attackspam
Unauthorized connection attempt detected from IP address 46.185.214.92 to port 445
2020-04-04 21:22:49
34.92.182.252 attackbotsspam
Apr  4 10:38:19 xxx sshd[28565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.bc.googleusercontent.com  user=r.r
Apr  4 10:38:19 xxx sshd[28565]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.bc.googleusercontent.com  user=r.r
Apr  4 10:48:14 xxx sshd[29422]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.bc.googleusercontent.com  user=r.r
Apr  4 10:48:14 xxx sshd[29422]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.bc.googleusercontent.com  user=r.r
Apr  4 10:52:09 xxx sshd[29664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.bc.googleusercontent.com  user=r.r
Apr  4 10:52:09 xxx sshd[29664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=252.182.92.34.........
------------------------------
2020-04-04 21:46:07
213.32.71.196 attackbots
Apr  4 05:11:56 pixelmemory sshd[23372]: Failed password for root from 213.32.71.196 port 39196 ssh2
Apr  4 05:15:19 pixelmemory sshd[25411]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.71.196
Apr  4 05:15:21 pixelmemory sshd[25411]: Failed password for invalid user meitao from 213.32.71.196 port 48034 ssh2
...
2020-04-04 21:37:50
61.177.172.128 attackbots
2020-04-04T13:41:45.052831abusebot-2.cloudsearch.cf sshd[5090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
2020-04-04T13:41:47.309162abusebot-2.cloudsearch.cf sshd[5090]: Failed password for root from 61.177.172.128 port 57343 ssh2
2020-04-04T13:41:51.658960abusebot-2.cloudsearch.cf sshd[5090]: Failed password for root from 61.177.172.128 port 57343 ssh2
2020-04-04T13:41:45.052831abusebot-2.cloudsearch.cf sshd[5090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
2020-04-04T13:41:47.309162abusebot-2.cloudsearch.cf sshd[5090]: Failed password for root from 61.177.172.128 port 57343 ssh2
2020-04-04T13:41:51.658960abusebot-2.cloudsearch.cf sshd[5090]: Failed password for root from 61.177.172.128 port 57343 ssh2
2020-04-04T13:41:45.052831abusebot-2.cloudsearch.cf sshd[5090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser
...
2020-04-04 21:44:52
106.13.147.89 attackbotsspam
Apr  4 15:19:44 ovpn sshd\[19755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.147.89  user=root
Apr  4 15:19:46 ovpn sshd\[19755\]: Failed password for root from 106.13.147.89 port 49398 ssh2
Apr  4 15:33:15 ovpn sshd\[22841\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.147.89  user=root
Apr  4 15:33:17 ovpn sshd\[22841\]: Failed password for root from 106.13.147.89 port 46402 ssh2
Apr  4 15:41:44 ovpn sshd\[24734\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.147.89  user=root
2020-04-04 21:59:30
207.154.193.178 attackspambots
Apr  4 15:32:48 host01 sshd[5144]: Failed password for root from 207.154.193.178 port 47352 ssh2
Apr  4 15:37:17 host01 sshd[5966]: Failed password for root from 207.154.193.178 port 59058 ssh2
...
2020-04-04 22:02:47
185.164.138.21 attack
Automatic report - SSH Brute-Force Attack
2020-04-04 22:20:39

Recently Reported IPs

152.143.145.116 220.175.82.122 217.245.121.44 120.30.93.180
100.160.207.194 1.253.80.73 14.83.102.98 222.185.210.181
80.218.182.54 120.86.202.114 118.7.16.191 139.43.76.119
238.127.168.241 157.112.68.164 218.247.85.195 115.149.82.54
231.91.30.90 125.152.251.34 134.51.84.165 20.73.61.101