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

Region: Ohio

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: Amazon.com, Inc.

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Tue May 14 23:47:05 CST 2019
;; MSG SIZE  rcvd: 117

Host info
138.234.58.13.in-addr.arpa domain name pointer ec2-13-58-234-138.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
138.234.58.13.in-addr.arpa	name = ec2-13-58-234-138.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
142.105.210.59 attackspam
Automatic report - Port Scan Attack
2019-11-12 20:51:09
203.229.246.118 attackbots
Nov 12 07:11:40 Tower sshd[20201]: Connection from 203.229.246.118 port 34574 on 192.168.10.220 port 22
Nov 12 07:12:05 Tower sshd[20201]: Invalid user qhsupport from 203.229.246.118 port 34574
Nov 12 07:12:05 Tower sshd[20201]: error: Could not get shadow information for NOUSER
Nov 12 07:12:05 Tower sshd[20201]: Failed password for invalid user qhsupport from 203.229.246.118 port 34574 ssh2
Nov 12 07:12:06 Tower sshd[20201]: Received disconnect from 203.229.246.118 port 34574:11: Normal Shutdown, Thank you for playing [preauth]
Nov 12 07:12:06 Tower sshd[20201]: Disconnected from invalid user qhsupport 203.229.246.118 port 34574 [preauth]
2019-11-12 20:39:27
167.71.159.129 attackspam
SSH/22 MH Probe, BF, Hack -
2019-11-12 20:31:10
83.97.20.46 attack
[portscan] tcp/143 [IMAP]
[scan/connect: 2 time(s)]
in blocklist.de:'listed [pop3]'
*(RWIN=65535)(11121222)
2019-11-12 20:15:00
182.117.33.119 attackspambots
Honeypot attack, port: 23, PTR: hn.kd.ny.adsl.
2019-11-12 20:30:33
184.75.211.146 attackbots
(From frederick.peeples@hotmail.com) Do away with credit card fees from your business forever get info here: http://bit.ly/neverfees
2019-11-12 20:36:54
170.130.187.26 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2019-11-12 20:43:44
51.254.210.53 attackspambots
Nov 12 15:10:54 vibhu-HP-Z238-Microtower-Workstation sshd\[22765\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.210.53  user=root
Nov 12 15:10:57 vibhu-HP-Z238-Microtower-Workstation sshd\[22765\]: Failed password for root from 51.254.210.53 port 54494 ssh2
Nov 12 15:14:25 vibhu-HP-Z238-Microtower-Workstation sshd\[23015\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.210.53  user=root
Nov 12 15:14:27 vibhu-HP-Z238-Microtower-Workstation sshd\[23015\]: Failed password for root from 51.254.210.53 port 34528 ssh2
Nov 12 15:18:00 vibhu-HP-Z238-Microtower-Workstation sshd\[23236\]: Invalid user host from 51.254.210.53
Nov 12 15:18:01 vibhu-HP-Z238-Microtower-Workstation sshd\[23236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.210.53
...
2019-11-12 20:35:51
42.225.222.226 attack
Honeypot attack, port: 23, PTR: hn.kd.ny.adsl.
2019-11-12 20:24:07
42.228.124.236 attackbotsspam
Port scan
2019-11-12 20:23:08
187.250.34.104 attackbots
Port 1433 Scan
2019-11-12 20:46:32
124.152.76.213 attackspambots
Nov 12 11:59:02 srv01 sshd[14370]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.152.76.213  user=root
Nov 12 11:59:04 srv01 sshd[14370]: Failed password for root from 124.152.76.213 port 61615 ssh2
Nov 12 12:04:24 srv01 sshd[14761]: Invalid user apache from 124.152.76.213
Nov 12 12:04:24 srv01 sshd[14761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.152.76.213
Nov 12 12:04:24 srv01 sshd[14761]: Invalid user apache from 124.152.76.213
Nov 12 12:04:26 srv01 sshd[14761]: Failed password for invalid user apache from 124.152.76.213 port 22424 ssh2
...
2019-11-12 20:51:34
103.40.8.170 attackbots
Nov 11 20:37:34 sachi sshd\[31178\]: Invalid user lyndon from 103.40.8.170
Nov 11 20:37:34 sachi sshd\[31178\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.40.8.170
Nov 11 20:37:37 sachi sshd\[31178\]: Failed password for invalid user lyndon from 103.40.8.170 port 42086 ssh2
Nov 11 20:42:26 sachi sshd\[31643\]: Invalid user lab from 103.40.8.170
Nov 11 20:42:26 sachi sshd\[31643\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.40.8.170
2019-11-12 20:38:48
218.219.123.118 attackspam
Honeypot attack, port: 23, PTR: 218-219-123-118.ppp.bbiq.jp.
2019-11-12 20:53:03
182.73.26.2 attack
Honeypot attack, port: 445, PTR: PTR record not found
2019-11-12 20:37:27

Recently Reported IPs

216.218.206.91 119.21.159.102 182.52.183.125 199.244.31.143
201.233.158.220 1.182.24.137 194.235.139.3 95.110.95.245
77.247.110.48 12.255.29.69 41.246.31.91 113.22.10.1
36.206.102.124 103.196.138.1 201.159.112.252 184.19.192.210
176.223.135.68 133.237.119.126 174.46.145.157 103.136.83.83