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

;; QUESTION SECTION:
;129.205.143.163.		IN	A

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

;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 04:46:42 CST 2022
;; MSG SIZE  rcvd: 108
Host info
163.143.205.129.in-addr.arpa domain name pointer 129-205-143-163.dynamic.macrolan.co.za.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
163.143.205.129.in-addr.arpa	name = 129-205-143-163.dynamic.macrolan.co.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.84.109.210 attackspam
11/24/2019-09:47:10.237947 103.84.109.210 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-25 04:34:24
206.189.136.160 attackbotsspam
Nov 24 21:15:57 ns381471 sshd[26512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.136.160
Nov 24 21:15:58 ns381471 sshd[26512]: Failed password for invalid user carlos from 206.189.136.160 port 59888 ssh2
2019-11-25 04:27:18
54.37.154.113 attackbotsspam
Nov 24 20:01:21 nextcloud sshd\[16283\]: Invalid user admin from 54.37.154.113
Nov 24 20:01:21 nextcloud sshd\[16283\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.154.113
Nov 24 20:01:23 nextcloud sshd\[16283\]: Failed password for invalid user admin from 54.37.154.113 port 40136 ssh2
...
2019-11-25 04:26:56
103.245.181.2 attack
2019-11-24T19:46:58.375965abusebot-2.cloudsearch.cf sshd\[19126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.245.181.2  user=root
2019-11-25 04:31:15
106.0.6.236 attackspambots
11/24/2019-09:47:21.604240 106.0.6.236 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-25 04:26:00
5.39.77.117 attackbotsspam
Nov 10 04:32:15 vtv3 sshd[15835]: Failed password for invalid user live!@# from 5.39.77.117 port 33965 ssh2
Nov 10 04:36:10 vtv3 sshd[18568]: Invalid user Pa$$w0rd444 from 5.39.77.117 port 52869
Nov 10 04:36:10 vtv3 sshd[18568]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.117
Nov 10 04:47:54 vtv3 sshd[25825]: Invalid user centos@123 from 5.39.77.117 port 52943
Nov 10 04:47:54 vtv3 sshd[25825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.117
Nov 10 04:47:56 vtv3 sshd[25825]: Failed password for invalid user centos@123 from 5.39.77.117 port 52943 ssh2
Nov 10 04:51:51 vtv3 sshd[28348]: Invalid user admina373045462 from 5.39.77.117 port 43556
Nov 10 04:51:51 vtv3 sshd[28348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.117
Nov 10 05:03:31 vtv3 sshd[3151]: Invalid user gernst from 5.39.77.117 port 43690
Nov 10 05:03:31 vtv3 sshd[3151]: pam_unix(sshd:auth): auth
2019-11-25 04:52:33
94.177.214.200 attack
Nov 24 19:09:49 hosting sshd[10991]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.214.200  user=root
Nov 24 19:09:51 hosting sshd[10991]: Failed password for root from 94.177.214.200 port 55492 ssh2
...
2019-11-25 05:04:09
45.55.53.198 attackbots
Port 22 Scan, PTR: None
2019-11-25 04:25:49
112.161.203.170 attackbots
Automatic report - Banned IP Access
2019-11-25 04:45:57
201.24.185.199 attack
2019-11-24T09:36:21.923483ns547587 sshd\[607\]: Invalid user kt from 201.24.185.199 port 54306
2019-11-24T09:36:21.928220ns547587 sshd\[607\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.24.185.199
2019-11-24T09:36:24.181823ns547587 sshd\[607\]: Failed password for invalid user kt from 201.24.185.199 port 54306 ssh2
2019-11-24T09:46:08.716271ns547587 sshd\[4598\]: Invalid user neon from 201.24.185.199 port 44211
2019-11-24T09:46:08.722011ns547587 sshd\[4598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.24.185.199
...
2019-11-25 04:57:17
144.217.89.55 attack
Unauthorized SSH login attempts
2019-11-25 04:56:30
196.201.39.150 attack
Scanning random ports - tries to find possible vulnerable services
2019-11-25 05:02:43
99.244.195.58 attackspambots
$f2bV_matches
2019-11-25 04:49:37
93.33.206.188 attackbots
SSH Brute-Force attacks
2019-11-25 05:05:28
222.169.185.234 attackspam
Nov 24 06:57:07 web1 sshd\[8952\]: Invalid user gadsby from 222.169.185.234
Nov 24 06:57:07 web1 sshd\[8952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234
Nov 24 06:57:10 web1 sshd\[8952\]: Failed password for invalid user gadsby from 222.169.185.234 port 39546 ssh2
Nov 24 07:01:33 web1 sshd\[9350\]: Invalid user steinum from 222.169.185.234
Nov 24 07:01:33 web1 sshd\[9350\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234
2019-11-25 04:31:49

Recently Reported IPs

129.205.143.159 118.170.148.217 129.205.143.160 129.205.143.164
129.205.143.180 129.205.143.168 129.205.143.167 118.170.15.222
129.205.143.184 129.205.143.196 129.205.143.189 129.205.143.204
129.205.143.198 129.205.143.211 129.205.143.2 129.205.143.19
129.205.143.206 129.205.143.213 129.205.143.216 129.205.143.22