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

Region: Virginia

Country: United States

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
Dec  2 11:53:26 w sshd[18157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-34-207-242-222.compute-1.amazonaws.com  user=r.r
Dec  2 11:53:28 w sshd[18157]: Failed password for r.r from 34.207.242.222 port 47488 ssh2
Dec  2 11:53:28 w sshd[18157]: Received disconnect from 34.207.242.222: 11: Bye Bye [preauth]
Dec  2 12:02:35 w sshd[18214]: Invalid user rossa from 34.207.242.222
Dec  2 12:02:35 w sshd[18214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-34-207-242-222.compute-1.amazonaws.com 
Dec  2 12:02:36 w sshd[18214]: Failed password for invalid user rossa from 34.207.242.222 port 46734 ssh2
Dec  2 12:02:36 w sshd[18214]: Received disconnect from 34.207.242.222: 11: Bye Bye [preauth]
Dec  2 12:09:17 w sshd[18358]: Invalid user esvall from 34.207.242.222
Dec  2 12:09:17 w sshd[18358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-........
-------------------------------
2019-12-05 02:27:37
attackspam
Dec  2 11:53:26 w sshd[18157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-34-207-242-222.compute-1.amazonaws.com  user=r.r
Dec  2 11:53:28 w sshd[18157]: Failed password for r.r from 34.207.242.222 port 47488 ssh2
Dec  2 11:53:28 w sshd[18157]: Received disconnect from 34.207.242.222: 11: Bye Bye [preauth]
Dec  2 12:02:35 w sshd[18214]: Invalid user rossa from 34.207.242.222
Dec  2 12:02:35 w sshd[18214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-34-207-242-222.compute-1.amazonaws.com 
Dec  2 12:02:36 w sshd[18214]: Failed password for invalid user rossa from 34.207.242.222 port 46734 ssh2
Dec  2 12:02:36 w sshd[18214]: Received disconnect from 34.207.242.222: 11: Bye Bye [preauth]
Dec  2 12:09:17 w sshd[18358]: Invalid user esvall from 34.207.242.222
Dec  2 12:09:17 w sshd[18358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-........
-------------------------------
2019-12-04 04:07:09
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.207.242.222
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2246
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 107 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Dec 04 04:07:04 CST 2019
;; MSG SIZE  rcvd: 118
Host info
222.242.207.34.in-addr.arpa domain name pointer ec2-34-207-242-222.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
222.242.207.34.in-addr.arpa	name = ec2-34-207-242-222.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.51.12.44 attackbotsspam
Unauthorized connection attempt detected from IP address 49.51.12.44 to port 7144 [J]
2020-03-01 05:50:01
114.34.46.16 attackspam
Honeypot attack, port: 81, PTR: 114-34-46-16.HINET-IP.hinet.net.
2020-03-01 06:08:36
83.219.147.135 attackspam
Unauthorized connection attempt detected from IP address 83.219.147.135 to port 80 [J]
2020-03-01 05:48:06
116.48.140.149 attack
Unauthorized connection attempt detected from IP address 116.48.140.149 to port 4567 [J]
2020-03-01 06:07:58
37.255.195.59 attackbotsspam
Unauthorized connection attempt detected from IP address 37.255.195.59 to port 23 [J]
2020-03-01 05:51:33
218.32.45.84 attackspam
suspicious action Sat, 29 Feb 2020 12:06:18 -0300
2020-03-01 06:23:06
49.51.241.239 attackbotsspam
Unauthorized connection attempt detected from IP address 49.51.241.239 to port 5051 [J]
2020-03-01 05:49:40
211.75.193.168 attackspam
Unauthorized connection attempt from IP address 211.75.193.168 on Port 445(SMB)
2020-03-01 05:55:26
149.90.46.222 attackspam
Unauthorized connection attempt detected from IP address 149.90.46.222 to port 81 [J]
2020-03-01 06:04:19
85.221.236.106 attack
Unauthorized connection attempt detected from IP address 85.221.236.106 to port 23 [J]
2020-03-01 05:47:33
138.204.203.59 attack
Unauthorized connection attempt detected from IP address 138.204.203.59 to port 23 [J]
2020-03-01 06:04:40
61.6.200.26 attackspambots
Unauthorized connection attempt detected from IP address 61.6.200.26 to port 8080 [J]
2020-03-01 06:17:43
2.182.250.16 attackbots
Unauthorized connection attempt detected from IP address 2.182.250.16 to port 23 [J]
2020-03-01 05:52:30
84.55.21.228 attack
Unauthorized connection attempt detected from IP address 84.55.21.228 to port 5555 [J]
2020-03-01 06:14:33
5.219.184.165 attackspam
Unauthorized connection attempt detected from IP address 5.219.184.165 to port 23 [J]
2020-03-01 05:52:17

Recently Reported IPs

108.124.200.239 99.253.120.178 159.203.201.115 1.39.57.5
69.197.191.146 151.61.31.112 131.116.125.97 73.162.229.46
203.64.42.173 207.63.4.60 101.233.187.208 31.16.197.20
132.184.155.85 134.60.84.129 190.230.217.19 183.188.6.21
149.202.93.208 218.182.45.132 105.83.94.100 37.206.245.70