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

;; QUESTION SECTION:
;103.21.136.44.			IN	A

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

;; Query time: 79 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 02:43:38 CST 2022
;; MSG SIZE  rcvd: 106
Host info
44.136.21.103.in-addr.arpa domain name pointer invalid.static.ip.tigerdns.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.136.21.103.in-addr.arpa	name = invalid.static.ip.tigerdns.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
105.67.0.167 attackbots
Hit on /wp-login.php
2019-07-10 05:39:19
122.154.134.38 attack
Jul  9 19:05:42 Ubuntu-1404-trusty-64-minimal sshd\[27232\]: Invalid user nishiyama from 122.154.134.38
Jul  9 19:05:42 Ubuntu-1404-trusty-64-minimal sshd\[27232\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.154.134.38
Jul  9 19:05:44 Ubuntu-1404-trusty-64-minimal sshd\[27232\]: Failed password for invalid user nishiyama from 122.154.134.38 port 33842 ssh2
Jul  9 22:19:43 Ubuntu-1404-trusty-64-minimal sshd\[2885\]: Invalid user netadmin from 122.154.134.38
Jul  9 22:19:43 Ubuntu-1404-trusty-64-minimal sshd\[2885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.154.134.38
2019-07-10 05:27:03
223.133.243.28 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-07-10 05:27:24
83.143.24.27 attackspambots
proto=tcp  .  spt=43900  .  dpt=25  .     (listed on Blocklist de  Jul 08)     (393)
2019-07-10 05:53:19
80.78.64.70 attackbotsspam
80.78.64.70 - - [09/Jul/2019:15:25:58 +0200] "POST /nous HTTP/1.1" 302 370 "-" "-"
...
2019-07-10 05:29:36
126.72.82.173 attackspambots
Brute force attempt
2019-07-10 05:38:33
200.77.186.212 attackspambots
proto=tcp  .  spt=58572  .  dpt=25  .     (listed on     Github Combined on 3 lists )     (391)
2019-07-10 05:54:55
109.230.182.12 attackspambots
[portscan] Port scan
2019-07-10 06:03:36
188.166.1.123 attackbotsspam
Jul  9 23:49:28 srv-4 sshd\[25040\]: Invalid user holland from 188.166.1.123
Jul  9 23:49:28 srv-4 sshd\[25040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.1.123
Jul  9 23:49:30 srv-4 sshd\[25040\]: Failed password for invalid user holland from 188.166.1.123 port 47948 ssh2
...
2019-07-10 05:34:35
5.126.123.129 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-08 16:19:25,476 INFO [shellcode_manager] (5.126.123.129) no match, writing hexdump (1b2c9fcb828a6ac7a2ca7e05b800aa4b :2114652) - MS17010 (EternalBlue)
2019-07-10 05:32:32
201.80.108.83 attackbotsspam
Jul  9 15:22:04 herz-der-gamer sshd[32218]: Failed password for root from 201.80.108.83 port 32323 ssh2
...
2019-07-10 06:02:05
41.214.20.60 attackbotsspam
ssh failed login
2019-07-10 05:22:58
69.125.3.217 attack
DDoS on port 53 UDP
2019-07-10 05:43:43
106.110.232.202 attackbots
$f2bV_matches
2019-07-10 05:42:56
103.244.64.37 attack
09.07.2019 13:28:15 SSH access blocked by firewall
2019-07-10 05:21:19

Recently Reported IPs

103.21.143.105 103.21.150.162 103.21.150.163 103.21.180.45
103.21.149.61 103.21.183.233 103.21.58.248 103.21.58.202
103.21.55.57 103.21.59.26 103.21.59.36 103.210.123.104
103.210.106.130 103.21.79.156 103.21.59.244 103.210.72.94
103.211.177.164 103.210.4.139 103.211.217.116 103.211.217.40