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

;; QUESTION SECTION:
;81.222.143.21.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 19 19:10:50 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 21.143.222.81.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.143.222.81.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
93.49.11.206 attack
Apr 21 23:58:59 DAAP sshd[18646]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.49.11.206  user=root
Apr 21 23:59:01 DAAP sshd[18646]: Failed password for root from 93.49.11.206 port 33401 ssh2
Apr 22 00:00:26 DAAP sshd[18694]: Invalid user o from 93.49.11.206 port 39212
Apr 22 00:00:26 DAAP sshd[18694]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.49.11.206
Apr 22 00:00:26 DAAP sshd[18694]: Invalid user o from 93.49.11.206 port 39212
Apr 22 00:00:29 DAAP sshd[18694]: Failed password for invalid user o from 93.49.11.206 port 39212 ssh2
...
2020-04-22 06:45:17
139.199.0.84 attack
Invalid user teamspeak from 139.199.0.84 port 31320
2020-04-22 06:46:36
212.100.155.154 attack
Invalid user admin01 from 212.100.155.154 port 48054
2020-04-22 06:15:06
43.243.168.63 attack
" "
2020-04-22 06:47:04
114.4.227.194 attack
Invalid user test from 114.4.227.194 port 56024
2020-04-22 06:41:54
110.80.142.84 attack
Apr 21 18:53:46: Invalid user git1 from 110.80.142.84 port 49968
2020-04-22 06:43:19
209.17.96.218 attackbots
Apr 21 21:48:43 debian-2gb-nbg1-2 kernel: \[9757479.963525\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=209.17.96.218 DST=195.201.40.59 LEN=44 TOS=0x08 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=58304 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0
2020-04-22 06:14:39
106.12.137.1 attack
invalid login attempt (it)
2020-04-22 06:36:07
79.136.70.159 attackbots
Apr 21 03:35:13 : SSH login attempts with invalid user
2020-04-22 06:35:55
49.233.88.50 attack
Invalid user dx from 49.233.88.50 port 47692
2020-04-22 06:23:21
34.80.55.211 attack
Apr 21 23:16:39 haigwepa sshd[12208]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.80.55.211 
Apr 21 23:16:40 haigwepa sshd[12208]: Failed password for invalid user yw from 34.80.55.211 port 35832 ssh2
...
2020-04-22 06:36:40
41.65.181.155 attackbotsspam
Invalid user yy from 41.65.181.155 port 56962
2020-04-22 06:38:12
139.186.4.114 attackspam
Invalid user cr from 139.186.4.114 port 53262
2020-04-22 06:16:07
140.86.12.31 attackbotsspam
SSH Invalid Login
2020-04-22 06:44:50
200.119.112.204 attackbotsspam
DATE:2020-04-21 23:18:39, IP:200.119.112.204, PORT:ssh SSH brute force auth (docker-dc)
2020-04-22 06:38:36

Recently Reported IPs

101.93.107.110 120.110.35.61 115.133.125.168 124.231.60.235
236.176.211.92 59.95.109.57 54.219.180.115 218.150.81.39
180.137.5.77 66.166.192.20 230.187.49.95 100.61.253.106
89.64.201.152 45.75.231.145 228.111.28.208 190.87.111.99
226.68.5.40 158.104.239.173 33.137.186.44 209.35.199.226