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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.131.34.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17527
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.131.34.81.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 05:04:01 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 81.34.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 81.34.131.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
60.30.92.74 attackspambots
2019-11-25T06:21:45.613094abusebot-5.cloudsearch.cf sshd\[24073\]: Invalid user test from 60.30.92.74 port 28618
2019-11-25 20:41:11
43.240.125.195 attackbotsspam
Nov 24 23:37:54 hanapaa sshd\[30744\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.240.125.195  user=root
Nov 24 23:37:57 hanapaa sshd\[30744\]: Failed password for root from 43.240.125.195 port 43642 ssh2
Nov 24 23:45:58 hanapaa sshd\[31509\]: Invalid user Daddy from 43.240.125.195
Nov 24 23:45:58 hanapaa sshd\[31509\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.240.125.195
Nov 24 23:46:00 hanapaa sshd\[31509\]: Failed password for invalid user Daddy from 43.240.125.195 port 51326 ssh2
2019-11-25 20:26:03
221.178.156.154 attack
221.178.156.154 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 20:29:59
187.190.236.88 attack
Nov 25 12:47:39 tux-35-217 sshd\[31002\]: Invalid user dovecot from 187.190.236.88 port 43602
Nov 25 12:47:39 tux-35-217 sshd\[31002\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.190.236.88
Nov 25 12:47:42 tux-35-217 sshd\[31002\]: Failed password for invalid user dovecot from 187.190.236.88 port 43602 ssh2
Nov 25 12:51:04 tux-35-217 sshd\[31011\]: Invalid user garcon from 187.190.236.88 port 50722
Nov 25 12:51:04 tux-35-217 sshd\[31011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.190.236.88
...
2019-11-25 20:57:17
187.67.44.105 attack
187.67.44.105 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 20:20:03
103.219.112.61 attackspam
Nov 25 12:52:55 sbg01 sshd[27447]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.61
Nov 25 12:52:57 sbg01 sshd[27447]: Failed password for invalid user kallis from 103.219.112.61 port 36182 ssh2
Nov 25 13:00:53 sbg01 sshd[27469]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.61
2019-11-25 20:20:20
139.59.2.205 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-11-25 20:47:05
116.255.191.36 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-11-25 20:18:50
138.197.199.249 attack
Nov 25 07:39:41 ny01 sshd[25197]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.199.249
Nov 25 07:39:43 ny01 sshd[25197]: Failed password for invalid user simon from 138.197.199.249 port 44820 ssh2
Nov 25 07:42:52 ny01 sshd[25490]: Failed password for root from 138.197.199.249 port 34081 ssh2
2019-11-25 20:46:22
185.208.148.54 attackbots
Automatic report - Port Scan Attack
2019-11-25 20:25:40
110.43.34.48 attackbotsspam
Nov 25 10:15:26 server sshd\[25374\]: Invalid user walter from 110.43.34.48
Nov 25 10:15:26 server sshd\[25374\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.43.34.48 
Nov 25 10:15:28 server sshd\[25374\]: Failed password for invalid user walter from 110.43.34.48 port 31670 ssh2
Nov 25 10:42:22 server sshd\[32302\]: Invalid user faggion from 110.43.34.48
Nov 25 10:42:22 server sshd\[32302\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.43.34.48 
...
2019-11-25 20:22:15
115.94.109.99 attackspam
Nov 25 12:31:01 sd-53420 sshd\[4812\]: Invalid user guest from 115.94.109.99
Nov 25 12:31:01 sd-53420 sshd\[4812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.109.99
Nov 25 12:31:04 sd-53420 sshd\[4812\]: Failed password for invalid user guest from 115.94.109.99 port 37328 ssh2
Nov 25 12:38:43 sd-53420 sshd\[6040\]: Invalid user destinesavior from 115.94.109.99
Nov 25 12:38:43 sd-53420 sshd\[6040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.109.99
...
2019-11-25 20:54:58
217.182.252.161 attack
$f2bV_matches
2019-11-25 20:25:23
121.99.240.85 attackspambots
121.99.240.85 was recorded 5 times by 1 hosts attempting to connect to the following ports: 51413. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-25 20:56:51
49.118.143.212 attackbots
Automatic report - Port Scan Attack
2019-11-25 20:51:35

Recently Reported IPs

104.131.34.225 104.131.35.178 104.131.39.11 104.131.40.233
104.131.44.187 104.131.45.243 104.131.45.37 104.131.47.107
104.131.47.79 104.131.48.171 104.131.48.30 104.131.48.65
104.131.48.79 104.131.49.133 185.199.26.162 104.131.5.73
104.131.53.20 104.131.58.142 104.131.6.158 104.131.6.198