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: China

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

;; QUESTION SECTION:
;121.9.103.136.			IN	A

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

;; Query time: 244 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 10:27:31 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 136.103.9.121.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 136.103.9.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.155.5.132 attackbots
Nov 10 13:55:36 ArkNodeAT sshd\[13850\]: Invalid user ts from 139.155.5.132
Nov 10 13:55:36 ArkNodeAT sshd\[13850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.5.132
Nov 10 13:55:38 ArkNodeAT sshd\[13850\]: Failed password for invalid user ts from 139.155.5.132 port 41058 ssh2
2019-11-10 21:09:10
148.3.113.41 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/148.3.113.41/ 
 
 ES - 1H : (43)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : ES 
 NAME ASN : ASN12430 
 
 IP : 148.3.113.41 
 
 CIDR : 148.3.0.0/16 
 
 PREFIX COUNT : 131 
 
 UNIQUE IP COUNT : 3717120 
 
 
 ATTACKS DETECTED ASN12430 :  
  1H - 1 
  3H - 1 
  6H - 5 
 12H - 8 
 24H - 15 
 
 DateTime : 2019-11-10 07:23:08 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-10 21:19:19
193.112.108.135 attackbots
Nov 10 11:22:18 server sshd\[28590\]: User root from 193.112.108.135 not allowed because listed in DenyUsers
Nov 10 11:22:18 server sshd\[28590\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.108.135  user=root
Nov 10 11:22:20 server sshd\[28590\]: Failed password for invalid user root from 193.112.108.135 port 35044 ssh2
Nov 10 11:26:41 server sshd\[9742\]: User root from 193.112.108.135 not allowed because listed in DenyUsers
Nov 10 11:26:41 server sshd\[9742\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.108.135  user=root
2019-11-10 21:16:47
221.217.49.147 attack
Nov 10 13:42:03 h2177944 sshd\[15455\]: Invalid user oracle from 221.217.49.147 port 36344
Nov 10 13:42:03 h2177944 sshd\[15455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.217.49.147
Nov 10 13:42:05 h2177944 sshd\[15455\]: Failed password for invalid user oracle from 221.217.49.147 port 36344 ssh2
Nov 10 14:04:25 h2177944 sshd\[16829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.217.49.147  user=root
...
2019-11-10 21:46:30
54.39.191.188 attackspam
Nov 10 14:21:43 markkoudstaal sshd[10159]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.191.188
Nov 10 14:21:45 markkoudstaal sshd[10159]: Failed password for invalid user postmaster from 54.39.191.188 port 42990 ssh2
Nov 10 14:25:43 markkoudstaal sshd[10436]: Failed password for root from 54.39.191.188 port 54156 ssh2
2019-11-10 21:31:25
68.183.193.46 attackbots
SSH invalid-user multiple login attempts
2019-11-10 21:20:43
209.97.168.118 attackbotsspam
Nov 10 06:03:53 ws19vmsma01 sshd[65648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.168.118
Nov 10 06:03:55 ws19vmsma01 sshd[65648]: Failed password for invalid user rv from 209.97.168.118 port 42664 ssh2
...
2019-11-10 21:25:13
45.118.144.31 attackbots
IP blocked
2019-11-10 21:35:35
71.6.147.254 attackspambots
8010/tcp 3388/tcp 4064/tcp...
[2019-09-10/11-10]166pkt,113pt.(tcp),17pt.(udp)
2019-11-10 21:15:20
192.241.99.226 attackbots
192.241.99.226 was recorded 7 times by 7 hosts attempting to connect to the following ports: 50022. Incident counter (4h, 24h, all-time): 7, 23, 105
2019-11-10 21:18:00
209.17.97.58 attack
8888/tcp 3000/tcp 4567/tcp...
[2019-09-10/11-09]109pkt,13pt.(tcp),1pt.(udp)
2019-11-10 21:22:11
148.70.56.123 attackbotsspam
Nov 10 10:59:32 sticky sshd\[20284\]: Invalid user 0 from 148.70.56.123 port 37800
Nov 10 10:59:32 sticky sshd\[20284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.56.123
Nov 10 10:59:34 sticky sshd\[20284\]: Failed password for invalid user 0 from 148.70.56.123 port 37800 ssh2
Nov 10 11:04:28 sticky sshd\[20466\]: Invalid user calculator from 148.70.56.123 port 47004
Nov 10 11:04:28 sticky sshd\[20466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.56.123
...
2019-11-10 21:46:01
185.143.223.38 attack
2019-11-10T14:08:19.759913+01:00 lumpi kernel: [3213679.065644] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=185.143.223.38 DST=172.31.1.100 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=24933 PROTO=TCP SPT=46957 DPT=33722 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-10 21:19:02
92.124.217.94 attackspambots
$f2bV_matches
2019-11-10 21:38:03
91.134.248.211 attackbotsspam
SQL Injection attack
2019-11-10 21:26:32

Recently Reported IPs

222.80.182.181 41.52.212.204 45.112.14.12 48.100.157.35
120.112.130.34 2.211.19.5 46.75.123.45 227.132.68.160
104.239.194.233 197.242.13.125 132.143.209.63 253.200.59.119
94.231.242.131 69.61.104.226 222.80.18.75 204.143.232.95
67.225.66.103 144.191.157.105 116.236.0.139 47.41.24.111