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
134.122.124.226 attack
Malicious IP
2024-05-06 13:41:50
134.122.126.136 attack
TCP port : 27017
2020-09-05 01:45:16
134.122.120.85 attackbots
Unauthorised access (Sep  3) SRC=134.122.120.85 LEN=40 TTL=243 ID=7771 TCP DPT=3389 WINDOW=1024 SYN 
Unauthorised access (Sep  2) SRC=134.122.120.85 LEN=40 TTL=243 ID=28464 TCP DPT=3389 WINDOW=1024 SYN
2020-09-05 00:42:08
134.122.120.85 attackspambots
Unauthorised access (Sep  3) SRC=134.122.120.85 LEN=40 TTL=243 ID=7771 TCP DPT=3389 WINDOW=1024 SYN 
Unauthorised access (Sep  2) SRC=134.122.120.85 LEN=40 TTL=243 ID=28464 TCP DPT=3389 WINDOW=1024 SYN
2020-09-04 16:06:53
134.122.120.85 attackbotsspam
Unauthorised access (Sep  3) SRC=134.122.120.85 LEN=40 TTL=243 ID=7771 TCP DPT=3389 WINDOW=1024 SYN 
Unauthorised access (Sep  2) SRC=134.122.120.85 LEN=40 TTL=243 ID=28464 TCP DPT=3389 WINDOW=1024 SYN
2020-09-04 08:26:06
134.122.120.236 attack
Unauthorized connection attempt detected from IP address 134.122.120.236 to port 3389 [T]
2020-08-31 13:45:14
134.122.127.196 attackspambots
SS1,DEF GET /adminer-3.6.1.php
2020-08-30 02:49:46
134.122.120.74 attackbotsspam
134.122.120.74 - - [26/Aug/2020:07:10:47 +0100] "POST /wp-login.php HTTP/1.1" 200 2369 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.122.120.74 - - [26/Aug/2020:07:10:48 +0100] "POST /wp-login.php HTTP/1.1" 200 2364 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.122.120.74 - - [26/Aug/2020:07:10:48 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-08-26 20:36:26
134.122.124.193 attack
Invalid user lia from 134.122.124.193 port 59936
2020-08-21 16:34:03
134.122.124.193 attackspam
Invalid user max from 134.122.124.193 port 41542
2020-08-19 20:21:49
134.122.120.74 attackspambots
Attempts to probe web pages for vulnerable PHP or other applications
2020-08-15 13:24:06
134.122.124.193 attackbotsspam
134.122.124.193 (US/United States/-), 12 distributed sshd attacks on account [root] in the last 3600 secs
2020-08-15 02:52:35
134.122.120.205 attack
Unauthorized connection attempt detected from IP address 134.122.120.205 to port 8088 [T]
2020-08-14 02:27:49
134.122.120.74 attackspam
134.122.120.74 - - [13/Aug/2020:14:18:38 +0200] "GET /wp-login.php HTTP/1.1" 200 6398 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.122.120.74 - - [13/Aug/2020:14:18:40 +0200] "POST /wp-login.php HTTP/1.1" 200 6649 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.122.120.74 - - [13/Aug/2020:14:18:41 +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-08-13 22:38:47
134.122.124.193 attackspambots
Aug  8 15:15:41 ajax sshd[1642]: Failed password for root from 134.122.124.193 port 60454 ssh2
2020-08-08 23:24:10
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.122.12.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1462
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.122.12.139.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 05:50:38 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 139.12.122.134.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.12.122.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
121.162.131.223 attackspam
Nov 23 23:25:03 sachi sshd\[16562\]: Invalid user elasticsearch from 121.162.131.223
Nov 23 23:25:03 sachi sshd\[16562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.162.131.223
Nov 23 23:25:05 sachi sshd\[16562\]: Failed password for invalid user elasticsearch from 121.162.131.223 port 50202 ssh2
Nov 23 23:28:42 sachi sshd\[16869\]: Invalid user admin from 121.162.131.223
Nov 23 23:28:42 sachi sshd\[16869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.162.131.223
2019-11-24 17:44:04
213.251.41.52 attackspambots
Brute-force attempt banned
2019-11-24 17:38:16
38.142.21.58 attackspambots
Nov 24 08:58:06 venus sshd\[12082\]: Invalid user waidyaratne from 38.142.21.58 port 31019
Nov 24 08:58:06 venus sshd\[12082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=38.142.21.58
Nov 24 08:58:07 venus sshd\[12082\]: Failed password for invalid user waidyaratne from 38.142.21.58 port 31019 ssh2
...
2019-11-24 17:04:50
222.186.175.215 attackbots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.215  user=root
Failed password for root from 222.186.175.215 port 35510 ssh2
Failed password for root from 222.186.175.215 port 35510 ssh2
Failed password for root from 222.186.175.215 port 35510 ssh2
Failed password for root from 222.186.175.215 port 35510 ssh2
2019-11-24 17:09:18
202.154.58.243 attackspambots
Automatic report - XMLRPC Attack
2019-11-24 17:11:59
131.161.84.232 attackspam
Automatic report - Port Scan Attack
2019-11-24 17:29:16
96.11.211.180 attackbots
Portscan or hack attempt detected by psad/fwsnort
2019-11-24 17:30:47
1.1.214.172 attack
Nov 24 08:14:42 heissa sshd\[1603\]: Invalid user buster from 1.1.214.172 port 40912
Nov 24 08:14:42 heissa sshd\[1603\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.1.214.172
Nov 24 08:14:44 heissa sshd\[1603\]: Failed password for invalid user buster from 1.1.214.172 port 40912 ssh2
Nov 24 08:21:14 heissa sshd\[5401\]: Invalid user admin from 1.1.214.172 port 49416
Nov 24 08:21:14 heissa sshd\[5401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.1.214.172
2019-11-24 17:22:26
222.186.180.8 attackbotsspam
Nov 23 23:31:56 hpm sshd\[22978\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8  user=root
Nov 23 23:31:59 hpm sshd\[22978\]: Failed password for root from 222.186.180.8 port 19624 ssh2
Nov 23 23:32:11 hpm sshd\[22978\]: Failed password for root from 222.186.180.8 port 19624 ssh2
Nov 23 23:32:15 hpm sshd\[23020\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8  user=root
Nov 23 23:32:16 hpm sshd\[23020\]: Failed password for root from 222.186.180.8 port 36886 ssh2
2019-11-24 17:34:32
86.190.249.226 attackspambots
Microsoft-Windows-Security-Auditing
2019-11-24 17:04:28
185.220.101.46 attackbots
Unauthorized access detected from banned ip
2019-11-24 17:17:43
180.76.100.246 attackspam
404 NOT FOUND
2019-11-24 17:43:26
123.207.233.222 attack
Nov 24 10:05:19 meumeu sshd[7914]: Failed password for root from 123.207.233.222 port 59922 ssh2
Nov 24 10:13:11 meumeu sshd[8902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.233.222 
Nov 24 10:13:14 meumeu sshd[8902]: Failed password for invalid user zczyz from 123.207.233.222 port 36740 ssh2
...
2019-11-24 17:28:36
179.119.249.144 attackspambots
Nov 24 07:08:30 db01 sshd[21139]: reveeclipse mapping checking getaddrinfo for 179-119-249-144.user.vivozap.com.br [179.119.249.144] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 24 07:08:30 db01 sshd[21139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.119.249.144  user=r.r
Nov 24 07:08:32 db01 sshd[21139]: Failed password for r.r from 179.119.249.144 port 1057 ssh2
Nov 24 07:08:33 db01 sshd[21139]: Received disconnect from 179.119.249.144: 11: Bye Bye [preauth]
Nov 24 07:08:35 db01 sshd[21173]: reveeclipse mapping checking getaddrinfo for 179-119-249-144.user.vivozap.com.br [179.119.249.144] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 24 07:08:35 db01 sshd[21173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.119.249.144  user=r.r
Nov 24 07:08:36 db01 sshd[21173]: Failed password for r.r from 179.119.249.144 port 1058 ssh2
Nov 24 07:08:37 db01 sshd[21173]: Received disconnect from 179.1........
-------------------------------
2019-11-24 17:24:27
178.150.184.114 attackspambots
Nov 24 07:15:26 mxgate1 postfix/postscreen[13998]: CONNECT from [178.150.184.114]:10606 to [176.31.12.44]:25
Nov 24 07:15:26 mxgate1 postfix/dnsblog[14022]: addr 178.150.184.114 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 24 07:15:26 mxgate1 postfix/dnsblog[14021]: addr 178.150.184.114 listed by domain bl.spamcop.net as 127.0.0.2
Nov 24 07:15:26 mxgate1 postfix/dnsblog[14023]: addr 178.150.184.114 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 24 07:15:26 mxgate1 postfix/dnsblog[14019]: addr 178.150.184.114 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Nov 24 07:15:26 mxgate1 postfix/dnsblog[14020]: addr 178.150.184.114 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 24 07:15:32 mxgate1 postfix/postscreen[13998]: DNSBL rank 6 for [178.150.184.114]:10606
Nov x@x
Nov 24 07:15:33 mxgate1 postfix/postscreen[13998]: HANGUP after 0.57 from [178.150.184.114]:10606 in tests after SMTP handshake
Nov 24 07:15:33 mxgate1 postfix/postscreen[13998]: DISCONNECT........
-------------------------------
2019-11-24 17:39:09

Recently Reported IPs

134.122.119.16 134.122.118.237 118.173.101.204 134.122.119.83
134.122.118.99 134.122.12.102 134.122.119.118 134.122.12.203
118.173.101.211 134.122.120.159 134.122.120.157 134.122.120.76
134.122.120.3 134.122.120.49 134.122.121.100 134.122.121.189
134.122.120.63 134.122.121.59 134.122.121.4 134.122.121.74