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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 133.242.249.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8407
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;133.242.249.20.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:38:59 CST 2022
;; MSG SIZE  rcvd: 107
Host info
20.249.242.133.in-addr.arpa domain name pointer www4110.sakura.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
20.249.242.133.in-addr.arpa	name = www4110.sakura.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.220.101.7 attackbotsspam
Splunk® : Brute-Force login attempt on SSH:
Aug 12 13:06:38 testbed sshd[22891]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.7  user=root
2019-08-13 01:10:36
113.59.224.89 attackspambots
Unauthorised access (Aug 12) SRC=113.59.224.89 LEN=40 TTL=240 ID=58428 TCP DPT=445 WINDOW=1024 SYN
2019-08-13 01:22:42
80.108.224.218 attackbotsspam
Automatic report - Port Scan Attack
2019-08-13 01:24:21
179.95.101.109 attack
firewall-block, port(s): 445/tcp
2019-08-13 00:59:46
13.80.16.81 attack
Aug 12 18:51:19 MK-Soft-Root1 sshd\[28186\]: Invalid user newuser from 13.80.16.81 port 58734
Aug 12 18:51:19 MK-Soft-Root1 sshd\[28186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.80.16.81
Aug 12 18:51:21 MK-Soft-Root1 sshd\[28186\]: Failed password for invalid user newuser from 13.80.16.81 port 58734 ssh2
...
2019-08-13 01:45:05
1.209.171.64 attackspam
$f2bV_matches_ltvn
2019-08-13 01:14:58
210.105.192.76 attackbots
SSH Brute Force, server-1 sshd[18304]: Failed password for invalid user scaner from 210.105.192.76 port 38363 ssh2
2019-08-13 01:23:46
139.59.42.211 attackspam
160/tcp 159/tcp 158/tcp...
[2019-06-15/08-12]243pkt,65pt.(tcp)
2019-08-13 00:55:59
52.179.180.63 attackspambots
Aug 12 07:37:44 aat-srv002 sshd[8642]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.179.180.63
Aug 12 07:37:46 aat-srv002 sshd[8642]: Failed password for invalid user admin3 from 52.179.180.63 port 56782 ssh2
Aug 12 07:42:14 aat-srv002 sshd[8758]: Failed password for root from 52.179.180.63 port 49122 ssh2
...
2019-08-13 01:27:08
52.73.169.169 attack
:
2019-08-13 01:03:59
104.238.116.19 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-13 01:34:52
59.1.116.20 attack
Aug 12 18:57:25 vpn01 sshd\[12237\]: Invalid user zimbra from 59.1.116.20
Aug 12 18:57:25 vpn01 sshd\[12237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.1.116.20
Aug 12 18:57:27 vpn01 sshd\[12237\]: Failed password for invalid user zimbra from 59.1.116.20 port 44386 ssh2
2019-08-13 01:07:52
194.190.71.9 attackspambots
Automatic report - Port Scan Attack
2019-08-13 01:45:28
190.82.46.97 attackspam
Automatic report - Port Scan Attack
2019-08-13 01:24:55
185.176.27.162 attackbots
08/12/2019-12:44:00.153569 185.176.27.162 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-13 00:58:49

Recently Reported IPs

133.242.50.140 133.242.48.66 133.242.58.100 133.242.45.49
133.242.52.104 133.242.5.149 133.242.50.148 133.242.51.119
133.242.54.12 133.242.54.87 133.242.6.220 133.242.6.80
133.242.70.210 133.242.74.253 133.242.6.73 133.242.68.55
133.242.76.220 133.242.6.237 133.242.74.118 133.242.72.59