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

;; QUESTION SECTION:
;104.81.57.96.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:31:59 CST 2023
;; MSG SIZE  rcvd: 105
Host info
96.57.81.104.in-addr.arpa domain name pointer a104-81-57-96.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
96.57.81.104.in-addr.arpa	name = a104-81-57-96.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.207.181.202 attackbotsspam
Honeypot attack, port: 445, PTR: 190-207-181-202.dyn.dsl.cantv.net.
2019-11-13 01:03:21
45.136.109.82 attack
Nov 12 18:03:37 h2177944 kernel: \[6453755.573830\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.109.82 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=35207 PROTO=TCP SPT=56799 DPT=8944 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 12 18:04:07 h2177944 kernel: \[6453785.086582\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.109.82 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=23504 PROTO=TCP SPT=56799 DPT=8371 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 12 18:05:05 h2177944 kernel: \[6453843.259422\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.109.82 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=24781 PROTO=TCP SPT=56799 DPT=9832 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 12 18:05:15 h2177944 kernel: \[6453853.116786\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.109.82 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=33534 PROTO=TCP SPT=56799 DPT=8186 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov 12 18:06:08 h2177944 kernel: \[6453906.529866\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.109.82 DST=85.214.117.9
2019-11-13 01:07:15
159.203.201.12 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-13 01:05:48
185.143.223.213 attackbotsspam
Port scan
2019-11-13 01:10:47
180.68.177.209 attack
Fail2Ban Ban Triggered
2019-11-13 00:55:24
40.83.171.103 attack
firewall-block, port(s): 3306/tcp
2019-11-13 00:39:51
123.13.15.114 attackbots
19/11/12@09:42:14: FAIL: IoT-Telnet address from=123.13.15.114
...
2019-11-13 01:08:25
173.230.226.254 attackspam
port 22
2019-11-13 00:42:07
201.28.8.163 attackbotsspam
SSH authentication failure x 6 reported by Fail2Ban
...
2019-11-13 01:12:13
101.230.236.177 attack
Nov 12 06:17:13 hpm sshd\[26554\]: Invalid user tyeanna from 101.230.236.177
Nov 12 06:17:13 hpm sshd\[26554\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.236.177
Nov 12 06:17:15 hpm sshd\[26554\]: Failed password for invalid user tyeanna from 101.230.236.177 port 52968 ssh2
Nov 12 06:21:14 hpm sshd\[26878\]: Invalid user richie from 101.230.236.177
Nov 12 06:21:14 hpm sshd\[26878\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.236.177
2019-11-13 00:34:06
42.234.212.7 attackspam
Honeypot attack, port: 23, PTR: hn.kd.ny.adsl.
2019-11-13 01:11:54
217.164.64.186 attackbotsspam
217.164.64.186 was recorded 5 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-13 00:43:47
40.65.184.154 attack
st-nyc1-01 recorded 3 login violations from 40.65.184.154 and was blocked at 2019-11-12 16:30:48. 40.65.184.154 has been blocked on 9 previous occasions. 40.65.184.154's first attempt was recorded at 2019-11-12 14:08:58
2019-11-13 00:31:50
182.61.54.213 attack
Nov 12 15:50:16 localhost sshd\[13291\]: Invalid user 12 from 182.61.54.213
Nov 12 15:50:16 localhost sshd\[13291\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.54.213
Nov 12 15:50:18 localhost sshd\[13291\]: Failed password for invalid user 12 from 182.61.54.213 port 43702 ssh2
Nov 12 15:55:28 localhost sshd\[13583\]: Invalid user \&\&\&\&\& from 182.61.54.213
Nov 12 15:55:28 localhost sshd\[13583\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.54.213
...
2019-11-13 00:30:58
104.243.41.97 attackbotsspam
Nov 12 05:09:20 sachi sshd\[7337\]: Invalid user fruen from 104.243.41.97
Nov 12 05:09:20 sachi sshd\[7337\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.243.41.97
Nov 12 05:09:22 sachi sshd\[7337\]: Failed password for invalid user fruen from 104.243.41.97 port 35972 ssh2
Nov 12 05:12:38 sachi sshd\[7630\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.243.41.97  user=root
Nov 12 05:12:39 sachi sshd\[7630\]: Failed password for root from 104.243.41.97 port 42508 ssh2
2019-11-13 00:50:26

Recently Reported IPs

104.81.220.180 104.81.20.209 104.81.24.228 104.81.183.226
104.81.246.167 104.81.73.234 104.81.42.122 104.81.216.174
104.82.114.182 104.81.7.113 104.81.25.74 104.81.97.84
104.81.62.18 104.81.94.149 104.80.73.95 104.81.45.38
104.82.112.64 104.82.120.35 104.81.74.129 104.81.79.57