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

Region: Fujian

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

;; QUESTION SECTION:
;121.207.145.103.		IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 11:15:00 CST 2025
;; MSG SIZE  rcvd: 108
Host info
103.145.207.121.in-addr.arpa domain name pointer 103.145.207.121.broad.xm.fj.dynamic.163data.com.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
103.145.207.121.in-addr.arpa	name = 103.145.207.121.broad.xm.fj.dynamic.163data.com.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.128.213.126 attack
2019-12-25T21:33:30.440374abusebot-3.cloudsearch.cf sshd[5178]: Invalid user hirn from 178.128.213.126 port 59194
2019-12-25T21:33:30.446284abusebot-3.cloudsearch.cf sshd[5178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.213.126
2019-12-25T21:33:30.440374abusebot-3.cloudsearch.cf sshd[5178]: Invalid user hirn from 178.128.213.126 port 59194
2019-12-25T21:33:32.082688abusebot-3.cloudsearch.cf sshd[5178]: Failed password for invalid user hirn from 178.128.213.126 port 59194 ssh2
2019-12-25T21:35:36.647648abusebot-3.cloudsearch.cf sshd[5222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.213.126  user=root
2019-12-25T21:35:38.586923abusebot-3.cloudsearch.cf sshd[5222]: Failed password for root from 178.128.213.126 port 51582 ssh2
2019-12-25T21:37:46.620837abusebot-3.cloudsearch.cf sshd[5285]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.
...
2019-12-26 06:39:38
51.38.232.93 attack
Dec 25 22:35:07 dev0-dcde-rnet sshd[31121]: Failed password for lp from 51.38.232.93 port 47386 ssh2
Dec 25 22:40:59 dev0-dcde-rnet sshd[31246]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.232.93
Dec 25 22:41:00 dev0-dcde-rnet sshd[31246]: Failed password for invalid user csp from 51.38.232.93 port 36850 ssh2
2019-12-26 06:09:42
202.131.126.142 attackbotsspam
Dec 25 21:09:08 XXX sshd[60074]: Invalid user lz from 202.131.126.142 port 33442
2019-12-26 06:04:50
200.98.64.68 attackspambots
Unauthorized connection attempt detected from IP address 200.98.64.68 to port 1433
2019-12-26 06:08:35
115.76.173.165 attackbots
Invalid user admin from 115.76.173.165 port 50380
2019-12-26 06:18:07
157.34.88.127 attack
Invalid user admin from 157.34.88.127 port 55386
2019-12-26 06:23:29
37.187.6.235 attack
SSH Login Bruteforce
2019-12-26 06:30:29
54.169.180.190 attackspambots
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 06:14:02
86.237.208.3 attackspambots
Dec 25 15:20:42 xxxxxxx0 sshd[1046]: Invalid user beaumont from 86.237.208.3 port 53664
Dec 25 15:20:45 xxxxxxx0 sshd[1046]: Failed password for invalid user beaumont from 86.237.208.3 port 53664 ssh2
Dec 25 15:30:55 xxxxxxx0 sshd[2485]: Invalid user copple from 86.237.208.3 port 46668
Dec 25 15:30:57 xxxxxxx0 sshd[2485]: Failed password for invalid user copple from 86.237.208.3 port 46668 ssh2
Dec 25 15:41:12 xxxxxxx0 sshd[4031]: Invalid user smmsp from 86.237.208.3 port 39678

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=86.237.208.3
2019-12-26 06:25:13
159.203.36.18 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2019-12-26 06:06:43
195.161.162.250 attack
Unauthorized connection attempt from IP address 195.161.162.250 on Port 445(SMB)
2019-12-26 06:42:20
51.161.12.231 attackspambots
Dec 25 23:28:29 debian-2gb-nbg1-2 kernel: \[965641.454896\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.161.12.231 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=10978 PROTO=TCP SPT=32767 DPT=8545 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-26 06:34:21
47.99.64.181 attack
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 06:23:43
172.86.70.163 attack
Dec 25 15:46:13 mxgate1 postfix/postscreen[4160]: CONNECT from [172.86.70.163]:40831 to [176.31.12.44]:25
Dec 25 15:46:13 mxgate1 postfix/dnsblog[4161]: addr 172.86.70.163 listed by domain zen.spamhaus.org as 127.0.0.3
Dec 25 15:46:13 mxgate1 postfix/dnsblog[4164]: addr 172.86.70.163 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Dec 25 15:46:19 mxgate1 postfix/postscreen[4160]: DNSBL rank 3 for [172.86.70.163]:40831
Dec x@x
Dec 25 15:46:20 mxgate1 postfix/postscreen[4160]: DISCONNECT [172.86.70.163]:40831


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=172.86.70.163
2019-12-26 06:20:21
109.237.4.16 attackbotsspam
Unauthorized connection attempt from IP address 109.237.4.16 on Port 445(SMB)
2019-12-26 06:41:06

Recently Reported IPs

232.89.61.20 115.79.49.95 215.161.182.242 214.96.114.102
170.202.59.96 30.135.80.2 61.15.56.94 157.209.128.60
129.250.183.219 21.253.209.217 160.108.228.227 199.28.53.85
187.159.31.96 138.26.66.225 196.219.131.134 94.211.89.141
224.161.210.137 204.186.147.95 212.154.89.242 185.100.52.34