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

Region: Gauteng

Country: South Africa

Internet Service Provider: Telkom

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

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

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 05:24:02 CST 2020
;; MSG SIZE  rcvd: 118
Host info
81.162.144.165.in-addr.arpa domain name pointer 8ta-165-144-162-81.telkomadsl.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
81.162.144.165.in-addr.arpa	name = 8ta-165-144-162-81.telkomadsl.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.133.114.19 attack
103.133.114.19 - - [15/Apr/2020:14:12:44 +0200] "GET /wp-login.php HTTP/1.1" 200 6463 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
103.133.114.19 - - [15/Apr/2020:14:12:45 +0200] "POST /wp-login.php HTTP/1.1" 200 7362 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
103.133.114.19 - - [15/Apr/2020:14:12:47 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-04-15 21:02:51
104.14.29.2 attackspam
Apr 15 12:03:03 localhost sshd[38659]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104-14-29-2.lightspeed.austtx.sbcglobal.net  user=root
Apr 15 12:03:05 localhost sshd[38659]: Failed password for root from 104.14.29.2 port 41775 ssh2
Apr 15 12:07:48 localhost sshd[39283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104-14-29-2.lightspeed.austtx.sbcglobal.net  user=root
Apr 15 12:07:50 localhost sshd[39283]: Failed password for root from 104.14.29.2 port 36827 ssh2
Apr 15 12:12:20 localhost sshd[39839]: Invalid user adidas from 104.14.29.2 port 60110
...
2020-04-15 21:26:15
37.187.12.126 attackbotsspam
SSH brute-force: detected 11 distinct usernames within a 24-hour window.
2020-04-15 21:29:09
1.214.215.236 attackspam
leo_www
2020-04-15 21:10:44
173.252.183.120 attackspam
Apr 15 12:41:12  sshd[23094]: Connection closed by 173.252.183.120 [preauth]
2020-04-15 20:53:09
89.248.167.131 attack
TCP Port Scanning
2020-04-15 21:30:47
2.144.247.229 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-04-15 21:12:58
36.67.42.121 attack
port scan and connect, tcp 80 (http)
2020-04-15 21:12:02
114.24.133.116 attack
Apr 15 12:12:50 localhost sshd[39909]: Invalid user pi from 114.24.133.116 port 45412
Apr 15 12:12:50 localhost sshd[39910]: Invalid user pi from 114.24.133.116 port 45418
Apr 15 12:12:50 localhost sshd[39909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114-24-133-116.dynamic-ip.hinet.net
Apr 15 12:12:50 localhost sshd[39909]: Invalid user pi from 114.24.133.116 port 45412
Apr 15 12:12:53 localhost sshd[39909]: Failed password for invalid user pi from 114.24.133.116 port 45412 ssh2
...
2020-04-15 20:56:51
54.37.149.233 attackbots
Apr 15 16:15:07 pkdns2 sshd\[38459\]: Address 54.37.149.233 maps to ip-54-37-149.eu, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr 15 16:15:09 pkdns2 sshd\[38459\]: Failed password for root from 54.37.149.233 port 34312 ssh2Apr 15 16:18:49 pkdns2 sshd\[38582\]: Address 54.37.149.233 maps to ip-54-37-149.eu, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr 15 16:18:49 pkdns2 sshd\[38582\]: Invalid user mqm from 54.37.149.233Apr 15 16:18:51 pkdns2 sshd\[38582\]: Failed password for invalid user mqm from 54.37.149.233 port 43334 ssh2Apr 15 16:22:36 pkdns2 sshd\[38756\]: Address 54.37.149.233 maps to ip-54-37-149.eu, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr 15 16:22:36 pkdns2 sshd\[38756\]: Invalid user git from 54.37.149.233
...
2020-04-15 21:27:23
120.28.167.33 attack
Apr 15 17:39:13 gw1 sshd[359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.28.167.33
Apr 15 17:39:15 gw1 sshd[359]: Failed password for invalid user soporte from 120.28.167.33 port 38510 ssh2
...
2020-04-15 21:14:16
189.8.108.161 attackbots
Apr 15 14:03:56 vserver sshd\[17324\]: Failed password for proxy from 189.8.108.161 port 50490 ssh2Apr 15 14:08:32 vserver sshd\[17354\]: Invalid user admin from 189.8.108.161Apr 15 14:08:33 vserver sshd\[17354\]: Failed password for invalid user admin from 189.8.108.161 port 59162 ssh2Apr 15 14:12:57 vserver sshd\[17438\]: Invalid user operator from 189.8.108.161
...
2020-04-15 20:54:41
45.125.65.35 attackspambots
Apr 15 14:41:55 srv01 postfix/smtpd\[19117\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 15 14:43:07 srv01 postfix/smtpd\[19115\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 15 14:43:28 srv01 postfix/smtpd\[19117\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 15 14:43:35 srv01 postfix/smtpd\[19117\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr 15 14:52:03 srv01 postfix/smtpd\[19115\]: warning: unknown\[45.125.65.35\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-04-15 20:59:13
192.3.177.213 attack
'Fail2Ban'
2020-04-15 21:18:02
31.129.234.81 attack
20/4/15@08:12:40: FAIL: Alarm-Network address from=31.129.234.81
20/4/15@08:12:41: FAIL: Alarm-Network address from=31.129.234.81
...
2020-04-15 21:06:38

Recently Reported IPs

94.16.134.11 38.98.57.179 93.203.246.183 166.195.104.114
110.196.169.107 136.0.5.32 149.129.214.186 27.39.17.32
86.234.171.34 71.74.152.236 218.166.155.115 74.209.115.104
45.7.80.204 86.171.24.2 255.134.74.64 187.214.171.120
84.154.38.19 88.96.87.80 70.27.54.232 175.77.18.66