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

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

;; QUESTION SECTION:
;114.221.85.82.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 14:59:57 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 82.85.221.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 82.85.221.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
82.221.131.102 attackspambots
search WP for "forgotten" wp-config backups ... checks for > 50 possible backupfile names
2019-06-25 20:40:23
201.111.162.11 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-06-25 20:36:31
178.128.152.46 attackspambots
wp-login.php
2019-06-25 20:12:32
182.18.171.148 attack
Invalid user user from 182.18.171.148 port 33686
2019-06-25 20:09:10
182.61.33.47 attackbots
Jun 25 13:43:33 lnxweb62 sshd[16222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.33.47
Jun 25 13:43:33 lnxweb62 sshd[16222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.33.47
2019-06-25 20:14:52
139.99.40.27 attackbotsspam
Invalid user steam from 139.99.40.27 port 59062
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.40.27
Failed password for invalid user steam from 139.99.40.27 port 59062 ssh2
Invalid user remi_ext from 139.99.40.27 port 39134
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.40.27
2019-06-25 20:26:43
183.101.208.41 attackbotsspam
Jun 25 13:42:19 localhost sshd\[10612\]: Invalid user control from 183.101.208.41
Jun 25 13:42:19 localhost sshd\[10612\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.101.208.41
Jun 25 13:42:21 localhost sshd\[10612\]: Failed password for invalid user control from 183.101.208.41 port 38590 ssh2
Jun 25 13:45:17 localhost sshd\[10863\]: Invalid user dn from 183.101.208.41
Jun 25 13:45:17 localhost sshd\[10863\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.101.208.41
...
2019-06-25 20:04:22
183.88.224.175 attackbots
$f2bV_matches
2019-06-25 20:11:41
154.214.115.108 attack
2019-06-24T10:35:07.113370stt-1.[munged] kernel: [5418532.826481] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:aa:c1:08:00 SRC=154.214.115.108 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=113 ID=256 PROTO=TCP SPT=40296 DPT=3389 WINDOW=16384 RES=0x00 SYN URGP=0 
2019-06-24T14:04:06.212314stt-1.[munged] kernel: [5431071.890312] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:a8:41:08:00 SRC=154.214.115.108 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=113 ID=256 PROTO=TCP SPT=43256 DPT=3389 WINDOW=16384 RES=0x00 SYN URGP=0 
2019-06-25T02:55:26.637382stt-1.[munged] kernel: [5477352.186711] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:97:36:58:84:78:ac:57:aa:c1:08:00 SRC=154.214.115.108 DST=[mungedIP1] LEN=40 TOS=0x00 PREC=0x00 TTL=113 ID=256 PROTO=TCP SPT=12476 DPT=3389 WINDOW=16384 RES=0x00 SYN URGP=0
2019-06-25 20:40:53
106.75.85.117 attackbots
Automatic report - Web App Attack
2019-06-25 20:41:43
58.65.164.10 attackspambots
SSH Brute-Force attacks
2019-06-25 20:10:47
120.138.110.214 attackspambots
Unauthorized connection attempt from IP address 120.138.110.214 on Port 445(SMB)
2019-06-25 20:28:28
148.72.213.224 attackbotsspam
2019-06-25T09:54:48.725550lon01.zurich-datacenter.net sshd\[11062\]: Invalid user nang from 148.72.213.224 port 39274
2019-06-25T09:54:48.732305lon01.zurich-datacenter.net sshd\[11062\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-148-72-213-224.ip.secureserver.net
2019-06-25T09:54:50.729654lon01.zurich-datacenter.net sshd\[11062\]: Failed password for invalid user nang from 148.72.213.224 port 39274 ssh2
2019-06-25T09:57:56.450798lon01.zurich-datacenter.net sshd\[11138\]: Invalid user wan from 148.72.213.224 port 41126
2019-06-25T09:57:56.456247lon01.zurich-datacenter.net sshd\[11138\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-148-72-213-224.ip.secureserver.net
...
2019-06-25 20:24:57
133.130.88.87 attack
Jun 25 08:56:07 vpn01 sshd\[6613\]: Invalid user deploy from 133.130.88.87
Jun 25 08:56:07 vpn01 sshd\[6613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.130.88.87
Jun 25 08:56:09 vpn01 sshd\[6613\]: Failed password for invalid user deploy from 133.130.88.87 port 33327 ssh2
2019-06-25 20:27:53
88.13.126.174 attackbotsspam
SSH Bruteforce
2019-06-25 19:53:54

Recently Reported IPs

114.221.85.55 114.221.86.108 114.221.86.145 114.221.86.191
114.221.86.140 114.221.86.210 114.221.86.24 114.221.86.36
114.221.86.68 114.221.86.72 114.221.93.211 114.221.86.4
114.221.86.216 114.222.106.214 113.53.14.231 113.53.14.243
113.53.14.59 114.222.247.97 114.222.247.41 114.222.42.123