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

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

;; QUESTION SECTION:
;104.21.30.232.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 20:28:52 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 232.30.21.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 232.30.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
155.186.168.193 attackbots
SSH Scan
2019-10-22 03:02:35
190.141.44.170 attackbotsspam
Fail2Ban Ban Triggered
2019-10-22 02:32:57
175.170.212.37 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/175.170.212.37/ 
 
 CN - 1H : (461)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4837 
 
 IP : 175.170.212.37 
 
 CIDR : 175.160.0.0/12 
 
 PREFIX COUNT : 1262 
 
 UNIQUE IP COUNT : 56665856 
 
 
 ATTACKS DETECTED ASN4837 :  
  1H - 6 
  3H - 23 
  6H - 54 
 12H - 106 
 24H - 161 
 
 DateTime : 2019-10-21 13:37:11 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-22 02:38:27
54.39.209.226 attackspambots
Honeypot attack, port: 23, PTR: PTR record not found
2019-10-22 02:34:29
94.102.51.11 attack
RDP_Brute_Force
2019-10-22 02:37:54
111.193.72.130 attackbotsspam
Oct 21 13:35:57 lnxweb62 sshd[10262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.193.72.130
Oct 21 13:35:57 lnxweb62 sshd[10263]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.193.72.130
Oct 21 13:35:59 lnxweb62 sshd[10262]: Failed password for invalid user pi from 111.193.72.130 port 38544 ssh2
Oct 21 13:35:59 lnxweb62 sshd[10263]: Failed password for invalid user pi from 111.193.72.130 port 38546 ssh2
2019-10-22 03:13:20
139.199.159.77 attackspam
Automatic report - Banned IP Access
2019-10-22 02:57:07
157.245.98.160 attackspam
2019-10-22T00:21:57.474740enmeeting.mahidol.ac.th sshd\[28826\]: User root from 157.245.98.160 not allowed because not listed in AllowUsers
2019-10-22T00:21:57.598602enmeeting.mahidol.ac.th sshd\[28826\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.98.160  user=root
2019-10-22T00:21:59.910382enmeeting.mahidol.ac.th sshd\[28826\]: Failed password for invalid user root from 157.245.98.160 port 48112 ssh2
...
2019-10-22 02:39:26
133.130.89.210 attackspam
Oct 21 15:42:59 vpn01 sshd[8381]: Failed password for root from 133.130.89.210 port 56232 ssh2
...
2019-10-22 02:51:39
54.36.182.244 attackbots
Oct 21 14:29:56 TORMINT sshd\[3069\]: Invalid user 00 from 54.36.182.244
Oct 21 14:29:56 TORMINT sshd\[3069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.182.244
Oct 21 14:29:58 TORMINT sshd\[3069\]: Failed password for invalid user 00 from 54.36.182.244 port 36814 ssh2
...
2019-10-22 02:51:14
185.153.199.2 attackbotsspam
10/21/2019-19:12:47.826574 185.153.199.2 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306
2019-10-22 02:39:07
103.76.252.6 attack
$f2bV_matches
2019-10-22 03:07:03
37.139.16.227 attack
Oct 21 17:18:17 vpn01 sshd[10136]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.139.16.227
Oct 21 17:18:19 vpn01 sshd[10136]: Failed password for invalid user saip from 37.139.16.227 port 41324 ssh2
...
2019-10-22 03:00:06
41.46.248.21 attack
Oct 21 13:35:59 tuxlinux sshd[13456]: Invalid user admin from 41.46.248.21 port 55950
Oct 21 13:35:59 tuxlinux sshd[13456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.46.248.21 
Oct 21 13:35:59 tuxlinux sshd[13456]: Invalid user admin from 41.46.248.21 port 55950
Oct 21 13:35:59 tuxlinux sshd[13456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.46.248.21 
Oct 21 13:35:59 tuxlinux sshd[13456]: Invalid user admin from 41.46.248.21 port 55950
Oct 21 13:35:59 tuxlinux sshd[13456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.46.248.21 
Oct 21 13:36:02 tuxlinux sshd[13456]: Failed password for invalid user admin from 41.46.248.21 port 55950 ssh2
...
2019-10-22 03:11:55
113.108.70.154 attack
Oct 21 20:53:17 andromeda postfix/smtpd\[9926\]: warning: unknown\[113.108.70.154\]: SASL LOGIN authentication failed: authentication failure
Oct 21 20:53:20 andromeda postfix/smtpd\[1830\]: warning: unknown\[113.108.70.154\]: SASL LOGIN authentication failed: authentication failure
Oct 21 20:53:23 andromeda postfix/smtpd\[1565\]: warning: unknown\[113.108.70.154\]: SASL LOGIN authentication failed: authentication failure
Oct 21 20:53:27 andromeda postfix/smtpd\[1565\]: warning: unknown\[113.108.70.154\]: SASL LOGIN authentication failed: authentication failure
Oct 21 20:53:33 andromeda postfix/smtpd\[8310\]: warning: unknown\[113.108.70.154\]: SASL LOGIN authentication failed: authentication failure
2019-10-22 03:06:30

Recently Reported IPs

104.21.30.230 104.21.30.238 104.21.30.239 104.21.30.24
79.164.106.150 104.21.30.243 5.204.151.215 104.21.30.246
104.21.30.248 104.21.30.25 104.21.30.252 15.125.129.83
104.21.30.26 104.21.30.3 104.21.30.31 104.21.30.32
104.21.30.34 104.21.30.38 104.21.30.42 104.21.30.44