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

;; QUESTION SECTION:
;221.45.229.136.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 23:35:59 CST 2025
;; MSG SIZE  rcvd: 107
Host info
136.229.45.221.in-addr.arpa domain name pointer softbank221045229136.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
136.229.45.221.in-addr.arpa	name = softbank221045229136.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.200.151.221 attackbotsspam
Automatic report - Port Scan Attack
2019-11-14 07:08:10
114.38.46.162 attack
23/tcp
[2019-11-13]1pkt
2019-11-14 07:22:39
139.59.95.216 attackbots
SSH Brute-Force attacks
2019-11-14 07:02:24
106.54.95.232 attackspam
Nov 13 23:59:09 vpn01 sshd[936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.95.232
Nov 13 23:59:11 vpn01 sshd[936]: Failed password for invalid user rueth from 106.54.95.232 port 38240 ssh2
...
2019-11-14 07:12:11
185.247.59.153 attackspambots
23/tcp
[2019-11-13]1pkt
2019-11-14 07:03:38
185.176.27.254 attack
11/13/2019-18:10:06.242469 185.176.27.254 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-14 07:11:58
121.143.171.119 attackspam
$f2bV_matches
2019-11-14 06:56:53
212.237.4.214 attack
2019-11-13T22:49:53.312696shield sshd\[12428\]: Invalid user manol from 212.237.4.214 port 41404
2019-11-13T22:49:53.318573shield sshd\[12428\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.4.214
2019-11-13T22:49:55.082919shield sshd\[12428\]: Failed password for invalid user manol from 212.237.4.214 port 41404 ssh2
2019-11-13T22:53:35.723321shield sshd\[12788\]: Invalid user farrelly from 212.237.4.214 port 50024
2019-11-13T22:53:35.729218shield sshd\[12788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.4.214
2019-11-14 06:58:56
104.140.188.58 attackbots
Port scan: Attack repeated for 24 hours
2019-11-14 06:57:30
92.119.160.106 attackbots
Nov 13 23:52:04 h2177944 kernel: \[6561043.222228\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.106 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=46710 PROTO=TCP SPT=51182 DPT=63664 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 13 23:55:16 h2177944 kernel: \[6561235.337198\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.106 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=3184 PROTO=TCP SPT=51182 DPT=63586 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 13 23:56:51 h2177944 kernel: \[6561329.988943\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.106 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=13632 PROTO=TCP SPT=51182 DPT=63571 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 14 00:01:31 h2177944 kernel: \[6561609.984818\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.106 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=14263 PROTO=TCP SPT=51182 DPT=63649 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 14 00:01:46 h2177944 kernel: \[6561625.320985\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.106 DST=85.2
2019-11-14 07:07:43
42.239.160.145 attackbotsspam
23/tcp
[2019-11-13]1pkt
2019-11-14 07:02:58
41.82.208.182 attack
2019-11-13T22:52:04.357054shield sshd\[12646\]: Invalid user daniluk from 41.82.208.182 port 19317
2019-11-13T22:52:04.361295shield sshd\[12646\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.82.208.182
2019-11-13T22:52:06.110475shield sshd\[12646\]: Failed password for invalid user daniluk from 41.82.208.182 port 19317 ssh2
2019-11-13T22:59:14.712329shield sshd\[13120\]: Invalid user test123 from 41.82.208.182 port 41074
2019-11-13T22:59:14.716578shield sshd\[13120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.82.208.182
2019-11-14 07:09:41
49.88.112.118 attackbots
Nov 13 17:06:14 minden010 sshd[555]: Failed password for root from 49.88.112.118 port 39479 ssh2
Nov 13 17:07:20 minden010 sshd[652]: Failed password for root from 49.88.112.118 port 24096 ssh2
Nov 13 17:07:23 minden010 sshd[652]: Failed password for root from 49.88.112.118 port 24096 ssh2
...
2019-11-14 06:58:04
45.82.153.35 attackbotsspam
45.82.153.35 was recorded 44 times by 19 hosts attempting to connect to the following ports: 15588,15544,25566,15511,25555,15522,25544,25588,25511,15566,15555,25533,25577,15577,15500,25522,26398,20778,19009,57900,25500,36540,38907,25599,19010,43288. Incident counter (4h, 24h, all-time): 44, 352, 3412
2019-11-14 07:12:57
197.46.35.184 attackbots
port scan and connect, tcp 23 (telnet)
2019-11-14 07:27:25

Recently Reported IPs

79.238.207.155 146.97.165.176 161.246.122.247 252.63.100.139
176.40.49.120 121.115.132.39 54.79.81.192 67.113.230.14
94.214.240.103 2.130.139.175 171.199.247.172 216.49.64.213
230.14.61.232 52.55.128.149 241.212.101.23 121.173.225.255
33.234.15.58 234.28.128.66 89.40.176.131 44.44.78.82