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

;; QUESTION SECTION:
;100.21.38.44.			IN	A

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

;; Query time: 46 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 31 19:58:35 CST 2025
;; MSG SIZE  rcvd: 105
Host info
44.38.21.100.in-addr.arpa domain name pointer ec2-100-21-38-44.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.38.21.100.in-addr.arpa	name = ec2-100-21-38-44.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.185.158.195 attack
Port scan and direct access per IP instead of hostname
2019-07-28 15:39:26
51.159.28.59 attackbotsspam
leo_www
2019-07-28 15:11:14
177.44.26.40 attack
Jul 27 21:07:52 web1 postfix/smtpd[27874]: warning: unknown[177.44.26.40]: SASL PLAIN authentication failed: authentication failure
...
2019-07-28 15:43:41
106.13.83.150 attack
Jul 28 03:29:51 animalibera sshd[31101]: Invalid user yuyang220502610117141 from 106.13.83.150 port 49920
...
2019-07-28 15:17:49
101.109.83.140 attackspam
Automatic report - Banned IP Access
2019-07-28 15:56:17
177.125.44.195 attack
Port scan and direct access per IP instead of hostname
2019-07-28 15:42:05
169.197.108.38 attackbotsspam
Port scan and direct access per IP instead of hostname
2019-07-28 15:58:36
174.97.237.86 attackbotsspam
POST / HTTP/1.1
2019-07-28 15:53:15
61.69.254.46 attackbotsspam
Jul 28 03:02:08 mail sshd\[28862\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.69.254.46  user=root
Jul 28 03:02:10 mail sshd\[28862\]: Failed password for root from 61.69.254.46 port 58266 ssh2
Jul 28 03:08:06 mail sshd\[28883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.69.254.46  user=root
...
2019-07-28 15:28:45
188.136.188.21 attackbotsspam
Port scan and direct access per IP instead of hostname
2019-07-28 15:08:45
95.32.44.96 attack
port scan and connect, tcp 23 (telnet)
2019-07-28 15:28:19
103.115.227.2 attack
Jul 28 01:08:01 *** sshd[17893]: User root from 103.115.227.2 not allowed because not listed in AllowUsers
2019-07-28 15:32:52
185.142.236.34 attackbotsspam
28.07.2019 05:57:57 Connection to port 1723 blocked by firewall
2019-07-28 15:16:19
196.1.99.12 attack
Invalid user setup from 196.1.99.12 port 48617
2019-07-28 15:13:54
203.253.145.158 attackspam
Invalid user !@\#$%\^ from 203.253.145.158 port 55128
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.253.145.158
Failed password for invalid user !@\#$%\^ from 203.253.145.158 port 55128 ssh2
Invalid user ferari from 203.253.145.158 port 50246
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.253.145.158
2019-07-28 15:25:47

Recently Reported IPs

38.197.67.161 164.233.119.224 35.97.155.46 251.20.21.175
147.14.98.68 67.9.149.146 253.109.67.94 225.57.236.129
214.210.108.112 80.85.205.1 40.4.135.255 150.244.126.7
157.175.68.195 249.131.245.195 39.26.8.8 176.243.1.176
203.95.40.133 189.68.102.173 86.148.247.26 207.100.186.83