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: United States of America (the)

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

;; QUESTION SECTION:
;134.224.11.21.			IN	A

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

;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 04:56:58 CST 2025
;; MSG SIZE  rcvd: 106
Host info
21.11.224.134.in-addr.arpa domain name pointer 134-224-11-21.zoom.us.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.11.224.134.in-addr.arpa	name = 134-224-11-21.zoom.us.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.98.210.210 attack
ssh brute force
2020-05-28 15:53:52
117.240.172.19 attackspambots
May 28 06:00:01 inter-technics sshd[21069]: Invalid user secretar from 117.240.172.19 port 55335
May 28 06:00:01 inter-technics sshd[21069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.240.172.19
May 28 06:00:01 inter-technics sshd[21069]: Invalid user secretar from 117.240.172.19 port 55335
May 28 06:00:03 inter-technics sshd[21069]: Failed password for invalid user secretar from 117.240.172.19 port 55335 ssh2
May 28 06:01:21 inter-technics sshd[21287]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.240.172.19  user=root
May 28 06:01:23 inter-technics sshd[21287]: Failed password for root from 117.240.172.19 port 36031 ssh2
...
2020-05-28 15:37:58
92.77.255.160 attackspambots
SSH login attempts.
2020-05-28 15:47:28
36.111.146.209 attackbots
Invalid user admin from 36.111.146.209 port 55166
2020-05-28 15:59:28
140.246.155.37 attack
SSH login attempts.
2020-05-28 15:33:30
54.38.187.5 attackspambots
$f2bV_matches
2020-05-28 15:44:48
210.74.11.97 attackspam
SSH login attempts.
2020-05-28 15:36:34
223.100.7.112 attackspambots
May 28 04:06:25 ws24vmsma01 sshd[139231]: Failed password for root from 223.100.7.112 port 33460 ssh2
...
2020-05-28 15:49:47
200.89.159.190 attackspambots
SSH login attempts.
2020-05-28 15:34:05
27.124.39.148 attackbots
Invalid user hplip from 27.124.39.148 port 59584
2020-05-28 15:40:59
104.225.149.55 attackspam
(sshd) Failed SSH login from 104.225.149.55 (US/United States/104.225.149.55.16clouds.com): 5 in the last 3600 secs
2020-05-28 15:31:56
180.76.121.28 attackspambots
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-05-28 15:51:20
103.120.227.88 attackbots
Invalid user micstars from 103.120.227.88 port 60132
2020-05-28 15:58:49
139.59.249.255 attackbots
May 28 09:48:18 eventyay sshd[32444]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.249.255
May 28 09:48:20 eventyay sshd[32444]: Failed password for invalid user stouffer from 139.59.249.255 port 20999 ssh2
May 28 09:52:37 eventyay sshd[32618]: Failed password for root from 139.59.249.255 port 28440 ssh2
...
2020-05-28 15:54:50
113.134.211.242 attackspambots
$f2bV_matches
2020-05-28 15:36:16

Recently Reported IPs

157.17.126.125 196.84.110.99 131.200.31.35 164.181.122.139
120.64.131.100 90.139.230.206 153.132.212.134 90.171.233.160
197.58.159.187 78.2.82.249 29.155.255.28 65.186.107.253
245.201.166.130 68.232.149.128 70.203.9.154 141.141.188.145
71.94.56.170 103.153.110.198 155.128.90.47 148.237.15.112