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

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

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 05:47:34 CST 2020
;; MSG SIZE  rcvd: 117
Host info
126.41.214.34.in-addr.arpa domain name pointer ec2-34-214-41-126.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
126.41.214.34.in-addr.arpa	name = ec2-34-214-41-126.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
174.112.6.16 attack
2019-08-12 UTC: 1x - root
2019-08-13 09:10:43
123.30.7.177 attackspambots
Aug 13 02:06:06 debian sshd\[16919\]: Invalid user train from 123.30.7.177 port 50624
Aug 13 02:06:06 debian sshd\[16919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.30.7.177
...
2019-08-13 09:13:04
89.248.168.107 attack
Aug 13 02:35:14 h2177944 kernel: \[3980271.531828\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=89.248.168.107 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=41011 PROTO=TCP SPT=53599 DPT=5415 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 02:39:27 h2177944 kernel: \[3980524.807285\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=89.248.168.107 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=43739 PROTO=TCP SPT=53622 DPT=5666 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 02:44:58 h2177944 kernel: \[3980855.743079\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=89.248.168.107 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=39974 PROTO=TCP SPT=53581 DPT=5284 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 02:46:30 h2177944 kernel: \[3980947.362000\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=89.248.168.107 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=33201 PROTO=TCP SPT=53659 DPT=5923 WINDOW=1024 RES=0x00 SYN URGP=0 
Aug 13 02:49:11 h2177944 kernel: \[3981108.472565\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=89.248.168.107 DST=85.214.
2019-08-13 09:19:20
118.24.210.86 attackbotsspam
Aug 13 01:48:48 intra sshd\[12336\]: Invalid user db2fenc1 from 118.24.210.86Aug 13 01:48:50 intra sshd\[12336\]: Failed password for invalid user db2fenc1 from 118.24.210.86 port 54987 ssh2Aug 13 01:53:47 intra sshd\[12394\]: Invalid user user from 118.24.210.86Aug 13 01:53:49 intra sshd\[12394\]: Failed password for invalid user user from 118.24.210.86 port 46439 ssh2Aug 13 01:58:42 intra sshd\[12432\]: Invalid user brix from 118.24.210.86Aug 13 01:58:43 intra sshd\[12432\]: Failed password for invalid user brix from 118.24.210.86 port 37882 ssh2
...
2019-08-13 09:14:19
191.53.58.132 attackbots
SASL PLAIN auth failed: ruser=...
2019-08-13 09:55:25
81.89.56.241 attackbots
2019-08-12 UTC: 2x - test(2x)
2019-08-13 09:15:39
122.154.239.93 attackbotsspam
Invalid user postgres from 122.154.239.93 port 40529
2019-08-13 09:13:27
89.174.64.3 attackspam
Aug 13 00:00:48 rigel postfix/smtpd[2541]: connect from unknown[89.174.64.3]
Aug 13 00:00:49 rigel postfix/smtpd[2541]: warning: unknown[89.174.64.3]: SASL CRAM-MD5 authentication failed: authentication failure
Aug 13 00:00:49 rigel postfix/smtpd[2541]: warning: unknown[89.174.64.3]: SASL PLAIN authentication failed: authentication failure
Aug 13 00:00:49 rigel postfix/smtpd[2541]: warning: unknown[89.174.64.3]: SASL LOGIN authentication failed: authentication failure
Aug 13 00:00:49 rigel postfix/smtpd[2541]: disconnect from unknown[89.174.64.3]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=89.174.64.3
2019-08-13 09:29:57
88.129.208.50 attackspambots
23/tcp 23/tcp 23/tcp...
[2019-06-21/08-12]8pkt,1pt.(tcp)
2019-08-13 09:28:57
35.197.227.71 attackbots
Aug 13 03:08:31 rpi sshd[19879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.197.227.71 
Aug 13 03:08:33 rpi sshd[19879]: Failed password for invalid user admin from 35.197.227.71 port 57738 ssh2
2019-08-13 09:17:13
200.192.147.219 attack
SASL PLAIN auth failed: ruser=...
2019-08-13 09:40:10
68.68.240.151 attackspam
Invalid user hadoop from 68.68.240.151 port 60829
2019-08-13 09:32:12
191.53.253.60 attack
SASL PLAIN auth failed: ruser=...
2019-08-13 09:45:46
201.80.92.184 attackbots
Aug 13 01:23:35 MK-Soft-VM7 sshd\[5395\]: Invalid user gdm from 201.80.92.184 port 60232
Aug 13 01:23:35 MK-Soft-VM7 sshd\[5395\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.80.92.184
Aug 13 01:23:37 MK-Soft-VM7 sshd\[5395\]: Failed password for invalid user gdm from 201.80.92.184 port 60232 ssh2
...
2019-08-13 09:23:55
200.3.16.114 attackbotsspam
SASL PLAIN auth failed: ruser=...
2019-08-13 09:43:23

Recently Reported IPs

72.238.213.254 182.167.85.164 188.19.28.130 172.94.110.86
188.18.148.235 212.164.13.39 193.40.102.112 212.159.227.55
124.176.251.222 49.81.52.109 84.10.14.133 70.3.109.10
121.211.78.221 37.142.233.0 17.78.224.150 182.45.196.76
78.11.167.177 76.28.214.147 112.22.91.232 186.235.200.51