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

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

;; QUESTION SECTION:
;214.83.204.85.			IN	A

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

;; Query time: 114 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 18 02:47:17 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 85.204.83.214.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 214.83.204.85.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
31.163.52.133 attackbotsspam
Chat Spam
2019-10-27 12:43:45
138.68.242.220 attackbots
Invalid user ax400 from 138.68.242.220 port 38916
2019-10-27 13:03:04
184.75.211.140 attackspambots
(From david@davidmelnichuk.com) I saw this form on your site, and I submitted it. Now you’re reading this, so that means it works. Awesome! But that’s not enough.

For this form to make your business money, people have to respond to you when you reach out to them. Don’t you hate it when they never answer, or by the time you get back to them, they already decided to do business with your competitor? This ends today. I made a free video tutorial that shows you how to setup an immediate SMS message and email response to go out to every lead that submits this form so you can start a conversation while they are still thinking about your services.

If you contact a lead in the first 2 minutes after they’ve submitted this web form, they’re 100x more likely to respond and 78% of customers buy from the first responder. Check out my free tutorial on how to set this up: http://bit.ly/how-to-setup-an-automatic-sms-and-email

What’s the catch? Nothing. My step-by-step training here is completely free and will show y
2019-10-27 13:22:34
222.186.180.9 attackbots
Oct 27 01:16:15 TORMINT sshd\[14140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9  user=root
Oct 27 01:16:17 TORMINT sshd\[14140\]: Failed password for root from 222.186.180.9 port 52390 ssh2
Oct 27 01:16:30 TORMINT sshd\[14140\]: Failed password for root from 222.186.180.9 port 52390 ssh2
...
2019-10-27 13:25:08
94.191.31.53 attack
Oct 27 04:56:27 mars sshd\[27342\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.31.53  user=root
Oct 27 04:56:29 mars sshd\[27342\]: Failed password for root from 94.191.31.53 port 53564 ssh2
Oct 27 04:56:32 mars sshd\[27344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.31.53  user=root
...
2019-10-27 13:24:50
211.23.61.194 attackbotsspam
Oct 27 06:20:56 pkdns2 sshd\[46393\]: Invalid user zhouh from 211.23.61.194Oct 27 06:20:57 pkdns2 sshd\[46393\]: Failed password for invalid user zhouh from 211.23.61.194 port 49816 ssh2Oct 27 06:24:29 pkdns2 sshd\[46521\]: Invalid user user3 from 211.23.61.194Oct 27 06:24:31 pkdns2 sshd\[46521\]: Failed password for invalid user user3 from 211.23.61.194 port 58370 ssh2Oct 27 06:28:08 pkdns2 sshd\[46733\]: Invalid user sdnmuser from 211.23.61.194Oct 27 06:28:10 pkdns2 sshd\[46733\]: Failed password for invalid user sdnmuser from 211.23.61.194 port 38692 ssh2
...
2019-10-27 12:51:19
49.88.112.72 attackspam
5x Failed Password
2019-10-27 13:10:53
167.71.215.72 attack
Oct 27 04:34:22 localhost sshd\[110867\]: Invalid user samir from 167.71.215.72 port 21989
Oct 27 04:34:22 localhost sshd\[110867\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.215.72
Oct 27 04:34:24 localhost sshd\[110867\]: Failed password for invalid user samir from 167.71.215.72 port 21989 ssh2
Oct 27 04:38:27 localhost sshd\[110983\]: Invalid user samir from 167.71.215.72 port 59907
Oct 27 04:38:27 localhost sshd\[110983\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.215.72
...
2019-10-27 12:47:43
132.248.88.73 attack
Oct 27 04:38:55 localhost sshd\[110999\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.248.88.73  user=root
Oct 27 04:38:56 localhost sshd\[110999\]: Failed password for root from 132.248.88.73 port 38701 ssh2
Oct 27 04:43:44 localhost sshd\[111209\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.248.88.73  user=root
Oct 27 04:43:46 localhost sshd\[111209\]: Failed password for root from 132.248.88.73 port 58994 ssh2
Oct 27 04:48:22 localhost sshd\[111317\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.248.88.73  user=uucp
...
2019-10-27 12:58:03
13.235.150.69 attack
2019-10-27T04:40:13.202508abusebot-7.cloudsearch.cf sshd\[27869\]: Invalid user liverpoo from 13.235.150.69 port 48570
2019-10-27 13:19:05
43.228.117.222 attackbotsspam
2019-10-27T03:57:41.919544abusebot-5.cloudsearch.cf sshd\[27451\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.228.117.222  user=root
2019-10-27 12:47:04
124.43.130.47 attack
2019-10-27T04:28:27.685468abusebot-7.cloudsearch.cf sshd\[27822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.43.130.47  user=root
2019-10-27 12:58:38
157.245.166.183 attackbots
157.245.166.183 - - [27/Oct/2019:04:56:32 +0100] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157.245.166.183 - - [27/Oct/2019:04:56:33 +0100] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157.245.166.183 - - [27/Oct/2019:04:56:33 +0100] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157.245.166.183 - - [27/Oct/2019:04:56:33 +0100] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157.245.166.183 - - [27/Oct/2019:04:56:33 +0100] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157.245.166.183 - - [27/Oct/2019:04:56:35 +0100] "POST /wp-login.php HTTP/1.1" 200 1486 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
157
2019-10-27 13:22:48
121.7.127.92 attack
Oct 27 05:56:59 www sshd\[89644\]: Invalid user ta from 121.7.127.92
Oct 27 05:56:59 www sshd\[89644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.7.127.92
Oct 27 05:57:01 www sshd\[89644\]: Failed password for invalid user ta from 121.7.127.92 port 50953 ssh2
...
2019-10-27 13:06:23
195.140.169.190 attackspam
RDP Brute-Force (Grieskirchen RZ2)
2019-10-27 13:16:19

Recently Reported IPs

216.27.86.191 214.203.66.45 212.96.170.49 212.18.231.203
77.221.31.0 62.144.126.199 182.26.17.175 112.155.252.143
232.228.245.16 225.76.41.60 210.155.253.187 209.85.223.76
209.136.28.2 206.238.137.55 206.22.26.23 205.201.188.233
9.202.180.246 203.223.10.194 202.19.170.92 66.249.229.110