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

;; QUESTION SECTION:
;57.91.245.137.			IN	A

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

;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 08:33:15 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 137.245.91.57.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 137.245.91.57.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
88.198.139.2 attackspambots
Port scan on 1 port(s): 53
2019-11-02 19:36:06
180.101.125.226 attack
Nov  2 10:23:37 server sshd\[11097\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.125.226  user=root
Nov  2 10:23:39 server sshd\[11097\]: Failed password for root from 180.101.125.226 port 36134 ssh2
Nov  2 10:31:45 server sshd\[13241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.125.226  user=root
Nov  2 10:31:47 server sshd\[13241\]: Failed password for root from 180.101.125.226 port 59838 ssh2
Nov  2 10:37:55 server sshd\[14561\]: Invalid user yy from 180.101.125.226
Nov  2 10:37:55 server sshd\[14561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.125.226 
...
2019-11-02 19:20:02
129.204.201.27 attackbots
Automatic report - Banned IP Access
2019-11-02 19:34:22
61.177.152.42 attackbots
TCP Port Scanning
2019-11-02 19:50:34
85.15.107.128 attackspam
Chat Spam
2019-11-02 19:32:04
138.68.212.113 attackbotsspam
179/tcp 1433/tcp 5060/udp...
[2019-09-02/10-31]51pkt,43pt.(tcp),4pt.(udp)
2019-11-02 19:20:16
159.203.201.0 attackspambots
19277/tcp 587/tcp 45081/tcp...
[2019-09-14/11-01]41pkt,38pt.(tcp),1pt.(udp)
2019-11-02 19:23:44
42.119.59.78 attackbotsspam
scan z
2019-11-02 19:19:13
159.203.201.12 attackspam
Port scan: Attack repeated for 24 hours
2019-11-02 19:18:43
93.88.25.212 attackspambots
TCP Port Scanning
2019-11-02 19:46:12
146.185.25.165 attackspambots
2082/tcp 8001/tcp 995/tcp...
[2019-09-02/11-02]32pkt,12pt.(tcp),3pt.(udp)
2019-11-02 19:59:16
114.38.91.38 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/114.38.91.38/ 
 
 TW - 1H : (98)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : TW 
 NAME ASN : ASN3462 
 
 IP : 114.38.91.38 
 
 CIDR : 114.38.0.0/16 
 
 PREFIX COUNT : 390 
 
 UNIQUE IP COUNT : 12267520 
 
 
 ATTACKS DETECTED ASN3462 :  
  1H - 7 
  3H - 21 
  6H - 39 
 12H - 65 
 24H - 92 
 
 DateTime : 2019-11-02 04:42:34 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-02 19:22:54
189.130.40.39 attackbots
Automatic report - Port Scan Attack
2019-11-02 19:30:42
222.186.42.169 attackbotsspam
8010/tcp 888/tcp
[2019-10-15/11-02]2pkt
2019-11-02 19:49:12
172.105.89.161 attack
11/02/2019-06:13:59.307768 172.105.89.161 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-02 19:25:11

Recently Reported IPs

6.114.17.7 64.200.161.222 182.114.68.8 218.203.233.113
204.140.69.62 171.39.226.12 193.220.69.129 198.22.199.210
77.91.26.110 246.42.47.21 223.159.81.192 22.171.180.35
216.159.214.52 63.224.11.44 70.237.112.247 41.246.133.253
75.75.140.29 253.233.86.244 227.127.58.100 58.15.91.188