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 of America (the)

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

;; QUESTION SECTION:
;35.89.138.34.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 21 04:41:56 CST 2025
;; MSG SIZE  rcvd: 105
Host info
34.138.89.35.in-addr.arpa domain name pointer ec2-35-89-138-34.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.138.89.35.in-addr.arpa	name = ec2-35-89-138-34.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
77.246.57.234 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 29-10-2019 11:40:32.
2019-10-29 21:01:47
112.83.58.179 attack
Port Scan
2019-10-29 20:34:35
222.186.175.167 attackbots
Oct 29 02:26:00 auw2 sshd\[16595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167  user=root
Oct 29 02:26:02 auw2 sshd\[16595\]: Failed password for root from 222.186.175.167 port 34680 ssh2
Oct 29 02:26:06 auw2 sshd\[16595\]: Failed password for root from 222.186.175.167 port 34680 ssh2
Oct 29 02:26:10 auw2 sshd\[16595\]: Failed password for root from 222.186.175.167 port 34680 ssh2
Oct 29 02:26:27 auw2 sshd\[16639\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167  user=root
2019-10-29 20:32:59
46.172.8.25 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 29-10-2019 11:40:31.
2019-10-29 21:03:25
187.28.50.230 attackbots
Oct 29 13:48:48 sso sshd[8978]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.28.50.230
Oct 29 13:48:50 sso sshd[8978]: Failed password for invalid user jiangsuidc from 187.28.50.230 port 44188 ssh2
...
2019-10-29 20:58:45
80.102.178.129 attackspam
Oct 29 11:38:51 ip-172-30-0-179 sshd\[5347\]: Invalid user admin from 80.102.178.129\
Oct 29 11:39:32 ip-172-30-0-179 sshd\[5453\]: Invalid user pi from 80.102.178.129\
Oct 29 11:39:52 ip-172-30-0-179 sshd\[5455\]: Invalid user debian from 80.102.178.129\
Oct 29 11:40:16 ip-172-30-0-179 sshd\[5457\]: Invalid user osmc from 80.102.178.129\
Oct 29 11:40:36 ip-172-30-0-179 sshd\[5459\]: Invalid user xbian from 80.102.178.129\
Oct 29 11:40:56 ip-172-30-0-179 sshd\[5461\]: Invalid user ubnt from 80.102.178.129\
2019-10-29 20:43:54
129.204.201.9 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.201.9  user=root
Failed password for root from 129.204.201.9 port 36120 ssh2
Invalid user ins from 129.204.201.9 port 48530
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.201.9
Failed password for invalid user ins from 129.204.201.9 port 48530 ssh2
2019-10-29 20:55:30
139.198.189.36 attackspambots
Invalid user akerhielm from 139.198.189.36 port 39202
2019-10-29 20:47:59
222.186.175.169 attackbotsspam
Oct 29 13:54:47 arianus sshd\[1602\]: Unable to negotiate with 222.186.175.169 port 25030: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 \[preauth\]
...
2019-10-29 20:58:14
104.89.31.107 attackspam
10/29/2019-13:39:57.561924 104.89.31.107 Protocol: 6 SURICATA TLS invalid record/traffic
2019-10-29 20:49:22
49.88.112.114 attackbotsspam
Oct 29 02:30:14 wbs sshd\[8533\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
Oct 29 02:30:17 wbs sshd\[8533\]: Failed password for root from 49.88.112.114 port 44752 ssh2
Oct 29 02:31:19 wbs sshd\[8613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
Oct 29 02:31:21 wbs sshd\[8613\]: Failed password for root from 49.88.112.114 port 49660 ssh2
Oct 29 02:33:18 wbs sshd\[8794\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114  user=root
2019-10-29 20:39:01
49.235.243.246 attack
2019-10-29T12:13:22.563303abusebot-7.cloudsearch.cf sshd\[9551\]: Invalid user primtsc from 49.235.243.246 port 34624
2019-10-29 20:38:36
36.76.3.122 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 29-10-2019 11:40:30.
2019-10-29 21:05:22
112.222.29.147 attack
Oct 29 13:01:35 vps647732 sshd[16615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.222.29.147
Oct 29 13:01:37 vps647732 sshd[16615]: Failed password for invalid user ready from 112.222.29.147 port 35086 ssh2
...
2019-10-29 20:36:29
59.126.168.163 attackbotsspam
Port Scan
2019-10-29 20:29:34

Recently Reported IPs

212.191.38.199 172.143.105.44 81.253.77.3 121.152.239.54
229.35.112.243 3.181.93.83 213.203.183.217 194.47.171.251
215.13.217.221 51.113.116.158 138.54.207.60 176.214.107.67
227.230.79.169 117.254.5.199 129.20.54.43 98.179.194.156
88.225.130.136 142.32.10.106 66.63.224.220 202.235.111.138