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:
IP Type Details Datetime
104.131.45.150 attackbotsspam
SSH Brute-Force Attack
2020-10-10 06:06:26
104.131.45.150 attackspam
Oct  9 12:08:42 santamaria sshd\[16538\]: Invalid user user1 from 104.131.45.150
Oct  9 12:08:42 santamaria sshd\[16538\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150
Oct  9 12:08:44 santamaria sshd\[16538\]: Failed password for invalid user user1 from 104.131.45.150 port 57974 ssh2
...
2020-10-09 22:13:31
104.131.45.150 attack
$f2bV_matches
2020-10-09 14:03:29
104.131.45.150 attackbots
2020-10-04 13:27:23.806264-0500  localhost sshd[92460]: Failed password for root from 104.131.45.150 port 34974 ssh2
2020-10-05 04:06:22
104.131.45.150 attack
(sshd) Failed SSH login from 104.131.45.150 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  4 02:01:54 optimus sshd[12276]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150  user=root
Oct  4 02:01:56 optimus sshd[12276]: Failed password for root from 104.131.45.150 port 39428 ssh2
Oct  4 02:14:27 optimus sshd[29613]: Invalid user student7 from 104.131.45.150
Oct  4 02:14:27 optimus sshd[29613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150 
Oct  4 02:14:29 optimus sshd[29613]: Failed password for invalid user student7 from 104.131.45.150 port 57512 ssh2
2020-10-04 19:56:44
104.131.45.150 attack
Sep 12 17:21:00 prox sshd[28018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150 
Sep 12 17:21:03 prox sshd[28018]: Failed password for invalid user chloe from 104.131.45.150 port 45598 ssh2
2020-09-13 00:04:48
104.131.45.150 attack
refused connect from 104.131.45.150 (104.131.45.150) multiples intentos de violar acceso
2020-09-12 16:05:16
104.131.45.150 attackspam
2020-09-11T23:28:14.926484abusebot-5.cloudsearch.cf sshd[19384]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150  user=root
2020-09-11T23:28:16.784083abusebot-5.cloudsearch.cf sshd[19384]: Failed password for root from 104.131.45.150 port 36014 ssh2
2020-09-11T23:32:02.067762abusebot-5.cloudsearch.cf sshd[19495]: Invalid user kevin from 104.131.45.150 port 43254
2020-09-11T23:32:02.074363abusebot-5.cloudsearch.cf sshd[19495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150
2020-09-11T23:32:02.067762abusebot-5.cloudsearch.cf sshd[19495]: Invalid user kevin from 104.131.45.150 port 43254
2020-09-11T23:32:03.565556abusebot-5.cloudsearch.cf sshd[19495]: Failed password for invalid user kevin from 104.131.45.150 port 43254 ssh2
2020-09-11T23:34:33.906263abusebot-5.cloudsearch.cf sshd[19552]: Invalid user ec2-user from 104.131.45.150 port 37400
...
2020-09-12 07:52:05
104.131.45.150 attackspambots
"Unauthorized connection attempt on SSHD detected"
2020-09-05 21:03:23
104.131.45.150 attackspam
Sep  4 22:05:53 l02a sshd[10943]: Invalid user lzy from 104.131.45.150
Sep  4 22:05:53 l02a sshd[10943]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150 
Sep  4 22:05:53 l02a sshd[10943]: Invalid user lzy from 104.131.45.150
Sep  4 22:05:55 l02a sshd[10943]: Failed password for invalid user lzy from 104.131.45.150 port 48500 ssh2
2020-09-05 05:27:16
104.131.45.150 attackbotsspam
Sep  1 11:25:58 rancher-0 sshd[1383586]: Invalid user jader from 104.131.45.150 port 47446
Sep  1 11:25:59 rancher-0 sshd[1383586]: Failed password for invalid user jader from 104.131.45.150 port 47446 ssh2
...
2020-09-01 18:16:56
104.131.45.150 attackbotsspam
detected by Fail2Ban
2020-08-26 01:17:18
104.131.45.150 attackspam
20 attempts against mh-ssh on cloud
2020-08-19 13:23:29
104.131.45.150 attackbotsspam
SSH_bulk_scanner
2020-08-16 16:37:40
104.131.45.150 attack
Lines containing failures of 104.131.45.150
Aug  3 00:07:20 shared02 sshd[17393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150  user=r.r
Aug  3 00:07:22 shared02 sshd[17393]: Failed password for r.r from 104.131.45.150 port 41584 ssh2
Aug  3 00:07:22 shared02 sshd[17393]: Received disconnect from 104.131.45.150 port 41584:11: Bye Bye [preauth]
Aug  3 00:07:22 shared02 sshd[17393]: Disconnected from authenticating user r.r 104.131.45.150 port 41584 [preauth]
Aug  3 00:18:21 shared02 sshd[23428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.45.150  user=r.r
Aug  3 00:18:23 shared02 sshd[23428]: Failed password for r.r from 104.131.45.150 port 33536 ssh2
Aug  3 00:18:23 shared02 sshd[23428]: Received disconnect from 104.131.45.150 port 33536:11: Bye Bye [preauth]
Aug  3 00:18:23 shared02 sshd[23428]: Disconnected from authenticating user r.r 104.131.45.150 port 33536........
------------------------------
2020-08-09 05:31:48
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.131.45.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18186
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.131.45.112.			IN	A

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

;; Query time: 97 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 08:19:21 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 112.45.131.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 112.45.131.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
163.172.90.3 attack
Invalid user fake from 163.172.90.3 port 55168
2020-02-26 07:13:46
114.217.141.100 attack
suspicious action Tue, 25 Feb 2020 13:32:14 -0300
2020-02-26 07:43:17
198.108.67.31 attack
Port 1311 scan denied
2020-02-26 07:43:34
2.236.104.42 attack
Automatic report - Port Scan Attack
2020-02-26 07:32:22
218.151.100.195 attackspam
Invalid user elsearch from 218.151.100.195 port 44956
2020-02-26 07:15:05
201.211.179.170 attackspam
DATE:2020-02-25 17:30:31, IP:201.211.179.170, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-02-26 07:20:51
14.226.42.197 attackbotsspam
Honeypot attack, port: 445, PTR: static.vnpt.vn.
2020-02-26 07:19:15
200.29.103.70 attackspam
20/2/25@11:32:38: FAIL: Alarm-Network address from=200.29.103.70
20/2/25@11:32:38: FAIL: Alarm-Network address from=200.29.103.70
...
2020-02-26 07:23:19
2.59.78.29 attackbotsspam
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-02-26 07:36:29
49.228.178.16 attack
Honeypot attack, port: 445, PTR: 49-228-178-0.24.nat.tls1b-cgn02.myaisfibre.com.
2020-02-26 07:32:55
217.182.77.186 attack
$f2bV_matches
2020-02-26 07:12:08
185.109.250.48 attackbotsspam
suspicious action Tue, 25 Feb 2020 13:57:14 -0300
2020-02-26 07:12:52
101.255.90.234 attackspambots
Unauthorized connection attempt from IP address 101.255.90.234 on Port 445(SMB)
2020-02-26 07:35:31
1.55.223.150 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-26 07:42:15
88.241.21.246 attackspambots
Honeypot attack, port: 81, PTR: 88.241.21.246.dynamic.ttnet.com.tr.
2020-02-26 07:26:40

Recently Reported IPs

104.131.29.136 104.131.249.90 104.131.54.6 104.131.49.141
125.102.207.15 104.131.57.253 104.131.64.51 104.131.99.130
104.140.114.91 104.131.78.158 125.114.200.197 104.149.158.11
104.145.225.3 104.144.63.166 104.149.198.143 104.149.204.16
104.149.198.144 104.149.175.82 104.149.142.237 104.152.108.9