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: Korea (the Republic of)

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

;; QUESTION SECTION:
;14.84.140.129.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 25 05:22:10 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 129.140.84.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.140.84.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.54.242.239 attack
Mar  8 09:18:55 Tower sshd[27036]: Connection from 106.54.242.239 port 50292 on 192.168.10.220 port 22 rdomain ""
Mar  8 09:18:59 Tower sshd[27036]: Invalid user vagrant from 106.54.242.239 port 50292
Mar  8 09:18:59 Tower sshd[27036]: error: Could not get shadow information for NOUSER
Mar  8 09:18:59 Tower sshd[27036]: Failed password for invalid user vagrant from 106.54.242.239 port 50292 ssh2
Mar  8 09:18:59 Tower sshd[27036]: Received disconnect from 106.54.242.239 port 50292:11: Bye Bye [preauth]
Mar  8 09:18:59 Tower sshd[27036]: Disconnected from invalid user vagrant 106.54.242.239 port 50292 [preauth]
2020-03-08 21:48:35
187.134.43.16 attack
Mar  8 14:18:58  sshd\[18297\]: Invalid user seesbot from 187.134.43.16Mar  8 14:18:59  sshd\[18297\]: Failed password for invalid user seesbot from 187.134.43.16 port 34792 ssh2
...
2020-03-08 21:39:30
112.85.42.188 attackspambots
03/08/2020-09:25:25.817918 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan
2020-03-08 21:26:17
213.120.127.47 attackspam
Automatic report - Port Scan Attack
2020-03-08 21:40:32
217.165.204.150 attackspam
Dec 14 07:06:47 ms-srv sshd[10961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.165.204.150
Dec 14 07:06:48 ms-srv sshd[10961]: Failed password for invalid user admin from 217.165.204.150 port 59809 ssh2
2020-03-08 21:46:25
217.129.168.73 attack
Jan 19 02:10:32 ms-srv sshd[57925]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.129.168.73
Jan 19 02:10:35 ms-srv sshd[57925]: Failed password for invalid user 1502 from 217.129.168.73 port 53111 ssh2
2020-03-08 22:14:14
134.209.115.206 attackbotsspam
Mar  8 13:31:26 localhost sshd[56409]: Invalid user root^1234 from 134.209.115.206 port 41640
Mar  8 13:31:26 localhost sshd[56409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.115.206
Mar  8 13:31:26 localhost sshd[56409]: Invalid user root^1234 from 134.209.115.206 port 41640
Mar  8 13:31:28 localhost sshd[56409]: Failed password for invalid user root^1234 from 134.209.115.206 port 41640 ssh2
Mar  8 13:37:56 localhost sshd[56896]: Invalid user alicante from 134.209.115.206 port 48094
...
2020-03-08 21:52:02
217.16.143.113 attackspambots
Nov  2 18:43:21 ms-srv sshd[58064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.16.143.113
Nov  2 18:43:23 ms-srv sshd[58064]: Failed password for invalid user inmate from 217.16.143.113 port 52786 ssh2
2020-03-08 21:58:06
139.162.112.248 attackbotsspam
firewall-block, port(s): 8080/tcp
2020-03-08 21:36:16
37.123.163.106 attack
Mar  8 13:59:19 ns382633 sshd\[18508\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.123.163.106  user=root
Mar  8 13:59:22 ns382633 sshd\[18508\]: Failed password for root from 37.123.163.106 port 63695 ssh2
Mar  8 14:10:31 ns382633 sshd\[20923\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.123.163.106  user=root
Mar  8 14:10:33 ns382633 sshd\[20923\]: Failed password for root from 37.123.163.106 port 63695 ssh2
Mar  8 14:18:59 ns382633 sshd\[22047\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.123.163.106  user=root
2020-03-08 21:37:20
198.245.49.37 attackspambots
Mar  8 20:33:24 webhost01 sshd[25069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.245.49.37
Mar  8 20:33:27 webhost01 sshd[25069]: Failed password for invalid user aapje123 from 198.245.49.37 port 36268 ssh2
...
2020-03-08 21:47:25
217.146.30.27 attackbots
Oct 22 01:34:30 ms-srv sshd[11789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.146.30.27
Oct 22 01:34:33 ms-srv sshd[11789]: Failed password for invalid user PRODDTA from 217.146.30.27 port 52370 ssh2
2020-03-08 22:07:14
218.72.217.162 attack
Honeypot attack, port: 445, PTR: 162.217.72.218.broad.ls.zj.dynamic.163data.com.cn.
2020-03-08 21:31:53
217.14.208.84 attackspam
May 22 18:55:46 ms-srv sshd[38009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.14.208.84
May 22 18:55:49 ms-srv sshd[38009]: Failed password for invalid user admin from 217.14.208.84 port 38522 ssh2
2020-03-08 22:08:24
222.186.30.218 attackspambots
IP blocked
2020-03-08 22:06:47

Recently Reported IPs

234.48.27.84 4.226.57.198 48.26.209.38 135.132.13.198
243.132.229.44 46.199.246.37 99.21.203.224 131.192.80.26
40.252.214.148 20.85.172.140 156.134.210.1 81.118.53.181
125.18.123.216 133.70.187.229 47.243.126.52 119.41.233.80
108.39.218.207 243.16.220.90 12.166.242.4 164.109.222.227