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

;; QUESTION SECTION:
;104.21.49.18.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 23:13:44 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 18.49.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 18.49.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
219.92.232.90 attackbots
firewall-block, port(s): 1433/tcp
2019-12-27 21:48:15
103.26.43.202 attack
Invalid user webadmin from 103.26.43.202 port 38986
2019-12-27 22:23:42
188.254.0.197 attackbots
Tried sshing with brute force.
2019-12-27 22:06:43
185.156.73.60 attackbotsspam
Dec 27 15:18:29 debian-2gb-nbg1-2 kernel: \[1109032.577906\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.156.73.60 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=45409 PROTO=TCP SPT=54074 DPT=49432 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-27 22:27:25
121.234.206.165 attack
Scanning
2019-12-27 22:07:46
193.33.233.254 attackbotsspam
[portscan] Port scan
2019-12-27 22:09:01
131.255.187.107 attackbots
1577427619 - 12/27/2019 07:20:19 Host: 131.255.187.107/131.255.187.107 Port: 445 TCP Blocked
2019-12-27 21:52:42
118.70.74.152 attackspambots
1577427586 - 12/27/2019 07:19:46 Host: 118.70.74.152/118.70.74.152 Port: 445 TCP Blocked
2019-12-27 22:18:49
35.185.239.108 attack
Invalid user gdm from 35.185.239.108 port 52344
2019-12-27 21:46:12
222.186.175.183 attackspambots
Dec 27 14:48:47 localhost sshd\[6848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.183  user=root
Dec 27 14:48:49 localhost sshd\[6848\]: Failed password for root from 222.186.175.183 port 33256 ssh2
Dec 27 14:48:53 localhost sshd\[6848\]: Failed password for root from 222.186.175.183 port 33256 ssh2
2019-12-27 21:52:23
182.48.106.205 attack
SSH Brute-Force reported by Fail2Ban
2019-12-27 21:47:57
202.90.198.2 attack
Dec 27 11:58:07 mail1 sshd\[13877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.90.198.2  user=root
Dec 27 11:58:09 mail1 sshd\[13877\]: Failed password for root from 202.90.198.2 port 55118 ssh2
Dec 27 12:03:06 mail1 sshd\[16119\]: Invalid user amtszeit from 202.90.198.2 port 33440
Dec 27 12:03:06 mail1 sshd\[16119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.90.198.2
Dec 27 12:03:09 mail1 sshd\[16119\]: Failed password for invalid user amtszeit from 202.90.198.2 port 33440 ssh2
...
2019-12-27 22:08:40
142.90.107.176 attack
Invalid user weblogic from 142.90.107.176 port 53148
2019-12-27 21:54:42
45.116.232.24 attack
firewall-block, port(s): 445/tcp
2019-12-27 22:10:25
112.194.128.176 attackspambots
Fail2Ban - FTP Abuse Attempt
2019-12-27 22:17:17

Recently Reported IPs

104.21.49.179 104.21.49.181 104.21.49.186 104.21.49.19
104.21.49.191 104.21.49.193 104.21.49.2 104.21.49.200
104.21.49.201 104.21.49.204 104.21.49.206 104.21.49.21
104.21.49.211 104.21.49.212 104.21.49.214 91.179.8.184
104.21.49.216 104.21.49.217 104.21.49.218 104.21.49.220