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

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

;; QUESTION SECTION:
;104.18.26.58.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 18 07:21:31 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 58.26.18.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 58.26.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
91.186.119.29 attack
1594497991 - 07/11/2020 22:06:31 Host: 91.186.119.29/91.186.119.29 Port: 445 TCP Blocked
2020-07-12 05:59:07
208.109.14.122 attack
536. On Jul 11 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 208.109.14.122.
2020-07-12 06:00:56
194.26.29.112 attack
Jul 11 23:08:00 debian-2gb-nbg1-2 kernel: \[16760263.047713\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.26.29.112 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=47884 PROTO=TCP SPT=44138 DPT=505 WINDOW=1024 RES=0x00 SYN URGP=0
2020-07-12 05:38:16
107.172.227.216 attack
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with palmerchiroga.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any v
2020-07-12 05:33:24
49.232.135.14 attack
Jul 11 14:05:04 dignus sshd[12151]: Failed password for invalid user nostra from 49.232.135.14 port 50058 ssh2
Jul 11 14:09:22 dignus sshd[12566]: Invalid user jiajiajia from 49.232.135.14 port 44926
Jul 11 14:09:22 dignus sshd[12566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.135.14
Jul 11 14:09:25 dignus sshd[12566]: Failed password for invalid user jiajiajia from 49.232.135.14 port 44926 ssh2
Jul 11 14:13:48 dignus sshd[13019]: Invalid user developer from 49.232.135.14 port 39788
...
2020-07-12 05:31:56
46.38.145.248 attack
Jul 11 23:31:07 srv01 postfix/smtpd\[1946\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:31:25 srv01 postfix/smtpd\[1945\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:32:01 srv01 postfix/smtpd\[1946\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:32:10 srv01 postfix/smtpd\[1945\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:32:14 srv01 postfix/smtpd\[7596\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-07-12 05:36:40
178.128.101.13 attackbotsspam
Fail2Ban Ban Triggered
2020-07-12 06:00:24
5.63.162.11 attack
2020-07-11T21:21:10.533943server.espacesoutien.com sshd[15540]: Invalid user vicky from 5.63.162.11 port 35562
2020-07-11T21:21:10.547163server.espacesoutien.com sshd[15540]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.63.162.11
2020-07-11T21:21:10.533943server.espacesoutien.com sshd[15540]: Invalid user vicky from 5.63.162.11 port 35562
2020-07-11T21:21:12.421786server.espacesoutien.com sshd[15540]: Failed password for invalid user vicky from 5.63.162.11 port 35562 ssh2
...
2020-07-12 05:50:08
112.85.42.176 attack
Jul 11 23:54:33 minden010 sshd[31282]: Failed password for root from 112.85.42.176 port 23011 ssh2
Jul 11 23:54:36 minden010 sshd[31282]: Failed password for root from 112.85.42.176 port 23011 ssh2
Jul 11 23:54:40 minden010 sshd[31282]: Failed password for root from 112.85.42.176 port 23011 ssh2
Jul 11 23:54:43 minden010 sshd[31282]: Failed password for root from 112.85.42.176 port 23011 ssh2
...
2020-07-12 06:01:42
111.229.139.95 attack
(sshd) Failed SSH login from 111.229.139.95 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD
2020-07-12 05:46:32
168.0.81.191 attack
Automatic report - Port Scan Attack
2020-07-12 05:58:36
112.85.42.187 attack
2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187  user=root
2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2
2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187  user=root
2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2
2020-07-11T17:41:50.965264uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2
...
2020-07-12 05:43:20
185.143.73.162 attack
Jul 11 23:30:15 web02.agentur-b-2.de postfix/smtpd[2300705]: warning: unknown[185.143.73.162]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:30:59 web02.agentur-b-2.de postfix/smtpd[2299741]: warning: unknown[185.143.73.162]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:31:42 web02.agentur-b-2.de postfix/smtpd[2299741]: warning: unknown[185.143.73.162]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:32:25 web02.agentur-b-2.de postfix/smtpd[2299741]: warning: unknown[185.143.73.162]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul 11 23:33:08 web02.agentur-b-2.de postfix/smtpd[2300705]: warning: unknown[185.143.73.162]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-07-12 05:53:46
183.249.242.103 attackspambots
Jul 11 23:58:34 journals sshd\[107146\]: Invalid user internet from 183.249.242.103
Jul 11 23:58:34 journals sshd\[107146\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.249.242.103
Jul 11 23:58:37 journals sshd\[107146\]: Failed password for invalid user internet from 183.249.242.103 port 40047 ssh2
Jul 12 00:01:52 journals sshd\[108748\]: Invalid user zhangxiaofei from 183.249.242.103
Jul 12 00:01:52 journals sshd\[108748\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.249.242.103
...
2020-07-12 05:35:04
209.141.58.20 attackspam
SSH Invalid Login
2020-07-12 05:51:03

Recently Reported IPs

104.18.26.198 104.18.27.181 104.18.27.197 104.18.27.198
104.18.27.58 104.18.28.115 104.18.28.129 104.18.28.47
104.18.29.115 104.18.29.47 104.18.3.177 104.18.3.29
104.18.3.33 104.18.3.60 104.18.30.154 104.18.31.154
104.18.47.226 104.18.47.233 104.19.116.55 104.19.132.96