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

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:
IP Type Details Datetime
14.134.189.33 attackbots
Lines containing failures of 14.134.189.33
Jun 25 05:51:50 nexus sshd[1099]: Invalid user discover from 14.134.189.33 port 42428
Jun 25 05:51:50 nexus sshd[1099]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.134.189.33
Jun 25 05:51:52 nexus sshd[1099]: Failed password for invalid user discover from 14.134.189.33 port 42428 ssh2
Jun 25 05:51:53 nexus sshd[1099]: Received disconnect from 14.134.189.33 port 42428:11: Bye Bye [preauth]
Jun 25 05:51:53 nexus sshd[1099]: Disconnected from 14.134.189.33 port 42428 [preauth]
Jun 25 05:55:00 nexus sshd[1136]: Invalid user qa from 14.134.189.33 port 52558
Jun 25 05:55:00 nexus sshd[1136]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.134.189.33


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=14.134.189.33
2020-06-25 14:17:26
14.134.189.204 attackbotsspam
SSH login attempts.
2020-05-28 19:51:02
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.134.189.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;14.134.189.134.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:59:59 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 134.189.134.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 134.189.134.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
2a01:4f8:202:5106::2 attackbots
xmlrpc attack
2020-04-01 00:20:19
185.220.101.33 attack
Automatic report - Port Scan
2020-03-31 23:53:00
138.197.195.52 attackspam
Mar 31 17:11:09 ovpn sshd\[6390\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.195.52  user=root
Mar 31 17:11:10 ovpn sshd\[6390\]: Failed password for root from 138.197.195.52 port 38402 ssh2
Mar 31 17:18:33 ovpn sshd\[8060\]: Invalid user zhuowan from 138.197.195.52
Mar 31 17:18:33 ovpn sshd\[8060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.195.52
Mar 31 17:18:36 ovpn sshd\[8060\]: Failed password for invalid user zhuowan from 138.197.195.52 port 50192 ssh2
2020-03-31 23:59:01
122.227.16.242 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-04-01 00:22:36
95.213.177.123 attackspambots
Port scan on 1 port(s): 8080
2020-03-31 23:46:02
39.101.208.109 attack
trying to access non-authorized port
2020-03-31 23:32:51
196.52.84.46 attackbotsspam
fell into ViewStateTrap:amsterdam
2020-04-01 00:00:53
181.209.63.116 attack
Mar 31 06:37:33 our-server-hostname sshd[10981]: reveeclipse mapping checking getaddrinfo for 116.63.209.181.in-addr.arpa [181.209.63.116] failed - POSSIBLE BREAK-IN ATTEMPT!
Mar 31 06:37:33 our-server-hostname sshd[10981]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.209.63.116  user=r.r
Mar 31 06:37:35 our-server-hostname sshd[10981]: Failed password for r.r from 181.209.63.116 port 43261 ssh2
Mar 31 06:46:45 our-server-hostname sshd[12850]: reveeclipse mapping checking getaddrinfo for 116.63.209.181.in-addr.arpa [181.209.63.116] failed - POSSIBLE BREAK-IN ATTEMPT!
Mar 31 06:46:45 our-server-hostname sshd[12850]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.209.63.116  user=r.r
Mar 31 06:46:47 our-server-hostname sshd[12850]: Failed password for r.r from 181.209.63.116 port 34182 ssh2
Mar 31 06:51:05 our-server-hostname sshd[13791]: reveeclipse mapping checking getaddrinfo fo........
-------------------------------
2020-04-01 00:17:23
58.49.94.230 attackbotsspam
Unauthorized connection attempt detected from IP address 58.49.94.230 to port 1433
2020-03-31 23:46:54
138.68.46.85 attack
Spoofing spamming phishing fraudulent perpetrator of various scams, including fake scratch cards, fake Netflix offers, spoofed BT messages, delayed parcels awaiting shipment, please confirm transaction, a new message is waiting for you, your Bitcoin transaction has been approved, bogus investment scams, or false mobile phone offers. This is sent from a different domain and IP address each and every time. This one has come from  domain of @repertoirepool.com designates 138.68.46.85 as permitted sender.
2020-03-31 23:45:38
82.221.131.71 attack
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: Invalid user pgadmin from 82.221.131.71
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.221.131.71
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: Invalid user pgadmin from 82.221.131.71
Mar 31 16:54:05 srv-ubuntu-dev3 sshd[106970]: Failed password for invalid user pgadmin from 82.221.131.71 port 41962 ssh2
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.221.131.71
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: Invalid user pgadmin from 82.221.131.71
Mar 31 16:54:05 srv-ubuntu-dev3 sshd[106970]: Failed password for invalid user pgadmin from 82.221.131.71 port 41962 ssh2
Mar 31 16:54:08 srv-ubuntu-dev3 sshd[106970]: Failed password for invalid user pgadmin from 82.221.131.71 port 41962 ssh2
Mar 31 16:54:03 srv-ubuntu-dev3 sshd[106970]: pam_unix(sshd:auth): authenticatio
...
2020-03-31 23:41:07
188.95.231.105 attack
Mar 30 11:39:45 foo sshd[30487]: Did not receive identification string from 188.95.231.105
Mar 30 11:41:41 foo sshd[30512]: Invalid user test from 188.95.231.105
Mar 30 11:41:41 foo sshd[30512]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.95.231.105 
Mar 30 11:41:43 foo sshd[30512]: Failed password for invalid user test from 188.95.231.105 port 55236 ssh2
Mar 30 11:41:43 foo sshd[30512]: Received disconnect from 188.95.231.105: 11: Bye Bye [preauth]
Mar 30 11:42:37 foo sshd[30520]: Invalid user kafka from 188.95.231.105
Mar 30 11:42:37 foo sshd[30520]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.95.231.105 
Mar 30 11:42:39 foo sshd[30520]: Failed password for invalid user kafka from 188.95.231.105 port 60178 ssh2
Mar 30 11:42:39 foo sshd[30520]: Received disconnect from 188.95.231.105: 11: Bye Bye [preauth]
Mar 30 11:43:33 foo sshd[30534]: Invalid user test1 from 188.95.231.1........
-------------------------------
2020-04-01 00:26:53
188.162.53.43 attackbots
Honeypot attack, port: 445, PTR: client.yota.ru.
2020-04-01 00:05:12
80.82.65.74 attackspam
03/31/2020-11:33:57.446693 80.82.65.74 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-04-01 00:00:25
121.11.111.230 attackbotsspam
DATE:2020-03-31 17:42:01, IP:121.11.111.230, PORT:ssh SSH brute force auth (docker-dc)
2020-04-01 00:06:34

Recently Reported IPs

14.134.189.114 14.134.189.119 14.134.189.126 14.134.189.142
14.134.189.140 14.134.189.14 14.134.189.125 14.134.189.144
14.134.189.159 14.134.189.139 14.134.189.150 14.134.189.156
14.134.189.154 14.134.189.161 14.134.189.152 14.134.189.188
14.134.189.192 14.134.189.184 14.134.189.162 14.134.189.199