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

Region: Oregon

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

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

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

;; Query time: 118 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 09 07:29:37 CST 2020
;; MSG SIZE  rcvd: 117
Host info
228.104.34.52.in-addr.arpa domain name pointer ec2-52-34-104-228.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
228.104.34.52.in-addr.arpa	name = ec2-52-34-104-228.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.71.39.62 attackspambots
Jan 22 23:04:15 eddieflores sshd\[25176\]: Invalid user sharp from 167.71.39.62
Jan 22 23:04:15 eddieflores sshd\[25176\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.39.62
Jan 22 23:04:17 eddieflores sshd\[25176\]: Failed password for invalid user sharp from 167.71.39.62 port 42216 ssh2
Jan 22 23:07:18 eddieflores sshd\[25592\]: Invalid user vbox from 167.71.39.62
Jan 22 23:07:18 eddieflores sshd\[25592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.39.62
2020-01-23 17:07:21
118.126.111.108 attackspambots
"SSH brute force auth login attempt."
2020-01-23 16:52:40
62.234.206.12 attackbotsspam
"SSH brute force auth login attempt."
2020-01-23 16:53:58
51.158.113.194 attackspambots
"SSH brute force auth login attempt."
2020-01-23 16:59:57
76.233.226.106 attackspambots
"SSH brute force auth login attempt."
2020-01-23 16:39:59
112.220.85.26 attackspambots
"SSH brute force auth login attempt."
2020-01-23 17:05:57
115.233.218.204 attack
"SSH brute force auth login attempt."
2020-01-23 16:30:40
111.231.81.129 attackspambots
"SSH brute force auth login attempt."
2020-01-23 16:43:31
208.93.153.177 attackbotsspam
" "
2020-01-23 16:33:16
128.199.95.60 attackbotsspam
Unauthorized connection attempt detected from IP address 128.199.95.60 to port 2220 [J]
2020-01-23 17:08:29
79.137.33.20 attackbotsspam
Unauthorized connection attempt detected from IP address 79.137.33.20 to port 2220 [J]
2020-01-23 16:47:33
179.111.200.155 attack
"SSH brute force auth login attempt."
2020-01-23 16:52:20
181.231.78.192 attack
"SSH brute force auth login attempt."
2020-01-23 17:03:10
218.92.0.189 attackbotsspam
01/23/2020-03:54:06.164087 218.92.0.189 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-23 16:54:23
217.19.154.220 attack
"SSH brute force auth login attempt."
2020-01-23 16:46:04

Recently Reported IPs

174.109.86.177 82.36.235.1 171.226.100.209 63.42.119.146
123.74.121.179 41.30.76.55 175.210.20.22 182.100.101.73
99.7.207.128 92.111.184.31 99.236.125.95 91.192.173.88
117.143.178.184 218.255.211.19 60.166.88.244 84.149.185.38
68.148.43.187 129.32.241.45 48.170.112.115 2401:4900:1972:1cc8:f1d6:4d26:c8b9:d75c