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

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
01/11/2020-09:04:46.049938 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-11 16:17:38
attackbots
01/10/2020-23:14:31.286600 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-11 06:29:41
attack
01/10/2020-11:22:34.578308 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-10 18:35:31
attackspambots
01/09/2020-00:34:51.150642 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-09 07:36:57
attackbots
01/08/2020-06:27:54.232154 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-08 13:28:07
attackbots
01/07/2020-18:29:06.802362 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-08 01:43:34
attack
01/03/2020-22:54:36.763876 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-04 06:02:21
attackbots
01/03/2020-01:22:48.171374 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-03 08:28:54
attackbots
01/02/2020-21:02:36.456375 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-03 04:08:55
attack
01/02/2020-14:07:33.640138 52.34.195.239 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-02 21:12:26
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.34.195.239
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27816
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;52.34.195.239.			IN	A

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

;; Query time: 588 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 02 21:12:19 CST 2020
;; MSG SIZE  rcvd: 117
Host info
239.195.34.52.in-addr.arpa domain name pointer ec2-52-34-195-239.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
239.195.34.52.in-addr.arpa	name = ec2-52-34-195-239.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
1.22.124.94 attack
<6 unauthorized SSH connections
2020-05-28 16:13:05
36.111.146.209 attackbots
Invalid user admin from 36.111.146.209 port 55166
2020-05-28 15:59:28
49.233.169.219 attack
Invalid user student from 49.233.169.219 port 39527
2020-05-28 16:26:15
106.12.176.2 attack
Invalid user czdlpics from 106.12.176.2 port 56364
2020-05-28 16:06:20
213.230.75.160 attack
IP 213.230.75.160 attacked honeypot on port: 8080 at 5/28/2020 4:55:11 AM
2020-05-28 15:50:46
88.157.229.59 attackspambots
SSH login attempts.
2020-05-28 16:03:56
91.137.99.234 attackspambots
Invalid user sharra from 91.137.99.234 port 50766
2020-05-28 16:06:47
46.190.58.55 attackbotsspam
SSH login attempts.
2020-05-28 16:17:46
45.14.150.52 attackbotsspam
SIP/5060 Probe, BF, Hack -
2020-05-28 16:20:59
51.68.44.154 attackbotsspam
May 28 06:58:56 ip-172-31-62-245 sshd\[20610\]: Failed password for root from 51.68.44.154 port 33591 ssh2\
May 28 07:02:35 ip-172-31-62-245 sshd\[20643\]: Invalid user Server from 51.68.44.154\
May 28 07:02:37 ip-172-31-62-245 sshd\[20643\]: Failed password for invalid user Server from 51.68.44.154 port 36861 ssh2\
May 28 07:06:10 ip-172-31-62-245 sshd\[20664\]: Invalid user test from 51.68.44.154\
May 28 07:06:12 ip-172-31-62-245 sshd\[20664\]: Failed password for invalid user test from 51.68.44.154 port 40141 ssh2\
2020-05-28 16:12:38
111.230.226.124 attackbots
SSH login attempts.
2020-05-28 16:10:18
103.120.227.88 attackbots
Invalid user micstars from 103.120.227.88 port 60132
2020-05-28 15:58:49
148.56.63.236 attack
SSH login attempts.
2020-05-28 16:16:21
35.200.130.142 attack
May 28 01:37:04 server1 sshd\[25609\]: Failed password for invalid user uftp from 35.200.130.142 port 50280 ssh2
May 28 01:41:01 server1 sshd\[26824\]: Invalid user samsi from 35.200.130.142
May 28 01:41:01 server1 sshd\[26824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.200.130.142 
May 28 01:41:03 server1 sshd\[26824\]: Failed password for invalid user samsi from 35.200.130.142 port 48700 ssh2
May 28 01:45:09 server1 sshd\[28342\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.200.130.142  user=root
...
2020-05-28 15:56:07
182.61.44.177 attackspam
"fail2ban match"
2020-05-28 16:07:02

Recently Reported IPs

32.239.64.245 86.9.130.2 24.106.178.90 116.8.13.125
51.150.24.93 199.131.199.47 115.117.48.73 202.98.203.23
183.80.179.205 120.25.69.4 112.80.136.219 106.112.177.45
21.65.211.7 39.244.4.82 91.206.55.85 60.176.228.8
42.119.240.33 42.117.213.127 221.227.181.144 122.52.201.172