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

;; QUESTION SECTION:
;137.57.113.117.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Dec 11 06:32:42 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 117.113.57.137.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 117.113.57.137.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.248.130.152 attackbotsspam
20/1/19@23:52:47: FAIL: Alarm-Network address from=180.248.130.152
...
2020-01-20 16:59:22
125.47.65.38 attack
port scan and connect, tcp 1433 (ms-sql-s)
2020-01-20 16:50:29
213.59.144.39 attackbots
Jan 19 19:39:59 kapalua sshd\[30806\]: Invalid user vnc from 213.59.144.39
Jan 19 19:39:59 kapalua sshd\[30806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.59.144.39
Jan 19 19:40:01 kapalua sshd\[30806\]: Failed password for invalid user vnc from 213.59.144.39 port 53352 ssh2
Jan 19 19:46:01 kapalua sshd\[31246\]: Invalid user jf from 213.59.144.39
Jan 19 19:46:01 kapalua sshd\[31246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.59.144.39
2020-01-20 16:42:06
73.124.236.66 attackbots
Unauthorized connection attempt detected from IP address 73.124.236.66 to port 2220 [J]
2020-01-20 16:51:22
140.143.163.113 attack
Unauthorized connection attempt detected from IP address 140.143.163.113 to port 2220 [J]
2020-01-20 17:12:13
182.191.119.185 attackspambots
Automatic report - Port Scan Attack
2020-01-20 17:10:28
202.65.170.174 attackspambots
Unauthorized IMAP connection attempt
2020-01-20 16:40:52
103.27.200.159 attackspambots
Automatic report - SSH Brute-Force Attack
2020-01-20 16:39:45
36.37.131.169 attack
20/1/19@23:52:31: FAIL: Alarm-Network address from=36.37.131.169
20/1/19@23:52:31: FAIL: Alarm-Network address from=36.37.131.169
...
2020-01-20 17:06:10
60.250.31.107 attack
Unauthorized connection attempt detected from IP address 60.250.31.107 to port 2220 [J]
2020-01-20 16:41:38
1.194.48.93 attackspambots
SSH/22 MH Probe, BF, Hack -
2020-01-20 17:08:47
94.97.100.159 attack
445/tcp 445/tcp 445/tcp
[2020-01-20]3pkt
2020-01-20 17:12:45
62.234.106.199 attackbots
Unauthorized connection attempt detected from IP address 62.234.106.199 to port 2220 [J]
2020-01-20 17:03:02
68.119.254.29 attackspambots
Automatic report - Port Scan Attack
2020-01-20 16:55:14
183.83.166.187 attack
Unauthorized connection attempt detected from IP address 183.83.166.187 to port 445
2020-01-20 16:52:45

Recently Reported IPs

124.241.96.46 125.150.143.20 54.82.214.224 107.0.177.228
49.211.101.1 139.1.94.191 226.191.244.146 64.107.132.124
171.56.49.105 232.76.98.212 15.158.245.0 71.212.124.60
195.13.20.20 255.101.114.17 194.133.211.135 254.227.102.25
198.118.166.132 135.136.100.36 176.253.224.9 120.150.173.143