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

Region: Tokyo

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

;; QUESTION SECTION:
;133.9.0.52.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jun 28 12:42:31 CST 2025
;; MSG SIZE  rcvd: 103
Host info
Host 52.0.9.133.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 52.0.9.133.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.12.197.52 attackbots
Brute-force attempt banned
2020-04-21 19:58:40
114.234.4.249 attack
SpamScore above: 10.0
2020-04-21 19:38:25
103.247.217.147 attack
WordPress login Brute force / Web App Attack on client site.
2020-04-21 19:23:02
202.98.248.123 attackspambots
Invalid user ps from 202.98.248.123 port 58797
2020-04-21 20:02:44
218.70.19.74 attackspam
Unauthorized connection attempt detected from IP address 218.70.19.74 to port 139
2020-04-21 19:51:26
178.32.218.192 attackspambots
Invalid user admin from 178.32.218.192 port 42066
2020-04-21 20:03:36
152.32.135.17 attackspambots
Invalid user km from 152.32.135.17 port 58054
2020-04-21 20:05:00
59.36.151.0 attackbotsspam
Unauthorised connection attempt detected at AUO NODE 1. System is sshd. Protected by AUO Stack Web Application Firewall (WAF)
2020-04-21 19:24:02
92.63.194.30 attack
Unauthorized connection attempt detected from IP address 92.63.194.30 to port 1945
2020-04-21 19:25:01
49.233.90.66 attackbots
Apr 21 12:39:39 roki sshd[22231]: Invalid user user from 49.233.90.66
Apr 21 12:39:39 roki sshd[22231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.90.66
Apr 21 12:39:41 roki sshd[22231]: Failed password for invalid user user from 49.233.90.66 port 54302 ssh2
Apr 21 12:45:08 roki sshd[22595]: Invalid user fq from 49.233.90.66
Apr 21 12:45:08 roki sshd[22595]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.90.66
...
2020-04-21 19:31:40
106.54.44.202 attack
Apr 21 18:41:50 webhost01 sshd[9975]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.44.202
Apr 21 18:41:51 webhost01 sshd[9975]: Failed password for invalid user eu from 106.54.44.202 port 58812 ssh2
...
2020-04-21 19:54:19
103.26.195.54 attackspam
Unauthorized connection attempt detected from IP address 103.26.195.54 to port 445
2020-04-21 19:37:29
49.235.77.83 attackspam
Apr 21 13:19:06 prox sshd[5584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.77.83 
Apr 21 13:19:07 prox sshd[5584]: Failed password for invalid user space from 49.235.77.83 port 47890 ssh2
2020-04-21 19:25:41
159.89.133.144 attack
$f2bV_matches
2020-04-21 19:47:32
153.236.121.137 attackbotsspam
Automatic report - Port Scan Attack
2020-04-21 19:28:54

Recently Reported IPs

116.146.52.213 15.71.74.248 183.171.113.130 113.88.197.98
150.137.5.241 57.5.242.24 53.90.149.28 102.120.7.76
58.114.252.26 11.60.153.40 28.14.72.131 223.96.219.119
56.149.224.223 111.142.211.143 42.161.136.194 220.62.82.121
24.83.147.131 58.184.162.231 165.149.105.21 33.235.194.13