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

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
133.242.228.107 attackbots
2019-08-20 08:50:38,798 fail2ban.actions        [878]: NOTICE  [sshd] Ban 133.242.228.107
2019-08-20 11:55:49,784 fail2ban.actions        [878]: NOTICE  [sshd] Ban 133.242.228.107
2019-08-20 15:02:29,310 fail2ban.actions        [878]: NOTICE  [sshd] Ban 133.242.228.107
...
2019-10-03 19:20:57
133.242.228.107 attackbotsspam
$f2bV_matches
2019-09-25 06:34:26
133.242.228.107 attack
Invalid user dados from 133.242.228.107 port 45034
2019-09-24 17:26:04
133.242.228.107 attackbots
Invalid user system from 133.242.228.107 port 40475
2019-09-20 16:11:09
133.242.228.107 attackbots
Automatic report - SSH Brute-Force Attack
2019-09-20 07:02:21
133.242.228.107 attackspambots
Automated report - ssh fail2ban:
Aug 27 04:50:49 authentication failure 
Aug 27 04:50:51 wrong password, user=developer, port=36742, ssh2
Aug 27 04:55:37 authentication failure
2019-08-27 13:52:37
133.242.228.107 attack
Aug 23 09:11:50 vps65 sshd\[1381\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107  user=git
Aug 23 09:11:53 vps65 sshd\[1381\]: Failed password for git from 133.242.228.107 port 35318 ssh2
...
2019-08-23 18:45:17
133.242.228.107 attackspambots
Automatic report - Banned IP Access
2019-08-23 01:49:38
133.242.228.107 attack
Repeated brute force against a port
2019-08-16 19:47:28
133.242.228.107 attack
Jul 18 14:31:54 mail sshd\[17992\]: Invalid user debian from 133.242.228.107 port 46342
Jul 18 14:31:54 mail sshd\[17992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul 18 14:31:57 mail sshd\[17992\]: Failed password for invalid user debian from 133.242.228.107 port 46342 ssh2
Jul 18 14:37:32 mail sshd\[19011\]: Invalid user dan from 133.242.228.107 port 46366
Jul 18 14:37:32 mail sshd\[19011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
2019-07-18 20:43:23
133.242.228.107 attackbotsspam
Jul 18 09:45:55 mail sshd\[28355\]: Invalid user ftpuser from 133.242.228.107 port 35255
Jul 18 09:45:55 mail sshd\[28355\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul 18 09:45:58 mail sshd\[28355\]: Failed password for invalid user ftpuser from 133.242.228.107 port 35255 ssh2
Jul 18 09:51:31 mail sshd\[29279\]: Invalid user el from 133.242.228.107 port 35276
Jul 18 09:51:31 mail sshd\[29279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
2019-07-18 16:08:50
133.242.228.107 attackbots
Jul 18 02:16:48 mail sshd\[13919\]: Invalid user bh from 133.242.228.107 port 56784
Jul 18 02:16:48 mail sshd\[13919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul 18 02:16:49 mail sshd\[13919\]: Failed password for invalid user bh from 133.242.228.107 port 56784 ssh2
Jul 18 02:22:27 mail sshd\[14909\]: Invalid user cms from 133.242.228.107 port 56825
Jul 18 02:22:27 mail sshd\[14909\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
2019-07-18 08:27:14
133.242.228.107 attack
Jul 12 20:56:46 legacy sshd[21079]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul 12 20:56:48 legacy sshd[21079]: Failed password for invalid user na from 133.242.228.107 port 51479 ssh2
Jul 12 21:02:40 legacy sshd[21248]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
...
2019-07-13 03:08:19
133.242.228.107 attackbots
Jul 12 09:02:42 legacy sshd[32291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul 12 09:02:44 legacy sshd[32291]: Failed password for invalid user rama from 133.242.228.107 port 34049 ssh2
Jul 12 09:08:49 legacy sshd[32438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
...
2019-07-12 15:19:10
133.242.228.107 attackbots
Jul  7 10:35:10 nextcloud sshd\[1197\]: Invalid user server from 133.242.228.107
Jul  7 10:35:10 nextcloud sshd\[1197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.242.228.107
Jul  7 10:35:12 nextcloud sshd\[1197\]: Failed password for invalid user server from 133.242.228.107 port 40986 ssh2
...
2019-07-07 18:43:37
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 133.242.228.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17947
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;133.242.228.69.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:38:54 CST 2022
;; MSG SIZE  rcvd: 107
Host info
69.228.242.133.in-addr.arpa domain name pointer server.hall-info.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
69.228.242.133.in-addr.arpa	name = server.hall-info.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.85.42.179 attackbots
Nov 28 09:58:19 server sshd\[22600\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.179  user=root
Nov 28 09:58:20 server sshd\[22605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.179  user=root
Nov 28 09:58:21 server sshd\[22602\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.179  user=root
Nov 28 09:58:22 server sshd\[22610\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.179  user=root
Nov 28 09:58:22 server sshd\[22600\]: Failed password for root from 112.85.42.179 port 57816 ssh2
...
2019-11-28 15:04:56
120.138.5.172 attackspam
Automatic report - Banned IP Access
2019-11-28 15:02:17
185.220.100.253 attack
Automatic report - Banned IP Access
2019-11-28 14:52:11
208.93.153.177 attackbotsspam
Attempted to connect 2 times to port 443 TCP
2019-11-28 14:56:39
63.81.87.100 attackspambots
Nov 28 07:30:06  exim[29266]: [1\51] 1iaDJU-0007c2-7N H=announce.vidyad.com (announce.alibash.com) [63.81.87.100] F= rejected after DATA: This message scored 99.8 spam points.
2019-11-28 14:49:15
164.52.24.176 attack
" "
2019-11-28 14:39:48
77.247.108.77 attackbotsspam
11/28/2019-07:29:56.768286 77.247.108.77 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 74
2019-11-28 15:18:14
119.196.83.14 attack
2019-11-28T06:30:47.451600abusebot-5.cloudsearch.cf sshd\[21608\]: Invalid user robert from 119.196.83.14 port 55802
2019-11-28 14:47:19
218.92.0.181 attack
2019-11-27T17:01:14.218591homeassistant sshd[21445]: Failed password for root from 218.92.0.181 port 38443 ssh2
2019-11-28T06:42:43.627005homeassistant sshd[17927]: Failed none for root from 218.92.0.181 port 6614 ssh2
2019-11-28T06:42:43.830510homeassistant sshd[17927]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.181  user=root
...
2019-11-28 14:43:09
178.207.12.10 attackbotsspam
Automatic report - Port Scan Attack
2019-11-28 14:59:14
222.186.175.182 attackbotsspam
Nov 28 11:50:30 gw1 sshd[20168]: Failed password for root from 222.186.175.182 port 26414 ssh2
Nov 28 11:50:42 gw1 sshd[20168]: error: maximum authentication attempts exceeded for root from 222.186.175.182 port 26414 ssh2 [preauth]
...
2019-11-28 14:51:39
123.20.98.28 attackbots
Nov 28 07:15:59 nexus sshd[9181]: Invalid user admin from 123.20.98.28 port 51911
Nov 28 07:15:59 nexus sshd[9181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.20.98.28
Nov 28 07:16:01 nexus sshd[9181]: Failed password for invalid user admin from 123.20.98.28 port 51911 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=123.20.98.28
2019-11-28 15:01:45
95.210.109.129 attackbots
Wordpress login scanning
2019-11-28 14:48:15
41.93.32.88 attack
Nov 28 11:31:06 gw1 sshd[19771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.93.32.88
Nov 28 11:31:07 gw1 sshd[19771]: Failed password for invalid user collazos from 41.93.32.88 port 47784 ssh2
...
2019-11-28 14:50:55
206.189.133.82 attackbotsspam
Nov 28 03:22:51 firewall sshd[26738]: Invalid user server from 206.189.133.82
Nov 28 03:22:54 firewall sshd[26738]: Failed password for invalid user server from 206.189.133.82 port 36126 ssh2
Nov 28 03:29:58 firewall sshd[26862]: Invalid user aaa from 206.189.133.82
...
2019-11-28 15:15:43

Recently Reported IPs

133.242.214.112 133.242.23.185 133.242.23.200 133.242.242.76
133.242.233.15 133.242.249.141 133.242.234.66 133.242.243.165
133.242.249.82 133.242.249.152 133.242.249.16 133.242.249.65
133.242.249.178 133.242.28.6 133.242.249.226 133.242.249.38
133.242.249.75 133.242.50.140 133.242.249.20 133.242.48.66