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

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

;; QUESTION SECTION:
;45.57.168.141.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 02:19:00 CST 2022
;; MSG SIZE  rcvd: 106
Host info
141.168.57.45.in-addr.arpa domain name pointer siesta.keencupid.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
141.168.57.45.in-addr.arpa	name = siesta.keencupid.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.71.6.221 attackbots
Dec 23 14:43:04 ns41 sshd[16997]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.6.221
2019-12-23 22:58:51
202.195.225.40 attackspam
Dec 23 17:59:54 hosting sshd[5855]: Invalid user oconnor from 202.195.225.40 port 7776
...
2019-12-23 23:19:28
35.240.253.241 attackbotsspam
Dec 23 15:53:59 meumeu sshd[23481]: Failed password for root from 35.240.253.241 port 38528 ssh2
Dec 23 15:59:54 meumeu sshd[24343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.240.253.241 
Dec 23 15:59:56 meumeu sshd[24343]: Failed password for invalid user operator from 35.240.253.241 port 41852 ssh2
...
2019-12-23 23:14:49
185.164.63.234 attackbots
Dec 23 14:10:53 XXXXXX sshd[61315]: Invalid user elmyra from 185.164.63.234 port 59058
2019-12-23 23:08:22
13.211.222.132 attack
Apr 19 22:43:12 yesfletchmain sshd\[13589\]: Invalid user h from 13.211.222.132 port 53502
Apr 19 22:43:12 yesfletchmain sshd\[13589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.211.222.132
Apr 19 22:43:13 yesfletchmain sshd\[13589\]: Failed password for invalid user h from 13.211.222.132 port 53502 ssh2
Apr 19 22:46:26 yesfletchmain sshd\[13700\]: Invalid user jira from 13.211.222.132 port 52458
Apr 19 22:46:26 yesfletchmain sshd\[13700\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.211.222.132
...
2019-12-23 23:27:39
13.64.93.10 attackspam
Mar 12 02:17:26 yesfletchmain sshd\[21548\]: Invalid user couchdb from 13.64.93.10 port 39872
Mar 12 02:17:26 yesfletchmain sshd\[21548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.64.93.10
Mar 12 02:17:28 yesfletchmain sshd\[21548\]: Failed password for invalid user couchdb from 13.64.93.10 port 39872 ssh2
Mar 12 02:22:31 yesfletchmain sshd\[21657\]: Invalid user victor from 13.64.93.10 port 39872
Mar 12 02:22:31 yesfletchmain sshd\[21657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.64.93.10
...
2019-12-23 23:10:50
54.38.81.106 attack
2019-12-23T14:51:48.574989Z adf97b4d956e New connection: 54.38.81.106:40114 (172.17.0.5:2222) [session: adf97b4d956e]
2019-12-23T14:59:45.303380Z ee719632c4e8 New connection: 54.38.81.106:46572 (172.17.0.5:2222) [session: ee719632c4e8]
2019-12-23 23:33:34
67.205.153.16 attackbots
Dec 23 14:35:17 XXXXXX sshd[61522]: Invalid user jumani from 67.205.153.16 port 36140
2019-12-23 23:10:10
51.68.174.177 attackspam
Dec 23 15:59:58 vpn01 sshd[18083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.174.177
Dec 23 16:00:00 vpn01 sshd[18083]: Failed password for invalid user & from 51.68.174.177 port 36114 ssh2
...
2019-12-23 23:05:42
46.101.249.232 attackbots
$f2bV_matches_ltvn
2019-12-23 23:14:30
123.24.220.92 attack
Unauthorized connection attempt from IP address 123.24.220.92 on Port 445(SMB)
2019-12-23 23:32:47
94.191.105.218 attackbots
firewall-block, port(s): 6379/tcp
2019-12-23 23:01:28
62.234.122.141 attackspam
Invalid user fullcontact from 62.234.122.141 port 36023
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.122.141
Failed password for invalid user fullcontact from 62.234.122.141 port 36023 ssh2
Invalid user ftpuser from 62.234.122.141 port 60628
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.122.141
2019-12-23 23:05:10
13.234.180.121 attackspam
Dec 12 02:53:47 yesfletchmain sshd\[22582\]: Invalid user test from 13.234.180.121 port 42012
Dec 12 02:53:47 yesfletchmain sshd\[22582\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.234.180.121
Dec 12 02:53:49 yesfletchmain sshd\[22582\]: Failed password for invalid user test from 13.234.180.121 port 42012 ssh2
Dec 12 03:00:30 yesfletchmain sshd\[22755\]: Invalid user eastwood from 13.234.180.121 port 61447
Dec 12 03:00:30 yesfletchmain sshd\[22755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.234.180.121
...
2019-12-23 23:23:12
45.136.108.160 attackspam
Dec 23 15:59:54 debian-2gb-nbg1-2 kernel: \[765939.945595\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.136.108.160 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=25261 PROTO=TCP SPT=57559 DPT=7934 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-23 23:16:44

Recently Reported IPs

31.12.95.144 45.15.129.144 128.90.202.54 49.238.172.90
193.123.254.68 20.24.66.60 37.35.42.113 149.18.57.33
95.164.234.156 203.204.200.103 203.150.113.28 95.164.233.172
113.88.127.151 128.90.158.137 128.90.122.5 151.68.17.59
125.74.215.140 117.83.16.135 85.208.86.52 95.181.150.77