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

;; QUESTION SECTION:
;13.244.141.164.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 06:28:50 CST 2022
;; MSG SIZE  rcvd: 107
Host info
164.141.244.13.in-addr.arpa domain name pointer ec2-13-244-141-164.af-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
164.141.244.13.in-addr.arpa	name = ec2-13-244-141-164.af-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.213.43.164 attack
Dec  5 11:53:09 itv-usvr-01 sshd[6137]: Invalid user Pekka from 129.213.43.164
Dec  5 11:53:09 itv-usvr-01 sshd[6137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.43.164
Dec  5 11:53:09 itv-usvr-01 sshd[6137]: Invalid user Pekka from 129.213.43.164
Dec  5 11:53:11 itv-usvr-01 sshd[6137]: Failed password for invalid user Pekka from 129.213.43.164 port 40870 ssh2
Dec  5 12:00:01 itv-usvr-01 sshd[6354]: Invalid user schwedhelm from 129.213.43.164
2019-12-05 13:11:25
196.27.127.61 attack
Dec  4 22:25:13 rotator sshd\[9678\]: Address 196.27.127.61 maps to 300080-host.customer.zol.co.zw, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Dec  4 22:25:13 rotator sshd\[9678\]: Invalid user defense from 196.27.127.61Dec  4 22:25:15 rotator sshd\[9678\]: Failed password for invalid user defense from 196.27.127.61 port 49936 ssh2Dec  4 22:32:56 rotator sshd\[10898\]: Address 196.27.127.61 maps to 300080-host.customer.zol.co.zw, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Dec  4 22:32:56 rotator sshd\[10898\]: Invalid user tallis from 196.27.127.61Dec  4 22:32:58 rotator sshd\[10898\]: Failed password for invalid user tallis from 196.27.127.61 port 50812 ssh2
...
2019-12-05 08:46:32
190.128.230.98 attack
2019-12-05T00:41:25.200939abusebot-3.cloudsearch.cf sshd\[20081\]: Invalid user guest555 from 190.128.230.98 port 42921
2019-12-05 08:48:17
202.169.62.187 attack
Dec  5 05:49:33 eventyay sshd[18954]: Failed password for root from 202.169.62.187 port 48556 ssh2
Dec  5 05:57:23 eventyay sshd[19186]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.169.62.187
Dec  5 05:57:25 eventyay sshd[19186]: Failed password for invalid user login from 202.169.62.187 port 54221 ssh2
...
2019-12-05 13:14:33
51.83.42.138 attackspam
Dec  4 22:37:11 heissa sshd\[1324\]: Invalid user odoo9 from 51.83.42.138 port 53704
Dec  4 22:37:11 heissa sshd\[1324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.ip-51-83-42.eu
Dec  4 22:37:13 heissa sshd\[1324\]: Failed password for invalid user odoo9 from 51.83.42.138 port 53704 ssh2
Dec  4 22:44:55 heissa sshd\[2735\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.ip-51-83-42.eu  user=mysql
Dec  4 22:44:57 heissa sshd\[2735\]: Failed password for mysql from 51.83.42.138 port 48276 ssh2
2019-12-05 08:50:07
106.75.7.171 attackspambots
Dec  4 15:35:58 TORMINT sshd\[28736\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.7.171  user=root
Dec  4 15:36:00 TORMINT sshd\[28736\]: Failed password for root from 106.75.7.171 port 34550 ssh2
Dec  4 15:42:12 TORMINT sshd\[29268\]: Invalid user admin from 106.75.7.171
Dec  4 15:42:12 TORMINT sshd\[29268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.7.171
...
2019-12-05 08:35:06
200.34.88.37 attackspambots
Dec  4 18:51:35 kapalua sshd\[11650\]: Invalid user blake from 200.34.88.37
Dec  4 18:51:35 kapalua sshd\[11650\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.34.88.37
Dec  4 18:51:37 kapalua sshd\[11650\]: Failed password for invalid user blake from 200.34.88.37 port 47790 ssh2
Dec  4 18:57:42 kapalua sshd\[12330\]: Invalid user couscous from 200.34.88.37
Dec  4 18:57:42 kapalua sshd\[12330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.34.88.37
2019-12-05 13:01:24
106.13.56.72 attackspam
Dec  4 23:50:01 srv206 sshd[25355]: Invalid user vps2015 from 106.13.56.72
...
2019-12-05 08:45:40
196.43.196.108 attack
Dec  4 14:00:58 php1 sshd\[1845\]: Invalid user ofsaa123 from 196.43.196.108
Dec  4 14:00:58 php1 sshd\[1845\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.43.196.108
Dec  4 14:01:00 php1 sshd\[1845\]: Failed password for invalid user ofsaa123 from 196.43.196.108 port 44784 ssh2
Dec  4 14:07:41 php1 sshd\[2500\]: Invalid user \*\*\*\*\*\*\* from 196.43.196.108
Dec  4 14:07:41 php1 sshd\[2500\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.43.196.108
2019-12-05 08:38:29
113.88.167.48 attackbotsspam
Unauthorised access (Dec  4) SRC=113.88.167.48 LEN=52 TTL=50 ID=13844 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-05 08:49:20
182.23.104.231 attackbotsspam
Dec  5 05:57:30 vpn01 sshd[10802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.23.104.231
Dec  5 05:57:31 vpn01 sshd[10802]: Failed password for invalid user guest from 182.23.104.231 port 44228 ssh2
...
2019-12-05 13:10:06
204.93.165.115 attackbotsspam
2019-12-05T04:57:37.176981abusebot-6.cloudsearch.cf sshd\[25230\]: Invalid user wckao from 204.93.165.115 port 51436
2019-12-05 13:06:59
148.70.18.221 attack
Dec  4 20:16:17 MainVPS sshd[3350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.18.221  user=mysql
Dec  4 20:16:19 MainVPS sshd[3350]: Failed password for mysql from 148.70.18.221 port 53866 ssh2
Dec  4 20:22:46 MainVPS sshd[14838]: Invalid user test from 148.70.18.221 port 60384
Dec  4 20:22:47 MainVPS sshd[14838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.18.221
Dec  4 20:22:46 MainVPS sshd[14838]: Invalid user test from 148.70.18.221 port 60384
Dec  4 20:22:48 MainVPS sshd[14838]: Failed password for invalid user test from 148.70.18.221 port 60384 ssh2
...
2019-12-05 08:45:17
77.42.77.135 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-12-05 08:43:23
61.183.178.194 attackbots
Dec  5 10:18:13 vibhu-HP-Z238-Microtower-Workstation sshd\[11995\]: Invalid user tar from 61.183.178.194
Dec  5 10:18:13 vibhu-HP-Z238-Microtower-Workstation sshd\[11995\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194
Dec  5 10:18:15 vibhu-HP-Z238-Microtower-Workstation sshd\[11995\]: Failed password for invalid user tar from 61.183.178.194 port 8921 ssh2
Dec  5 10:27:40 vibhu-HP-Z238-Microtower-Workstation sshd\[12501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.183.178.194  user=root
Dec  5 10:27:42 vibhu-HP-Z238-Microtower-Workstation sshd\[12501\]: Failed password for root from 61.183.178.194 port 8922 ssh2
...
2019-12-05 13:00:39

Recently Reported IPs

13.239.0.31 13.244.169.18 13.244.99.41 13.246.35.115
13.246.0.137 13.248.132.76 13.248.141.25 13.248.136.15
13.248.141.89 13.248.155.14 13.248.155.183 13.248.155.91
13.248.155.34 13.248.159.25 13.248.159.201 13.248.161.93
13.248.162.114 13.248.162.186 13.248.164.50 13.248.163.94