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:
IP Type Details Datetime
34.204.180.70 attackspambots
*Port Scan* detected from 34.204.180.70 (US/United States/ec2-34-204-180-70.compute-1.amazonaws.com). 11 hits in the last 250 seconds
2020-09-10 22:32:51
34.204.180.70 attack
*Port Scan* detected from 34.204.180.70 (US/United States/ec2-34-204-180-70.compute-1.amazonaws.com). 11 hits in the last 250 seconds
2020-09-10 04:52:36
34.204.178.0 attack
Invalid user hellen from 34.204.178.0 port 49846
2020-06-29 07:16:35
34.204.189.232 attackbots
Unauthorized connection attempt detected from IP address 34.204.189.232 to port 80 [T]
2020-06-12 16:52:53
34.204.165.169 attack
Address checking
2020-06-03 00:09:12
34.204.193.244 attack
Port scan on 1 port(s): 53
2020-04-14 13:22:57
34.204.193.243 attack
[portscan] Port scan
2020-04-01 03:22:44
34.204.196.170 attack
Port scan on 1 port(s): 53
2019-10-04 20:01:47
34.204.127.143 attackbotsspam
08/20/2019-22:11:14.081065 34.204.127.143 Protocol: 6 ET SCAN Potential SSH Scan
2019-08-21 10:11:43
34.204.197.113 attackbotsspam
by Amazon Technologies Inc.
2019-08-09 13:18:47
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.204.1.245
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50778
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;34.204.1.245.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 05:24:00 CST 2022
;; MSG SIZE  rcvd: 105
Host info
245.1.204.34.in-addr.arpa domain name pointer ec2-34-204-1-245.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
245.1.204.34.in-addr.arpa	name = ec2-34-204-1-245.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
167.99.65.138 attackspam
Invalid user lasick from 167.99.65.138 port 49876
2020-01-02 09:18:41
162.144.20.200 attackbots
01/02/2020-05:59:31.860087 162.144.20.200 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-02 13:07:10
37.170.83.42 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-01-02 09:12:37
5.196.29.194 attack
Invalid user evona from 5.196.29.194 port 48793
2020-01-02 09:13:58
200.87.233.68 attack
Jan  2 01:53:43 v22018076622670303 sshd\[20066\]: Invalid user clamav1 from 200.87.233.68 port 41915
Jan  2 01:53:43 v22018076622670303 sshd\[20066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.87.233.68
Jan  2 01:53:45 v22018076622670303 sshd\[20066\]: Failed password for invalid user clamav1 from 200.87.233.68 port 41915 ssh2
...
2020-01-02 08:55:11
165.22.103.237 attack
Jan  2 05:57:45 s1 sshd\[18967\]: User root from 165.22.103.237 not allowed because not listed in AllowUsers
Jan  2 05:57:45 s1 sshd\[18967\]: Failed password for invalid user root from 165.22.103.237 port 60698 ssh2
Jan  2 05:58:38 s1 sshd\[19020\]: Invalid user spyropoulos from 165.22.103.237 port 39502
Jan  2 05:58:38 s1 sshd\[19020\]: Failed password for invalid user spyropoulos from 165.22.103.237 port 39502 ssh2
Jan  2 05:59:31 s1 sshd\[19037\]: Invalid user admin from 165.22.103.237 port 46538
Jan  2 05:59:31 s1 sshd\[19037\]: Failed password for invalid user admin from 165.22.103.237 port 46538 ssh2
...
2020-01-02 13:06:52
116.196.82.52 attackspam
Unauthorized SSH login attempts
2020-01-02 09:03:39
114.237.188.186 attackbots
Jan  2 05:59:35 grey postfix/smtpd\[20073\]: NOQUEUE: reject: RCPT from unknown\[114.237.188.186\]: 554 5.7.1 Service unavailable\; Client host \[114.237.188.186\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[114.237.188.186\]\; from=\ to=\ proto=ESMTP helo=\
...
2020-01-02 13:04:19
114.113.146.57 attackspam
2020-01-02 dovecot_login authenticator failed for \(**REMOVED**\) \[114.113.146.57\]: 535 Incorrect authentication data \(set_id=nologin\)
2020-01-02 dovecot_login authenticator failed for \(**REMOVED**\) \[114.113.146.57\]: 535 Incorrect authentication data \(set_id=sales@**REMOVED**\)
2020-01-02 dovecot_login authenticator failed for \(**REMOVED**\) \[114.113.146.57\]: 535 Incorrect authentication data \(set_id=sales\)
2020-01-02 09:17:33
139.155.20.146 attackspambots
Jan  2 00:22:50 localhost sshd\[50892\]: Invalid user sajadior from 139.155.20.146 port 52084
Jan  2 00:22:50 localhost sshd\[50892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.20.146
Jan  2 00:22:53 localhost sshd\[50892\]: Failed password for invalid user sajadior from 139.155.20.146 port 52084 ssh2
Jan  2 00:26:54 localhost sshd\[50951\]: Invalid user mypassword from 139.155.20.146 port 49896
Jan  2 00:26:54 localhost sshd\[50951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.20.146
...
2020-01-02 09:22:03
190.94.18.2 attack
Jan  2 03:21:17 server sshd\[31843\]: Invalid user marino from 190.94.18.2
Jan  2 03:21:17 server sshd\[31843\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.94.18.2 
Jan  2 03:21:19 server sshd\[31843\]: Failed password for invalid user marino from 190.94.18.2 port 50228 ssh2
Jan  2 03:32:24 server sshd\[1372\]: Invalid user server1 from 190.94.18.2
Jan  2 03:32:24 server sshd\[1372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.94.18.2 
...
2020-01-02 09:18:11
106.75.122.168 attack
2020-01-01T23:44:35.191861pl1.awoom.xyz sshd[22824]: Invalid user schlichting from 106.75.122.168 port 34292
2020-01-01T23:44:35.197194pl1.awoom.xyz sshd[22824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.122.168
2020-01-01T23:44:35.191861pl1.awoom.xyz sshd[22824]: Invalid user schlichting from 106.75.122.168 port 34292
2020-01-01T23:44:37.185177pl1.awoom.xyz sshd[22824]: Failed password for invalid user schlichting from 106.75.122.168 port 34292 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=106.75.122.168
2020-01-02 09:00:59
80.211.29.222 attackspambots
80.211.29.222 - - [02/Jan/2020:05:59:32 +0100] "GET /awstats.pl?framename=mainright&output=refererpages HTTP/1.0" 404 280 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 YaBrowser/16.9.1.1131 Yowser/2.5 Safari/537.36"
2020-01-02 13:07:39
182.61.12.58 attackbotsspam
Jan  2 00:07:26 tuxlinux sshd[28829]: Invalid user 0. from 182.61.12.58 port 40554
Jan  2 00:07:26 tuxlinux sshd[28829]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.12.58 
Jan  2 00:07:26 tuxlinux sshd[28829]: Invalid user 0. from 182.61.12.58 port 40554
Jan  2 00:07:26 tuxlinux sshd[28829]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.12.58 
Jan  2 00:07:26 tuxlinux sshd[28829]: Invalid user 0. from 182.61.12.58 port 40554
Jan  2 00:07:26 tuxlinux sshd[28829]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.12.58 
Jan  2 00:07:29 tuxlinux sshd[28829]: Failed password for invalid user 0. from 182.61.12.58 port 40554 ssh2
...
2020-01-02 09:11:42
222.186.180.130 attack
Unauthorized connection attempt detected from IP address 222.186.180.130 to port 22
2020-01-02 08:56:40

Recently Reported IPs

194.150.140.117 189.190.159.33 46.198.241.192 191.176.145.97
89.44.181.171 103.130.141.98 60.248.52.28 102.191.145.19
175.214.73.138 83.225.35.196 27.68.173.57 192.206.45.49
1.246.223.6 185.93.73.81 197.49.148.5 94.232.40.229
156.223.68.90 115.239.48.218 172.253.120.101 122.136.60.211