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

;; QUESTION SECTION:
;140.1.221.21.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 03 16:10:49 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 21.221.1.140.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 21.221.1.140.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.76.158.224 attack
Feb 23 06:38:34 dedicated sshd[20391]: Failed password for invalid user juan from 180.76.158.224 port 33372 ssh2
Feb 23 06:38:32 dedicated sshd[20391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.158.224 
Feb 23 06:38:32 dedicated sshd[20391]: Invalid user juan from 180.76.158.224 port 33372
Feb 23 06:38:34 dedicated sshd[20391]: Failed password for invalid user juan from 180.76.158.224 port 33372 ssh2
Feb 23 06:43:21 dedicated sshd[21270]: Invalid user server from 180.76.158.224 port 51758
2020-02-23 17:56:37
103.146.36.10 attackspam
Unauthorized connection attempt detected from IP address 103.146.36.10 to port 23 [J]
2020-02-23 17:33:08
212.21.13.101 attackbots
Unauthorized connection attempt detected from IP address 212.21.13.101 to port 8080 [J]
2020-02-23 17:51:28
116.88.106.238 attackbotsspam
Unauthorized connection attempt detected from IP address 116.88.106.238 to port 5555 [J]
2020-02-23 17:29:59
114.33.235.109 attackspambots
Unauthorized connection attempt detected from IP address 114.33.235.109 to port 23 [J]
2020-02-23 18:03:51
123.204.88.119 attackspam
Unauthorized connection attempt detected from IP address 123.204.88.119 to port 26 [J]
2020-02-23 18:01:13
114.32.1.167 attackbots
Unauthorized connection attempt detected from IP address 114.32.1.167 to port 23 [J]
2020-02-23 18:04:15
61.227.77.99 attackbotsspam
Unauthorized connection attempt detected from IP address 61.227.77.99 to port 23 [J]
2020-02-23 18:11:34
99.243.16.225 attackspam
Unauthorized connection attempt detected from IP address 99.243.16.225 to port 4567 [J]
2020-02-23 18:06:56
118.100.177.5 attack
Unauthorized connection attempt detected from IP address 118.100.177.5 to port 8000 [J]
2020-02-23 17:28:35
103.66.10.12 attackspam
Unauthorized connection attempt detected from IP address 103.66.10.12 to port 23 [J]
2020-02-23 17:34:34
218.73.110.113 attack
Unauthorized connection attempt detected from IP address 218.73.110.113 to port 3389 [J]
2020-02-23 17:50:30
179.54.111.10 attackbots
Unauthorized connection attempt detected from IP address 179.54.111.10 to port 23 [J]
2020-02-23 17:57:15
111.92.6.57 attackspam
Unauthorized connection attempt detected from IP address 111.92.6.57 to port 23 [J]
2020-02-23 17:32:17
14.43.198.13 attackspam
Unauthorized connection attempt detected from IP address 14.43.198.13 to port 81 [J]
2020-02-23 17:45:50

Recently Reported IPs

218.75.160.237 165.117.175.149 226.89.149.253 57.231.35.0
143.36.177.193 93.219.69.70 193.228.13.23 56.164.74.169
37.184.26.200 155.133.46.195 37.131.212.106 64.252.234.173
60.193.129.237 67.9.232.28 49.130.226.29 126.128.93.52
226.105.255.189 165.128.4.243 92.181.221.202 31.49.213.4