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

;; QUESTION SECTION:
;133.11.30.11.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 10:16:47 CST 2025
;; MSG SIZE  rcvd: 105
Host info
11.30.11.133.in-addr.arpa domain name pointer csc-mst.is.s.u-tokyo.ac.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
11.30.11.133.in-addr.arpa	name = csc-mst.is.s.u-tokyo.ac.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
200.133.39.24 attackspam
Jan 12 16:34:47 vps691689 sshd[26942]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.133.39.24
Jan 12 16:34:49 vps691689 sshd[26942]: Failed password for invalid user batch from 200.133.39.24 port 45692 ssh2
Jan 12 16:38:21 vps691689 sshd[27081]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.133.39.24
...
2020-01-12 23:52:46
179.109.171.200 attackbotsspam
Unauthorized connection attempt detected from IP address 179.109.171.200 to port 8000 [J]
2020-01-12 23:58:32
106.12.181.34 attackbotsspam
Unauthorized connection attempt detected from IP address 106.12.181.34 to port 2220 [J]
2020-01-13 00:07:59
201.95.128.178 attack
Unauthorized connection attempt detected from IP address 201.95.128.178 to port 8080 [J]
2020-01-12 23:51:56
92.119.237.48 attack
Unauthorized connection attempt detected from IP address 92.119.237.48 to port 8080 [J]
2020-01-13 00:09:53
173.208.235.230 attackbots
Unauthorized connection attempt detected from IP address 173.208.235.230 to port 2220 [J]
2020-01-13 00:00:48
85.105.7.114 attackspambots
Unauthorized connection attempt detected from IP address 85.105.7.114 to port 23 [J]
2020-01-12 23:45:01
119.189.241.171 attackbots
Unauthorized connection attempt detected from IP address 119.189.241.171 to port 1433 [T]
2020-01-12 23:36:20
116.106.29.192 attackspambots
Unauthorized connection attempt detected from IP address 116.106.29.192 to port 81 [J]
2020-01-12 23:37:51
92.112.41.113 attackbotsspam
Unauthorized connection attempt detected from IP address 92.112.41.113 to port 80 [J]
2020-01-12 23:42:23
201.0.84.244 attackspambots
Unauthorized connection attempt detected from IP address 201.0.84.244 to port 23 [J]
2020-01-12 23:52:27
180.107.185.23 attackspam
Unauthorized connection attempt detected from IP address 180.107.185.23 to port 81 [J]
2020-01-12 23:57:16
46.143.206.136 attackspam
Unauthorized connection attempt detected from IP address 46.143.206.136 to port 81 [J]
2020-01-13 00:13:50
149.56.45.36 attackspam
Unauthorized connection attempt detected from IP address 149.56.45.36 to port 23 [J]
2020-01-13 00:02:25
177.47.192.75 attackbots
Unauthorized connection attempt detected from IP address 177.47.192.75 to port 23 [J]
2020-01-13 00:00:31

Recently Reported IPs

226.200.92.152 193.44.115.236 224.24.121.59 223.67.74.77
210.62.12.141 215.79.176.68 115.159.231.96 163.20.124.252
178.149.115.47 98.127.24.81 230.12.212.160 199.248.8.221
47.237.76.180 145.251.4.12 157.14.94.20 60.145.234.54
59.199.142.235 9.145.145.85 64.143.120.247 242.185.216.93