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.20.9.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30860
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.20.9.81.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 05:21:56 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 81.9.20.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.9.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.94.143.226 attackbotsspam
2019-10-05T05:44:54.589022abusebot-7.cloudsearch.cf sshd\[23751\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.94.143.226  user=root
2019-10-05 16:35:10
112.84.91.35 attack
Brute force attempt
2019-10-05 16:50:17
134.209.56.60 attackbotsspam
Oct  5 10:18:25 v22019058497090703 sshd[28551]: Failed password for root from 134.209.56.60 port 33116 ssh2
Oct  5 10:22:21 v22019058497090703 sshd[28870]: Failed password for root from 134.209.56.60 port 43014 ssh2
...
2019-10-05 16:28:28
213.100.250.96 attackbots
(sshd) Failed SSH login from 213.100.250.96 (EE/Estonia/-/-/static-213-100-250-96.cust.tele2.ee/[AS1257 TELE2]): 1 in the last 3600 secs
2019-10-05 16:35:26
111.230.53.144 attackspam
Oct  5 13:18:35 gw1 sshd[2850]: Failed password for root from 111.230.53.144 port 55326 ssh2
...
2019-10-05 16:30:30
61.172.238.14 attack
Sep 14 18:25:40 microserver sshd[13784]: Invalid user guest from 61.172.238.14 port 52850
Sep 14 18:25:40 microserver sshd[13784]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.172.238.14
Sep 14 18:25:42 microserver sshd[13784]: Failed password for invalid user guest from 61.172.238.14 port 52850 ssh2
Sep 14 18:28:53 microserver sshd[14017]: Invalid user locate from 61.172.238.14 port 49478
Sep 14 18:28:53 microserver sshd[14017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.172.238.14
Sep 14 18:42:04 microserver sshd[16038]: Invalid user wj from 61.172.238.14 port 35992
Sep 14 18:42:04 microserver sshd[16038]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.172.238.14
Sep 14 18:42:05 microserver sshd[16038]: Failed password for invalid user wj from 61.172.238.14 port 35992 ssh2
Sep 14 18:45:22 microserver sshd[16380]: Invalid user tani from 61.172.238.14 port 60862
Sep 14 18:4
2019-10-05 16:52:53
45.224.105.61 attackspam
$f2bV_matches
2019-10-05 16:20:05
118.24.55.171 attackbots
Failed password for root from 118.24.55.171 port 1836 ssh2
2019-10-05 16:36:29
51.75.65.209 attack
SSH brute-force: detected 13 distinct usernames within a 24-hour window.
2019-10-05 16:43:22
89.163.249.200 attackspambots
firewall-block, port(s): 3389/tcp
2019-10-05 16:36:50
163.172.163.79 attackbotsspam
Oct  5 08:31:56 vps647732 sshd[3780]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.163.79
Oct  5 08:31:59 vps647732 sshd[3780]: Failed password for invalid user Cosmetic2017 from 163.172.163.79 port 43364 ssh2
...
2019-10-05 16:33:20
144.217.214.13 attack
Oct  4 19:22:04 auw2 sshd\[15547\]: Invalid user Qwerty\#123 from 144.217.214.13
Oct  4 19:22:04 auw2 sshd\[15547\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip13.ip-144-217-214.net
Oct  4 19:22:07 auw2 sshd\[15547\]: Failed password for invalid user Qwerty\#123 from 144.217.214.13 port 40774 ssh2
Oct  4 19:26:48 auw2 sshd\[15963\]: Invalid user 123Gate from 144.217.214.13
Oct  4 19:26:48 auw2 sshd\[15963\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip13.ip-144-217-214.net
2019-10-05 16:51:46
125.74.10.146 attack
Oct  5 06:10:01 microserver sshd[25957]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.74.10.146  user=root
Oct  5 06:10:03 microserver sshd[25957]: Failed password for root from 125.74.10.146 port 43109 ssh2
Oct  5 06:14:37 microserver sshd[26635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.74.10.146  user=root
Oct  5 06:14:39 microserver sshd[26635]: Failed password for root from 125.74.10.146 port 60286 ssh2
Oct  5 06:19:15 microserver sshd[27279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.74.10.146  user=root
Oct  5 06:32:45 microserver sshd[29292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.74.10.146  user=root
Oct  5 06:32:47 microserver sshd[29292]: Failed password for root from 125.74.10.146 port 44287 ssh2
Oct  5 06:37:22 microserver sshd[29995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid
2019-10-05 16:26:21
104.143.83.242 attackspam
Port scan attempt detected by AWS-CCS, CTS, India
2019-10-05 16:17:36
123.206.81.59 attack
$f2bV_matches
2019-10-05 16:18:01

Recently Reported IPs

104.20.85.169 104.20.92.139 104.20.91.33 104.20.90.31
104.20.92.33 104.20.95.141 104.20.96.110 104.200.21.158
104.200.26.31 104.200.29.133 104.206.203.236 104.206.225.200
104.200.17.119 104.207.146.80 104.207.152.148 104.201.34.61
104.201.34.60 104.201.35.163 104.207.230.81 104.207.235.203