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

;; QUESTION SECTION:
;104.21.13.162.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 17:51:55 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 162.13.21.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 162.13.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.235.99.250 attackspam
Oct 24 14:33:24 icinga sshd[22407]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.235.99.250 
Oct 24 14:33:24 icinga sshd[22406]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.235.99.250 
Oct 24 14:33:26 icinga sshd[22407]: Failed password for invalid user pi from 176.235.99.250 port 60186 ssh2
Oct 24 14:33:26 icinga sshd[22406]: Failed password for invalid user pi from 176.235.99.250 port 60184 ssh2
...
2019-10-24 21:44:38
52.166.95.124 attack
Invalid user t from 52.166.95.124 port 13556
2019-10-24 21:56:45
104.236.224.69 attack
Invalid user wwwrun from 104.236.224.69 port 48973
2019-10-24 21:49:55
106.241.16.119 attack
$f2bV_matches
2019-10-24 22:14:53
103.40.235.233 attack
Invalid user zhuan from 103.40.235.233 port 40950
2019-10-24 22:16:49
80.178.115.146 attack
SSH Bruteforce
2019-10-24 21:54:19
138.68.242.220 attackbots
Oct 24 15:17:56 server sshd\[8588\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.242.220  user=root
Oct 24 15:17:58 server sshd\[8588\]: Failed password for root from 138.68.242.220 port 57986 ssh2
Oct 24 15:23:37 server sshd\[9897\]: Invalid user jomar from 138.68.242.220
Oct 24 15:23:37 server sshd\[9897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.242.220 
Oct 24 15:23:39 server sshd\[9897\]: Failed password for invalid user jomar from 138.68.242.220 port 39742 ssh2
...
2019-10-24 22:09:27
41.76.169.43 attackspam
Invalid user developer from 41.76.169.43 port 55214
2019-10-24 22:25:15
200.41.86.59 attack
Invalid user forums from 200.41.86.59 port 54940
2019-10-24 22:02:00
109.88.44.32 attackspambots
Invalid user pi from 109.88.44.32 port 41991
2019-10-24 22:14:37
95.85.60.251 attackspam
Invalid user nagesh from 95.85.60.251 port 59870
2019-10-24 21:51:29
51.38.37.128 attackspambots
Oct 24 16:09:47 SilenceServices sshd[28226]: Failed password for root from 51.38.37.128 port 35202 ssh2
Oct 24 16:13:26 SilenceServices sshd[29174]: Failed password for root from 51.38.37.128 port 55530 ssh2
2019-10-24 22:25:00
14.186.50.31 attackbots
Invalid user admin from 14.186.50.31 port 41117
2019-10-24 22:27:09
195.214.223.84 attackbots
Invalid user support from 195.214.223.84 port 34832
2019-10-24 22:02:37
101.124.6.112 attack
Invalid user admin from 101.124.6.112 port 37804
2019-10-24 21:51:09

Recently Reported IPs

104.21.13.16 243.101.3.90 104.21.13.163 104.21.13.166
104.21.13.171 104.21.13.174 104.21.13.176 104.21.13.178
104.21.13.179 104.21.13.185 104.21.13.188 207.230.187.169
104.21.13.190 104.21.13.192 104.21.13.194 104.21.13.197
104.21.13.198 0.125.7.104 104.21.13.199 104.21.13.2