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

;; QUESTION SECTION:
;52.201.83.214.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 08 21:42:17 CST 2025
;; MSG SIZE  rcvd: 106
Host info
214.83.201.52.in-addr.arpa domain name pointer ec2-52-201-83-214.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
214.83.201.52.in-addr.arpa	name = ec2-52-201-83-214.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
140.143.22.200 attack
2019-11-19T15:43:51.085094shield sshd\[5491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.22.200  user=root
2019-11-19T15:43:53.255892shield sshd\[5491\]: Failed password for root from 140.143.22.200 port 34242 ssh2
2019-11-19T15:49:56.558316shield sshd\[6838\]: Invalid user bergsvendsen from 140.143.22.200 port 40912
2019-11-19T15:49:56.563263shield sshd\[6838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.22.200
2019-11-19T15:49:58.507445shield sshd\[6838\]: Failed password for invalid user bergsvendsen from 140.143.22.200 port 40912 ssh2
2019-11-19 23:52:35
151.53.216.115 attackbotsspam
Automatic report - Port Scan Attack
2019-11-19 23:25:14
138.68.165.102 attack
Nov 19 09:16:13 linuxvps sshd\[50929\]: Invalid user lafay from 138.68.165.102
Nov 19 09:16:13 linuxvps sshd\[50929\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.165.102
Nov 19 09:16:15 linuxvps sshd\[50929\]: Failed password for invalid user lafay from 138.68.165.102 port 34760 ssh2
Nov 19 09:20:19 linuxvps sshd\[53495\]: Invalid user server from 138.68.165.102
Nov 19 09:20:19 linuxvps sshd\[53495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.165.102
2019-11-19 23:32:11
105.226.131.30 attack
Nov 19 13:57:10 mxgate1 postfix/postscreen[7608]: CONNECT from [105.226.131.30]:11098 to [176.31.12.44]:25
Nov 19 13:57:10 mxgate1 postfix/dnsblog[7611]: addr 105.226.131.30 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 19 13:57:10 mxgate1 postfix/dnsblog[7611]: addr 105.226.131.30 listed by domain zen.spamhaus.org as 127.0.0.11
Nov 19 13:57:10 mxgate1 postfix/dnsblog[7610]: addr 105.226.131.30 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 19 13:57:16 mxgate1 postfix/postscreen[7608]: DNSBL rank 3 for [105.226.131.30]:11098
Nov x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=105.226.131.30
2019-11-19 23:31:11
199.195.252.213 attackspambots
2019-11-19T14:14:48.872029hub.schaetter.us sshd\[18193\]: Invalid user relyea from 199.195.252.213 port 39698
2019-11-19T14:14:48.888745hub.schaetter.us sshd\[18193\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.252.213
2019-11-19T14:14:50.227108hub.schaetter.us sshd\[18193\]: Failed password for invalid user relyea from 199.195.252.213 port 39698 ssh2
2019-11-19T14:18:23.758605hub.schaetter.us sshd\[18198\]: Invalid user www-data from 199.195.252.213 port 48556
2019-11-19T14:18:23.766563hub.schaetter.us sshd\[18198\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.252.213
...
2019-11-19 23:25:36
92.118.160.5 attack
Fail2Ban Ban Triggered
2019-11-19 23:36:29
210.217.24.226 attackspambots
2019-11-19T15:42:24.893554abusebot-7.cloudsearch.cf sshd\[21944\]: Invalid user upload from 210.217.24.226 port 57676
2019-11-19 23:44:25
159.203.201.42 attack
" "
2019-11-20 00:04:45
218.23.104.250 attackspam
Nov 19 15:48:29 server sshd\[12974\]: Invalid user admin from 218.23.104.250
Nov 19 15:48:29 server sshd\[12974\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.23.104.250 
Nov 19 15:48:31 server sshd\[12974\]: Failed password for invalid user admin from 218.23.104.250 port 57002 ssh2
Nov 19 16:02:35 server sshd\[16571\]: Invalid user backup from 218.23.104.250
Nov 19 16:02:35 server sshd\[16571\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.23.104.250 
...
2019-11-19 23:38:39
222.82.237.238 attackbotsspam
Nov 19 08:02:39 Tower sshd[14360]: Connection from 222.82.237.238 port 60630 on 192.168.10.220 port 22
Nov 19 08:02:47 Tower sshd[14360]: Invalid user smieciu from 222.82.237.238 port 60630
Nov 19 08:02:47 Tower sshd[14360]: error: Could not get shadow information for NOUSER
Nov 19 08:02:47 Tower sshd[14360]: Failed password for invalid user smieciu from 222.82.237.238 port 60630 ssh2
Nov 19 08:02:48 Tower sshd[14360]: Received disconnect from 222.82.237.238 port 60630:11: Bye Bye [preauth]
Nov 19 08:02:48 Tower sshd[14360]: Disconnected from invalid user smieciu 222.82.237.238 port 60630 [preauth]
2019-11-19 23:28:58
222.186.175.202 attackbotsspam
[ssh] SSH attack
2019-11-19 23:50:18
139.59.40.233 attackbots
139.59.40.233 - - \[19/Nov/2019:13:43:05 +0000\] "POST /wp-login.php HTTP/1.1" 200 4358 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
139.59.40.233 - - \[19/Nov/2019:13:43:06 +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"
...
2019-11-20 00:06:10
128.201.207.58 attack
Brute force SMTP login attempts.
2019-11-19 23:39:40
223.247.223.194 attackspam
SSH Brute-Force attacks
2019-11-19 23:26:47
222.186.180.17 attackbotsspam
Nov 18 03:41:15 microserver sshd[22625]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.17  user=root
Nov 18 03:41:17 microserver sshd[22625]: Failed password for root from 222.186.180.17 port 20532 ssh2
Nov 18 03:41:20 microserver sshd[22625]: Failed password for root from 222.186.180.17 port 20532 ssh2
Nov 18 03:41:24 microserver sshd[22625]: Failed password for root from 222.186.180.17 port 20532 ssh2
Nov 18 06:30:37 microserver sshd[44259]: Failed none for root from 222.186.180.17 port 36016 ssh2
Nov 18 06:30:38 microserver sshd[44259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.17  user=root
Nov 18 06:30:40 microserver sshd[44259]: Failed password for root from 222.186.180.17 port 36016 ssh2
Nov 18 06:30:43 microserver sshd[44259]: Failed password for root from 222.186.180.17 port 36016 ssh2
Nov 18 06:30:46 microserver sshd[44259]: Failed password for root from 222.186.180.17 port 36016 ssh2
Nov
2019-11-19 23:27:08

Recently Reported IPs

247.125.122.129 6.32.83.62 235.167.146.242 90.82.70.5
223.5.191.247 46.223.229.247 170.238.102.55 179.233.56.104
70.38.212.228 41.27.39.244 146.131.97.237 55.179.85.96
62.116.194.86 53.220.202.205 12.95.76.74 142.197.154.20
73.236.125.74 86.199.49.117 244.97.82.203 39.86.58.97