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

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.227.139.186 attack
Apr 22 19:26:39 jane sshd[28480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186 
Apr 22 19:26:41 jane sshd[28480]: Failed password for invalid user oracle from 104.227.139.186 port 59286 ssh2
...
2020-04-23 01:52:42
104.227.139.186 attackbotsspam
$f2bV_matches
2020-04-19 03:15:06
104.227.139.186 attackspam
Apr 13 19:07:50 wbs sshd\[18975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=root
Apr 13 19:07:52 wbs sshd\[18975\]: Failed password for root from 104.227.139.186 port 52024 ssh2
Apr 13 19:11:31 wbs sshd\[19328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=root
Apr 13 19:11:32 wbs sshd\[19328\]: Failed password for root from 104.227.139.186 port 32864 ssh2
Apr 13 19:15:23 wbs sshd\[19641\]: Invalid user guest from 104.227.139.186
2020-04-14 13:37:06
104.227.139.186 attackbots
Apr  8 20:50:35 ip-172-31-62-245 sshd\[7538\]: Invalid user ftpuser from 104.227.139.186\
Apr  8 20:50:37 ip-172-31-62-245 sshd\[7538\]: Failed password for invalid user ftpuser from 104.227.139.186 port 46246 ssh2\
Apr  8 20:53:59 ip-172-31-62-245 sshd\[7599\]: Invalid user deploy from 104.227.139.186\
Apr  8 20:54:02 ip-172-31-62-245 sshd\[7599\]: Failed password for invalid user deploy from 104.227.139.186 port 55100 ssh2\
Apr  8 20:57:21 ip-172-31-62-245 sshd\[7645\]: Invalid user server from 104.227.139.186\
2020-04-09 05:43:59
104.227.139.186 attackbots
SSH Brute-Forcing (server1)
2020-04-03 20:25:56
104.227.139.186 attackbotsspam
Invalid user wangruiyang from 104.227.139.186 port 50010
2020-04-03 07:31:43
104.227.139.186 attackbots
Mar 30 08:01:33 ift sshd\[24292\]: Invalid user doj from 104.227.139.186Mar 30 08:01:35 ift sshd\[24292\]: Failed password for invalid user doj from 104.227.139.186 port 35366 ssh2Mar 30 08:04:59 ift sshd\[24672\]: Invalid user iia from 104.227.139.186Mar 30 08:05:01 ift sshd\[24672\]: Failed password for invalid user iia from 104.227.139.186 port 39870 ssh2Mar 30 08:08:17 ift sshd\[25391\]: Failed password for invalid user admin from 104.227.139.186 port 44374 ssh2
...
2020-03-30 14:22:20
104.227.139.186 attack
Mar 27 16:00:19 vps sshd[944339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
Mar 27 16:00:21 vps sshd[944339]: Failed password for invalid user hlds from 104.227.139.186 port 49264 ssh2
Mar 27 16:03:49 vps sshd[961505]: Invalid user xjz from 104.227.139.186 port 33940
Mar 27 16:03:49 vps sshd[961505]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
Mar 27 16:03:50 vps sshd[961505]: Failed password for invalid user xjz from 104.227.139.186 port 33940 ssh2
...
2020-03-28 04:30:44
104.227.139.186 attackbots
bruteforce detected
2020-03-22 03:33:48
104.227.139.186 attack
*Port Scan* detected from 104.227.139.186 (US/United States/New York/Buffalo/-). 4 hits in the last 285 seconds
2020-03-21 02:07:19
104.227.139.186 attack
2020-03-12T22:06:05.772585dmca.cloudsearch.cf sshd[17445]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=root
2020-03-12T22:06:07.580146dmca.cloudsearch.cf sshd[17445]: Failed password for root from 104.227.139.186 port 42822 ssh2
2020-03-12T22:10:00.623857dmca.cloudsearch.cf sshd[17681]: Invalid user telnet from 104.227.139.186 port 59342
2020-03-12T22:10:00.628702dmca.cloudsearch.cf sshd[17681]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
2020-03-12T22:10:00.623857dmca.cloudsearch.cf sshd[17681]: Invalid user telnet from 104.227.139.186 port 59342
2020-03-12T22:10:02.703106dmca.cloudsearch.cf sshd[17681]: Failed password for invalid user telnet from 104.227.139.186 port 59342 ssh2
2020-03-12T22:13:46.994269dmca.cloudsearch.cf sshd[17911]: Invalid user Ronald from 104.227.139.186 port 47630
...
2020-03-13 07:32:18
104.227.139.186 attackbots
2020-03-01T22:53:29.628179luisaranguren sshd[2881740]: Invalid user landscape from 104.227.139.186 port 42364
2020-03-01T22:53:31.452281luisaranguren sshd[2881740]: Failed password for invalid user landscape from 104.227.139.186 port 42364 ssh2
...
2020-03-01 20:15:13
104.227.139.186 attackspam
2020-02-26T21:45:12.280824shield sshd\[10107\]: Invalid user nagios2019 from 104.227.139.186 port 55176
2020-02-26T21:45:12.285979shield sshd\[10107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
2020-02-26T21:45:14.197860shield sshd\[10107\]: Failed password for invalid user nagios2019 from 104.227.139.186 port 55176 ssh2
2020-02-26T21:51:14.126358shield sshd\[11132\]: Invalid user bugzilla123 from 104.227.139.186 port 52320
2020-02-26T21:51:14.130433shield sshd\[11132\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
2020-02-27 05:58:09
104.227.139.186 attackbotsspam
Feb 24 13:54:36 hanapaa sshd\[4043\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=daemon
Feb 24 13:54:38 hanapaa sshd\[4043\]: Failed password for daemon from 104.227.139.186 port 59490 ssh2
Feb 24 14:01:57 hanapaa sshd\[4618\]: Invalid user quest from 104.227.139.186
Feb 24 14:01:57 hanapaa sshd\[4618\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186
Feb 24 14:01:59 hanapaa sshd\[4618\]: Failed password for invalid user quest from 104.227.139.186 port 58768 ssh2
2020-02-25 08:09:34
104.227.139.186 attack
invalid user
2020-02-14 03:37:50
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.227.13.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8669
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.227.13.45.			IN	A

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

;; Query time: 72 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 16:09:23 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 45.13.227.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 45.13.227.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
169.38.93.99 attackbots
US_RIPE_<177>1583556588 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2] {TCP} 169.38.93.99:61553
2020-03-07 20:33:05
49.235.221.86 attack
Mar  7 02:04:34 hpm sshd\[7794\]: Invalid user nginx from 49.235.221.86
Mar  7 02:04:34 hpm sshd\[7794\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.221.86
Mar  7 02:04:36 hpm sshd\[7794\]: Failed password for invalid user nginx from 49.235.221.86 port 58856 ssh2
Mar  7 02:11:35 hpm sshd\[8347\]: Invalid user gerrit2 from 49.235.221.86
Mar  7 02:11:35 hpm sshd\[8347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.221.86
2020-03-07 20:26:03
5.239.244.252 attack
Invalid user cloud from 5.239.244.252 port 36972
2020-03-07 20:37:51
213.226.126.85 attackspam
2020-03-07T09:31:23.437518abusebot-4.cloudsearch.cf sshd[21804]: Invalid user opforserver from 213.226.126.85 port 34532
2020-03-07T09:31:23.443973abusebot-4.cloudsearch.cf sshd[21804]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.226.126.85
2020-03-07T09:31:23.437518abusebot-4.cloudsearch.cf sshd[21804]: Invalid user opforserver from 213.226.126.85 port 34532
2020-03-07T09:31:25.080565abusebot-4.cloudsearch.cf sshd[21804]: Failed password for invalid user opforserver from 213.226.126.85 port 34532 ssh2
2020-03-07T09:35:42.308805abusebot-4.cloudsearch.cf sshd[22024]: Invalid user sshuser from 213.226.126.85 port 52492
2020-03-07T09:35:42.315506abusebot-4.cloudsearch.cf sshd[22024]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.226.126.85
2020-03-07T09:35:42.308805abusebot-4.cloudsearch.cf sshd[22024]: Invalid user sshuser from 213.226.126.85 port 52492
2020-03-07T09:35:44.177509abusebot-4.cloud
...
2020-03-07 20:40:33
176.31.252.148 attackspam
Mar  7 11:55:41 host sshd[57425]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=infra01.linalis.com  user=root
Mar  7 11:55:43 host sshd[57425]: Failed password for root from 176.31.252.148 port 34822 ssh2
...
2020-03-07 20:11:46
78.128.113.67 attack
(smtpauth) Failed SMTP AUTH login from 78.128.113.67 (BG/Bulgaria/ip-113-67.4vendeta.com): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-03-07 16:06:28 plain authenticator failed for ([78.128.113.67]) [78.128.113.67]: 535 Incorrect authentication data (set_id=igep@ardestancement.com)
2020-03-07 20:38:09
43.229.92.103 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 20:08:52
2.190.183.193 attackbots
20/3/6@23:50:12: FAIL: Alarm-Network address from=2.190.183.193
...
2020-03-07 20:11:15
45.56.78.64 attackbots
trying to access non-authorized port
2020-03-07 20:20:24
39.43.43.201 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 20:28:53
65.158.79.109 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 20:32:21
118.201.138.94 attack
Mar  7 06:48:34 master sshd[11573]: Failed password for root from 118.201.138.94 port 56818 ssh2
2020-03-07 20:05:24
71.6.233.230 attack
firewall-block, port(s): 4433/tcp
2020-03-07 20:15:56
80.82.65.74 attackspam
firewall-block, port(s): 3113/tcp, 10200/tcp, 20002/tcp
2020-03-07 20:25:20
195.54.166.26 attack
Scanning for open ports and vulnerable services: 33890,33891,33892,33893,33894,33895
2020-03-07 20:01:27

Recently Reported IPs

104.227.13.29 104.227.13.63 104.227.13.43 104.227.13.41
104.227.13.34 104.227.13.248 104.227.13.6 104.227.13.68
104.227.13.70 104.227.13.76 104.227.13.72 104.227.13.78
104.227.13.82 104.227.13.99 104.227.13.93 104.227.132.128
104.227.13.85 104.227.132.132 104.227.132.131 104.227.13.81