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

Region: New Jersey

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.131.48.26 attack
Sep 25 23:00:01 journals sshd\[39491\]: Invalid user phion from 104.131.48.26
Sep 25 23:00:01 journals sshd\[39491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.48.26
Sep 25 23:00:03 journals sshd\[39491\]: Failed password for invalid user phion from 104.131.48.26 port 39942 ssh2
Sep 25 23:05:51 journals sshd\[40106\]: Invalid user freeswitch from 104.131.48.26
Sep 25 23:05:51 journals sshd\[40106\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.48.26
...
2020-09-26 05:02:13
104.131.48.26 attack
Sep 25 13:48:46 IngegnereFirenze sshd[22567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.48.26  user=root
...
2020-09-25 21:55:56
104.131.48.26 attackbotsspam
Ssh brute force
2020-09-25 13:33:58
104.131.48.67 attack
SSH brute force
2020-09-20 22:22:25
104.131.48.67 attack
SSH brute force
2020-09-20 14:13:58
104.131.48.67 attackbots
Sep 19 22:47:20 xeon sshd[43792]: Failed password for root from 104.131.48.67 port 33574 ssh2
2020-09-20 06:13:58
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.131.48.149
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40948
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.131.48.149.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 22 22:28:20 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 149.48.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 149.48.131.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
209.141.46.240 attackspam
Dec 31 14:52:56 work-partkepr sshd\[30055\]: User mysql from 209.141.46.240 not allowed because not listed in AllowUsers
Dec 31 14:52:56 work-partkepr sshd\[30055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.46.240  user=mysql
...
2020-01-01 00:01:37
138.68.94.173 attackbots
2019-12-31T15:42:10.838811shield sshd\[4100\]: Invalid user pass1235 from 138.68.94.173 port 51884
2019-12-31T15:42:10.843508shield sshd\[4100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.94.173
2019-12-31T15:42:12.855318shield sshd\[4100\]: Failed password for invalid user pass1235 from 138.68.94.173 port 51884 ssh2
2019-12-31T15:44:33.603106shield sshd\[4612\]: Invalid user music from 138.68.94.173 port 40518
2019-12-31T15:44:33.606559shield sshd\[4612\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.94.173
2019-12-31 23:52:19
186.67.141.213 attack
firewall-block, port(s): 9731/tcp
2019-12-31 23:55:08
118.25.196.31 attack
Dec 31 17:39:02 server sshd\[19802\]: Invalid user titanite from 118.25.196.31
Dec 31 17:39:02 server sshd\[19802\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.196.31 
Dec 31 17:39:04 server sshd\[19802\]: Failed password for invalid user titanite from 118.25.196.31 port 55878 ssh2
Dec 31 17:53:07 server sshd\[22937\]: Invalid user monitor from 118.25.196.31
Dec 31 17:53:07 server sshd\[22937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.196.31 
...
2019-12-31 23:52:49
195.177.241.147 attackbots
port scan and connect, tcp 1433 (ms-sql-s)
2020-01-01 00:27:01
91.209.54.54 attackspam
3x Failed Password
2020-01-01 00:02:44
122.224.20.214 attack
SMB Server BruteForce Attack
2020-01-01 00:21:03
125.124.38.96 attack
" "
2020-01-01 00:30:29
41.82.3.200 attackspambots
Unauthorized IMAP connection attempt
2019-12-31 23:48:30
185.150.190.226 attack
firewall-block, port(s): 11211/udp
2020-01-01 00:13:41
199.195.249.6 attackbotsspam
Dec 31 16:00:55 server sshd[30234]: Failed password for root from 199.195.249.6 port 53520 ssh2
Dec 31 16:20:08 server sshd[30861]: User lp from 199.195.249.6 not allowed because not listed in AllowUsers
Dec 31 16:20:10 server sshd[30861]: Failed password for invalid user lp from 199.195.249.6 port 56816 ssh2
2019-12-31 23:46:25
103.74.111.70 attackspam
firewall-block, port(s): 445/tcp
2019-12-31 23:56:58
78.153.49.38 attack
SSH Brute-Forcing (server1)
2020-01-01 00:26:27
87.120.234.6 attackbotsspam
Automatic report - Port Scan Attack
2020-01-01 00:02:59
129.213.194.201 attack
Dec 31 15:53:05 vpn01 sshd[11484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.213.194.201
Dec 31 15:53:06 vpn01 sshd[11484]: Failed password for invalid user 12345678 from 129.213.194.201 port 54288 ssh2
...
2019-12-31 23:53:48

Recently Reported IPs

104.131.46.37 104.131.53.127 104.131.56.83 104.131.59.46
104.131.67.221 104.131.67.4 104.131.67.83 104.131.7.119
104.131.72.142 62.58.173.103 104.131.73.215 104.131.74.223
104.131.76.235 104.131.77.115 104.131.77.52 104.131.79.89
104.131.79.95 104.144.94.3 104.144.94.30 104.144.95.162