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

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

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 01 02:52:55 CST 2020
;; MSG SIZE  rcvd: 117
Host info
91.138.194.52.in-addr.arpa domain name pointer ec2-52-194-138-91.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
91.138.194.52.in-addr.arpa	name = ec2-52-194-138-91.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
160.16.216.114 attack
Aug  5 00:02:22 mail sshd[7552]: Invalid user test2 from 160.16.216.114
Aug  5 00:02:22 mail sshd[7552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.16.216.114
Aug  5 00:02:22 mail sshd[7552]: Invalid user test2 from 160.16.216.114
Aug  5 00:02:24 mail sshd[7552]: Failed password for invalid user test2 from 160.16.216.114 port 55990 ssh2
...
2019-08-05 07:56:31
92.243.126.25 attackspambots
Autoban   92.243.126.25 AUTH/CONNECT
2019-08-05 07:55:00
198.199.84.154 attackspam
Failed password for root from 198.199.84.154 port 46472 ssh2
Invalid user marixl from 198.199.84.154 port 46026
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.84.154
Failed password for invalid user marixl from 198.199.84.154 port 46026 ssh2
Invalid user greenhg from 198.199.84.154 port 45060
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.84.154
2019-08-05 07:53:41
91.236.66.123 attackspambots
Autoban   91.236.66.123 AUTH/CONNECT
2019-08-05 08:12:43
5.175.17.52 attack
Port Scan: TCP/445
2019-08-05 08:31:39
92.249.219.47 attack
Autoban   92.249.219.47 AUTH/CONNECT
2019-08-05 07:53:08
209.134.3.29 attack
3389BruteforceFW21
2019-08-05 08:13:26
91.230.252.145 attackbotsspam
Autoban   91.230.252.145 AUTH/CONNECT
2019-08-05 08:15:55
138.68.111.27 attackspam
(sshd) Failed SSH login from 138.68.111.27 (semako-01.weplay.space): 5 in the last 3600 secs
2019-08-05 08:09:26
97.105.137.194 attackbots
Port Scan: UDP/137
2019-08-05 08:25:57
41.41.87.22 attackspam
1564953312 - 08/05/2019 04:15:12 Host: host-41.41.87.22.tedata.net/41.41.87.22 Port: 23 TCP Blocked
...
2019-08-05 08:10:32
51.255.35.41 attackspam
SSH invalid-user multiple login attempts
2019-08-05 07:48:57
92.23.59.36 attackspambots
Autoban   92.23.59.36 AUTH/CONNECT
2019-08-05 07:56:03
220.142.125.71 attack
Port Scan: TCP/23
2019-08-05 08:33:12
190.74.92.21 attackbots
Port Scan: TCP/445
2019-08-05 08:18:20

Recently Reported IPs

59.124.115.208 189.212.177.10 72.210.252.156 138.122.51.100
183.66.47.121 104.129.129.73 167.172.209.208 222.102.206.151
177.5.100.146 212.108.87.135 171.101.94.1 2.204.49.129
102.164.212.81 145.255.9.210 81.198.171.29 109.166.181.174
14.230.44.53 96.19.85.39 201.222.90.63 96.221.206.30