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:
IP Type Details Datetime
104.26.2.116 normal
443
2025-03-28 16:46:33
104.26.2.27 attackspambots
SSH login attempts.
2020-06-19 19:32:02
104.26.2.46 attackbotsspam
Block🖕🖕🖕
2020-05-14 22:57:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.26.2.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28717
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.26.2.139.			IN	A

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

;; Query time: 92 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 04:08:38 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 139.2.26.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 139.2.26.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.83.77.224 attackbotsspam
2020-04-07T16:16:29.878652shield sshd\[8177\]: Invalid user deploy from 51.83.77.224 port 34174
2020-04-07T16:16:29.882177shield sshd\[8177\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.ip-51-83-77.eu
2020-04-07T16:16:31.656368shield sshd\[8177\]: Failed password for invalid user deploy from 51.83.77.224 port 34174 ssh2
2020-04-07T16:20:34.925442shield sshd\[9801\]: Invalid user user from 51.83.77.224 port 46018
2020-04-07T16:20:34.929535shield sshd\[9801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=224.ip-51-83-77.eu
2020-04-08 03:31:48
23.108.50.69 attackbotsspam
3,22-07/07 [bc04/m165] PostRequest-Spammer scoring: brussels
2020-04-08 03:04:00
125.91.32.157 attack
SSH brute-force: detected 10 distinct usernames within a 24-hour window.
2020-04-08 03:00:27
85.174.104.116 attackbotsspam
Unauthorized connection attempt from IP address 85.174.104.116 on Port 445(SMB)
2020-04-08 03:12:55
185.176.27.102 attackspam
Apr  7 20:51:27 debian-2gb-nbg1-2 kernel: \[8544507.453237\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.102 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=14798 PROTO=TCP SPT=45463 DPT=17600 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-08 03:04:59
51.91.100.109 attackspam
(sshd) Failed SSH login from 51.91.100.109 (FR/France/109.ip-51-91-100.eu): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  7 21:02:27 ubnt-55d23 sshd[11217]: Invalid user admin from 51.91.100.109 port 59640
Apr  7 21:02:30 ubnt-55d23 sshd[11217]: Failed password for invalid user admin from 51.91.100.109 port 59640 ssh2
2020-04-08 03:16:17
45.152.32.32 attack
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - positivelychiropractic.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across positivelychiropractic.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally
2020-04-08 03:03:02
49.48.102.180 attack
2020-04-07 14:40:43 plain_virtual_exim authenticator failed for ([127.0.0.1]) [49.48.102.180]: 535 Incorrect authentication data


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.48.102.180
2020-04-08 02:58:07
218.92.0.171 attack
Apr  7 19:21:07 124388 sshd[17874]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.171  user=root
Apr  7 19:21:09 124388 sshd[17874]: Failed password for root from 218.92.0.171 port 8778 ssh2
Apr  7 19:21:07 124388 sshd[17874]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.171  user=root
Apr  7 19:21:09 124388 sshd[17874]: Failed password for root from 218.92.0.171 port 8778 ssh2
Apr  7 19:21:25 124388 sshd[17874]: error: maximum authentication attempts exceeded for root from 218.92.0.171 port 8778 ssh2 [preauth]
2020-04-08 03:32:05
114.67.72.164 attack
Apr  7 17:30:04 icinga sshd[11654]: Failed password for root from 114.67.72.164 port 43394 ssh2
Apr  7 17:34:13 icinga sshd[18723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.72.164 
Apr  7 17:34:15 icinga sshd[18723]: Failed password for invalid user user from 114.67.72.164 port 55070 ssh2
...
2020-04-08 02:56:17
220.167.100.60 attackspambots
Apr  7 18:05:02 ns382633 sshd\[15619\]: Invalid user test from 220.167.100.60 port 40214
Apr  7 18:05:02 ns382633 sshd\[15619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.167.100.60
Apr  7 18:05:05 ns382633 sshd\[15619\]: Failed password for invalid user test from 220.167.100.60 port 40214 ssh2
Apr  7 18:08:04 ns382633 sshd\[16437\]: Invalid user oracle4 from 220.167.100.60 port 60204
Apr  7 18:08:04 ns382633 sshd\[16437\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.167.100.60
2020-04-08 03:30:02
85.148.182.127 attack
Apr  7 19:43:29 websrv1.aknwsrv.net postfix/smtpd[23013]: warning: s5594b67f.adsl.online.nl[85.148.182.127]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  7 19:43:29 websrv1.aknwsrv.net postfix/smtpd[23013]: lost connection after AUTH from s5594b67f.adsl.online.nl[85.148.182.127]
Apr  7 19:43:35 websrv1.aknwsrv.net postfix/smtpd[23013]: warning: s5594b67f.adsl.online.nl[85.148.182.127]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  7 19:43:35 websrv1.aknwsrv.net postfix/smtpd[23013]: lost connection after AUTH from s5594b67f.adsl.online.nl[85.148.182.127]
Apr  7 19:43:45 websrv1.aknwsrv.net postfix/smtpd[23013]: warning: s5594b67f.adsl.online.nl[85.148.182.127]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Apr  7 19:43:45 websrv1.aknwsrv.net postfix/smtpd[23013]: lost connection after AUTH from s5594b67f.adsl.online.nl[85.148.182.127]
2020-04-08 03:28:58
101.95.131.122 attack
Unauthorized connection attempt from IP address 101.95.131.122 on Port 445(SMB)
2020-04-08 03:14:20
201.156.218.95 attackspambots
Automatic report - Port Scan Attack
2020-04-08 03:16:42
197.50.31.97 attackspambots
Unauthorized connection attempt from IP address 197.50.31.97 on Port 445(SMB)
2020-04-08 03:34:49

Recently Reported IPs

104.26.2.132 104.26.2.136 104.26.2.137 104.26.2.133
104.26.2.138 104.26.2.135 104.26.2.14 104.26.2.141
104.26.2.140 104.26.2.142 104.26.2.146 104.26.2.145
104.26.2.143 104.26.2.147 104.26.2.144 104.26.2.148
104.26.2.149 104.26.2.153 104.26.2.151 104.26.2.152