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

;; QUESTION SECTION:
;104.21.13.102.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 17:50:01 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 102.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 102.13.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
50.63.163.199 attackbots
//site/wp-login.php
2019-12-29 21:07:23
85.237.61.85 attack
19/12/29@01:26:08: FAIL: Alarm-Network address from=85.237.61.85
19/12/29@01:26:08: FAIL: Alarm-Network address from=85.237.61.85
...
2019-12-29 21:01:40
134.209.156.57 attackspambots
$f2bV_matches
2019-12-29 20:52:03
222.186.42.4 attackbots
$f2bV_matches
2019-12-29 20:41:59
185.220.101.46 attack
Automatic report - Banned IP Access
2019-12-29 20:48:22
106.13.144.164 attackbotsspam
ssh failed login
2019-12-29 21:14:09
188.208.57.30 attackbotsspam
1577600805 - 12/29/2019 07:26:45 Host: 188.208.57.30/188.208.57.30 Port: 445 TCP Blocked
2019-12-29 20:40:06
178.128.59.109 attackbots
Dec 29 13:33:40 DAAP sshd[31180]: Invalid user grenness from 178.128.59.109 port 57804
Dec 29 13:33:40 DAAP sshd[31180]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.59.109
Dec 29 13:33:40 DAAP sshd[31180]: Invalid user grenness from 178.128.59.109 port 57804
Dec 29 13:33:42 DAAP sshd[31180]: Failed password for invalid user grenness from 178.128.59.109 port 57804 ssh2
Dec 29 13:38:15 DAAP sshd[31242]: Invalid user test from 178.128.59.109 port 60636
...
2019-12-29 21:14:30
192.169.158.224 attackspambots
192.169.158.224 - - [29/Dec/2019:07:33:07 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
192.169.158.224 - - [29/Dec/2019:07:33:07 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-12-29 20:42:51
190.85.15.251 attackbotsspam
Dec 29 09:00:22 localhost sshd\[30246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.15.251  user=root
Dec 29 09:00:24 localhost sshd\[30246\]: Failed password for root from 190.85.15.251 port 40899 ssh2
Dec 29 09:04:06 localhost sshd\[30289\]: Invalid user yash from 190.85.15.251
Dec 29 09:04:06 localhost sshd\[30289\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.15.251
Dec 29 09:04:08 localhost sshd\[30289\]: Failed password for invalid user yash from 190.85.15.251 port 46947 ssh2
...
2019-12-29 20:38:30
89.248.168.202 attack
Dec 29 13:28:27 debian-2gb-nbg1-2 kernel: \[1275219.426745\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.168.202 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=49214 PROTO=TCP SPT=40344 DPT=9732 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-29 20:32:12
92.246.17.5 attack
2019-12-28 UTC: 1x - root
2019-12-29 21:09:42
117.240.172.19 attack
Dec 29 12:35:09 localhost sshd\[47767\]: Invalid user bovigny from 117.240.172.19 port 59431
Dec 29 12:35:09 localhost sshd\[47767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.240.172.19
Dec 29 12:35:11 localhost sshd\[47767\]: Failed password for invalid user bovigny from 117.240.172.19 port 59431 ssh2
Dec 29 12:38:36 localhost sshd\[47892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.240.172.19  user=root
Dec 29 12:38:38 localhost sshd\[47892\]: Failed password for root from 117.240.172.19 port 44297 ssh2
...
2019-12-29 20:45:32
120.0.233.169 attackbotsspam
Sun Dec 29 07:26:32 2019 [pid 15430] [anonymous] FAIL LOGIN: Client "120.0.233.169"
Sun Dec 29 07:26:42 2019 [pid 15432] [notgoodbutcrazy] FAIL LOGIN: Client "120.0.233.169"
Sun Dec 29 07:26:47 2019 [pid 15434] [notgoodbutcrazy] FAIL LOGIN: Client "120.0.233.169"
Sun Dec 29 07:26:51 2019 [pid 15439] [www] FAIL LOGIN: Client "120.0.233.169"
Sun Dec 29 07:26:56 2019 [pid 15442] [notgoodbutcrazy] FAIL LOGIN: Client "120.0.233.169"
Sun Dec 29 07:26:56 2019 [pid 15444] [www] FAIL LOGIN: Client "120.0.233.169"
2019-12-29 20:35:03
58.246.187.102 attack
Dec 29 12:03:02 [snip] sshd[31944]: Invalid user neveu from 58.246.187.102 port 19648
Dec 29 12:03:02 [snip] sshd[31944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.246.187.102
Dec 29 12:03:03 [snip] sshd[31944]: Failed password for invalid user neveu from 58.246.187.102 port 19648 ssh2[...]
2019-12-29 20:34:15

Recently Reported IPs

104.21.12.96 104.21.13.103 239.201.135.105 104.21.13.111
104.21.13.113 104.21.13.116 40.123.134.154 125.27.204.226
104.21.13.121 104.21.13.122 104.21.13.124 104.21.13.125
104.21.13.13 243.186.233.167 104.21.13.130 104.21.13.136
104.21.13.14 104.21.13.142 104.21.13.144 104.21.13.145