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: United States

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

;; QUESTION SECTION:
;135.121.50.134.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 19:55:53 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 134.50.121.135.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.50.121.135.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
177.8.250.54 attackbots
SMTP-sasl brute force
...
2019-06-29 15:57:44
68.183.106.84 attackspam
Invalid user amssys from 68.183.106.84 port 45096
2019-06-29 15:38:58
139.59.180.53 attackspam
Jun 29 07:58:16 MK-Soft-VM6 sshd\[13339\]: Invalid user applmgr from 139.59.180.53 port 59172
Jun 29 07:58:17 MK-Soft-VM6 sshd\[13339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.180.53
Jun 29 07:58:19 MK-Soft-VM6 sshd\[13339\]: Failed password for invalid user applmgr from 139.59.180.53 port 59172 ssh2
...
2019-06-29 16:00:21
159.65.185.225 attackbots
Jun 29 02:12:00 XXXXXX sshd[33918]: Invalid user tftpd from 159.65.185.225 port 56692
2019-06-29 15:32:49
112.164.48.84 attackbots
Jun 29 00:43:11 localhost sshd\[21988\]: Invalid user admin from 112.164.48.84 port 33884
Jun 29 00:43:12 localhost sshd\[21988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.164.48.84
...
2019-06-29 15:53:11
200.69.250.253 attackspambots
Jun 29 06:32:34 sshgateway sshd\[5390\]: Invalid user zimbra from 200.69.250.253
Jun 29 06:32:34 sshgateway sshd\[5390\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.69.250.253
Jun 29 06:32:36 sshgateway sshd\[5390\]: Failed password for invalid user zimbra from 200.69.250.253 port 33254 ssh2
2019-06-29 16:09:24
60.167.23.24 attack
IP reached maximum auth failures
2019-06-29 15:21:55
91.225.163.153 attack
Automatic report - Web App Attack
2019-06-29 15:21:07
14.231.239.180 attackbots
Jun 29 00:45:51 master sshd[22259]: Failed password for invalid user admin from 14.231.239.180 port 37934 ssh2
2019-06-29 15:24:31
177.11.116.234 attackspambots
Brute force attempt
2019-06-29 15:47:28
181.111.181.50 attackbots
Jun 29 06:11:55 vps65 sshd\[30445\]: Invalid user mongodb from 181.111.181.50 port 56624
Jun 29 06:11:55 vps65 sshd\[30445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.111.181.50
...
2019-06-29 15:38:31
150.95.129.150 attackspam
2019-06-29T07:31:14.583501abusebot-5.cloudsearch.cf sshd\[17717\]: Invalid user node from 150.95.129.150 port 56046
2019-06-29 15:52:39
220.181.108.171 attack
Automatic report - Web App Attack
2019-06-29 15:19:01
103.27.238.202 attackspam
v+ssh-bruteforce
2019-06-29 16:06:19
14.186.168.223 attackbotsspam
Jun 29 02:06:18 master sshd[22364]: Failed password for invalid user admin from 14.186.168.223 port 57502 ssh2
2019-06-29 15:40:51

Recently Reported IPs

244.73.127.13 152.149.140.117 199.168.235.149 198.168.137.120
204.137.202.220 144.51.183.50 113.127.42.83 0.173.159.136
149.134.90.244 169.84.52.237 197.17.135.42 198.45.65.209
191.148.197.4 0.30.14.47 165.10.156.118 101.107.28.49
167.107.120.54 235.8.192.53 214.26.253.98 200.3.186.114