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: Norway

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

;; QUESTION SECTION:
;81.166.224.221.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 09:15:30 CST 2022
;; MSG SIZE  rcvd: 107
Host info
221.224.166.81.in-addr.arpa domain name pointer 221.81-166-224.customer.lyse.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
221.224.166.81.in-addr.arpa	name = 221.81-166-224.customer.lyse.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.51.44.237 attackspambots
20/1/19@23:51:15: FAIL: Alarm-Network address from=106.51.44.237
20/1/19@23:51:15: FAIL: Alarm-Network address from=106.51.44.237
...
2020-01-20 17:43:09
175.209.238.23 attack
Unauthorized connection attempt detected from IP address 175.209.238.23 to port 23 [J]
2020-01-20 17:53:38
142.93.148.51 attack
Unauthorized connection attempt detected from IP address 142.93.148.51 to port 2220 [J]
2020-01-20 17:32:33
124.156.50.89 attackspambots
Unauthorized connection attempt detected from IP address 124.156.50.89 to port 30 [J]
2020-01-20 17:56:07
116.3.213.203 attack
unauthorized connection attempt
2020-01-20 17:32:16
103.203.173.122 attack
Unauthorized connection attempt detected from IP address 103.203.173.122 to port 82 [J]
2020-01-20 17:58:24
14.237.16.119 attackspambots
Unauthorized connection attempt detected from IP address 14.237.16.119 to port 445
2020-01-20 17:48:01
91.234.194.246 attack
91.234.194.246 - - [20/Jan/2020:04:51:35 +0000] "POST /wp-login.php HTTP/1.1" 200 6409 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
91.234.194.246 - - [20/Jan/2020:04:51:36 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-20 17:35:50
162.243.165.39 attack
Jan 20 09:50:34 vpn01 sshd[15952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.165.39
Jan 20 09:50:36 vpn01 sshd[15952]: Failed password for invalid user ftpuser from 162.243.165.39 port 42380 ssh2
...
2020-01-20 17:42:48
180.191.216.20 attackbotsspam
20/1/19@23:51:07: FAIL: Alarm-Network address from=180.191.216.20
20/1/19@23:51:07: FAIL: Alarm-Network address from=180.191.216.20
...
2020-01-20 17:47:34
61.148.196.114 attackbotsspam
'IP reached maximum auth failures for a one day block'
2020-01-20 17:33:19
165.227.197.15 attackspam
Automatic report - XMLRPC Attack
2020-01-20 17:18:25
134.209.243.85 attackbots
Unauthorized connection attempt detected from IP address 134.209.243.85 to port 2220 [J]
2020-01-20 17:31:55
171.34.177.174 attack
Unauthorized connection attempt detected from IP address 171.34.177.174 to port 80 [J]
2020-01-20 17:54:27
182.61.54.106 attackspambots
Unauthorized connection attempt detected from IP address 182.61.54.106 to port 2220 [J]
2020-01-20 17:36:20

Recently Reported IPs

81.171.28.44 81.174.12.143 81.170.176.53 81.169.235.131
81.174.12.60 81.177.251.53 81.182.17.236 81.182.85.193
81.182.40.120 81.19.214.5 81.19.223.222 81.190.170.113
81.196.73.239 81.196.72.213 81.196.73.234 81.196.93.209
81.198.142.177 81.198.222.20 81.198.229.122 81.198.202.5