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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.214.180.30
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10067
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 48 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 19 13:52:23 CST 2020
;; MSG SIZE  rcvd: 117
Host info
30.180.214.34.in-addr.arpa domain name pointer ec2-34-214-180-30.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
30.180.214.34.in-addr.arpa	name = ec2-34-214-180-30.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.188.147 attackbots
Dec 28 08:06:45 pi sshd\[12590\]: Invalid user admin from 106.13.188.147 port 33144
Dec 28 08:06:45 pi sshd\[12590\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.188.147
Dec 28 08:06:47 pi sshd\[12590\]: Failed password for invalid user admin from 106.13.188.147 port 33144 ssh2
Dec 28 08:10:33 pi sshd\[12788\]: Invalid user vannie from 106.13.188.147 port 60388
Dec 28 08:10:33 pi sshd\[12788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.188.147
...
2019-12-28 21:46:25
54.37.155.165 attackspambots
Dec 28 11:27:50 sshgateway sshd\[2545\]: Invalid user rcs from 54.37.155.165
Dec 28 11:27:50 sshgateway sshd\[2545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.ip-54-37-155.eu
Dec 28 11:27:52 sshgateway sshd\[2545\]: Failed password for invalid user rcs from 54.37.155.165 port 33160 ssh2
2019-12-28 22:24:33
118.24.213.107 attack
(sshd) Failed SSH login from 118.24.213.107 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Dec 28 12:16:30 andromeda sshd[17779]: Invalid user braarvig from 118.24.213.107 port 52392
Dec 28 12:16:32 andromeda sshd[17779]: Failed password for invalid user braarvig from 118.24.213.107 port 52392 ssh2
Dec 28 12:25:45 andromeda sshd[18745]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.213.107  user=root
2019-12-28 22:10:55
107.189.11.160 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-12-28 22:12:10
195.128.126.72 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2019-12-28 22:22:28
210.242.67.17 attackbots
Dec 28 13:47:54 sd-53420 sshd\[4950\]: Invalid user rpm from 210.242.67.17
Dec 28 13:47:54 sd-53420 sshd\[4950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.242.67.17
Dec 28 13:47:56 sd-53420 sshd\[4950\]: Failed password for invalid user rpm from 210.242.67.17 port 49462 ssh2
Dec 28 13:51:16 sd-53420 sshd\[6385\]: User root from 210.242.67.17 not allowed because none of user's groups are listed in AllowGroups
Dec 28 13:51:16 sd-53420 sshd\[6385\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.242.67.17  user=root
...
2019-12-28 21:50:10
129.204.11.222 attackbots
Dec 28 10:01:13 v22018086721571380 sshd[24230]: Failed password for invalid user www from 129.204.11.222 port 46620 ssh2
2019-12-28 21:59:17
159.203.7.81 attackspambots
Invalid user admin from 159.203.7.81 port 48401
2019-12-28 22:10:26
109.123.117.235 attackbotsspam
9000/tcp 2086/tcp 60000/tcp...
[2019-11-02/12-28]6pkt,6pt.(tcp)
2019-12-28 21:48:55
185.209.0.91 attack
Dec 28 14:18:38 debian-2gb-nbg1-2 kernel: \[1191836.383232\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.209.0.91 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=22732 PROTO=TCP SPT=54735 DPT=43000 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-28 22:08:22
104.244.75.179 attackbots
Honeypot attack, port: 23, PTR: rb-10.fdgdfg526.info.
2019-12-28 22:04:47
180.215.104.98 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-12-28 22:17:08
122.241.71.205 attackbotsspam
Dec 28 01:19:27 esmtp postfix/smtpd[23160]: lost connection after AUTH from unknown[122.241.71.205]
Dec 28 01:19:35 esmtp postfix/smtpd[23160]: lost connection after AUTH from unknown[122.241.71.205]
Dec 28 01:19:38 esmtp postfix/smtpd[23160]: lost connection after AUTH from unknown[122.241.71.205]
Dec 28 01:19:41 esmtp postfix/smtpd[23160]: lost connection after AUTH from unknown[122.241.71.205]
Dec 28 01:19:46 esmtp postfix/smtpd[23160]: lost connection after AUTH from unknown[122.241.71.205]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=122.241.71.205
2019-12-28 21:59:50
103.103.128.61 attackbots
$f2bV_matches
2019-12-28 22:14:26
201.217.242.11 attackbotsspam
WordPress wp-login brute force :: 201.217.242.11 0.068 BYPASS [28/Dec/2019:06:19:34  0000] [censored_4] "POST /wp-login.php HTTP/1.1" 200 2100 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-12-28 22:08:01

Recently Reported IPs

103.45.161.100 92.240.207.157 216.74.108.64 78.21.134.147
190.39.221.221 62.234.73.102 186.88.93.122 116.4.11.63
60.220.185.22 200.232.191.159 3.135.231.162 115.76.178.168
176.102.166.52 78.128.113.94 46.191.233.128 190.250.65.6
182.133.17.174 41.234.156.17 123.155.154.204 5.5.210.62