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

;; QUESTION SECTION:
;26.139.114.57.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 21:08:22 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 57.114.139.26.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 57.114.139.26.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.61.40.158 attackspam
SSH brute force attempt
2020-04-02 05:01:06
109.102.129.67 attackspam
Port 23 (Telnet) access denied
2020-04-02 04:50:37
5.189.139.206 attackspambots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-04-02 04:50:13
23.80.97.160 attack
(From wordpresswizardwes@yahoo.com) Hi there,

I came across your website yesterday and ran into some missed opportunities I think you’ll want to take a look at!

I own a digital marketing company in Kingston Ontario, and can already see several minor improvements that would be solved by a basic website management package. Although cheap, this can significantly improve your online presence and outreach.

I know you’re probably very busy, but if you would like to learn more I'd be happy to send you a link with all the details.

I look forward to your response,

Wes
2020-04-02 04:51:04
188.186.182.56 attackspam
Automatic report - Port Scan Attack
2020-04-02 05:09:43
106.52.40.48 attackspambots
Apr  1 22:09:34 [HOSTNAME] sshd[12305]: User **removed** from 106.52.40.48 not allowed because not listed in AllowUsers
Apr  1 22:09:34 [HOSTNAME] sshd[12305]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.40.48  user=**removed**
Apr  1 22:09:37 [HOSTNAME] sshd[12305]: Failed password for invalid user **removed** from 106.52.40.48 port 53528 ssh2
...
2020-04-02 05:14:34
51.75.202.218 attackbotsspam
2020-03-30 22:13:17 server sshd[76270]: Failed password for invalid user root from 51.75.202.218 port 41500 ssh2
2020-04-02 05:13:20
134.209.178.109 attackbotsspam
Invalid user aya from 134.209.178.109 port 38710
2020-04-02 05:11:23
178.62.33.138 attack
SSH Brute Force
2020-04-02 05:12:31
111.62.12.169 attackbotsspam
Apr  1 23:27:28 hosting sshd[9585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.62.12.169  user=root
Apr  1 23:27:30 hosting sshd[9585]: Failed password for root from 111.62.12.169 port 46848 ssh2
Apr  1 23:41:00 hosting sshd[10779]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.62.12.169  user=root
Apr  1 23:41:03 hosting sshd[10779]: Failed password for root from 111.62.12.169 port 64784 ssh2
Apr  1 23:48:48 hosting sshd[11386]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.62.12.169  user=root
Apr  1 23:48:50 hosting sshd[11386]: Failed password for root from 111.62.12.169 port 52166 ssh2
...
2020-04-02 04:49:28
180.76.152.157 attack
Apr  1 15:18:36 ns381471 sshd[29330]: Failed password for root from 180.76.152.157 port 57304 ssh2
2020-04-02 05:10:54
49.234.44.48 attack
Apr  1 22:38:27 ewelt sshd[3283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.44.48
Apr  1 22:38:27 ewelt sshd[3283]: Invalid user ze from 49.234.44.48 port 48659
Apr  1 22:38:30 ewelt sshd[3283]: Failed password for invalid user ze from 49.234.44.48 port 48659 ssh2
Apr  1 22:43:24 ewelt sshd[3651]: Invalid user alarm from 49.234.44.48 port 50565
...
2020-04-02 04:47:06
192.95.6.110 attack
(sshd) Failed SSH login from 192.95.6.110 (BR/Brazil/sa.signifi.com): 5 in the last 3600 secs
2020-04-02 05:00:03
104.248.117.234 attackspam
2020-04-01T19:19:08.918600abusebot-5.cloudsearch.cf sshd[18602]: Invalid user ldhong from 104.248.117.234 port 38820
2020-04-01T19:19:08.925168abusebot-5.cloudsearch.cf sshd[18602]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.117.234
2020-04-01T19:19:08.918600abusebot-5.cloudsearch.cf sshd[18602]: Invalid user ldhong from 104.248.117.234 port 38820
2020-04-01T19:19:11.546943abusebot-5.cloudsearch.cf sshd[18602]: Failed password for invalid user ldhong from 104.248.117.234 port 38820 ssh2
2020-04-01T19:23:09.864019abusebot-5.cloudsearch.cf sshd[18734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.117.234  user=root
2020-04-01T19:23:11.903851abusebot-5.cloudsearch.cf sshd[18734]: Failed password for root from 104.248.117.234 port 50710 ssh2
2020-04-01T19:26:50.122460abusebot-5.cloudsearch.cf sshd[18755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
...
2020-04-02 05:14:55
49.234.163.238 attack
Apr  1 22:48:39 pve sshd[15780]: Failed password for root from 49.234.163.238 port 46746 ssh2
Apr  1 22:52:42 pve sshd[16438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.163.238 
Apr  1 22:52:44 pve sshd[16438]: Failed password for invalid user dk from 49.234.163.238 port 60120 ssh2
2020-04-02 05:04:25

Recently Reported IPs

104.128.237.197 178.211.138.207 240.40.178.225 224.119.26.17
74.76.170.251 124.222.148.94 239.110.179.79 5.38.187.129
158.111.74.5 239.96.188.115 151.50.26.181 14.182.16.26
82.167.57.205 203.27.81.27 184.76.123.107 250.155.92.64
161.191.145.80 61.25.95.243 168.206.240.155 82.50.202.65