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

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:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '119.248.0.0 - 119.251.255.255'

% Abuse contact for '119.248.0.0 - 119.251.255.255' is 'zhaoyz3@chinaunicom.cn'

inetnum:        119.248.0.0 - 119.251.255.255
netname:        UNICOM-HE
descr:          China Unicom Heibei Province Network
descr:          China Unicom
country:        CN
admin-c:        CH1302-AP
tech-c:         KL984-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CNCGROUP-HE
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2025-01-22T13:18:20Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         zhaoyz3@chinaunicom.cn
abuse-mailbox:  zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        zhaoyz3@chinaunicom.cn is invalid
mnt-by:         MAINT-CNCGROUP
last-modified:  2025-10-03T06:12:01Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         zhaoyz3@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        zhaoyz3@chinaunicom.cn is invalid
abuse-mailbox:  zhaoyz3@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-10T13:08:11Z
source:         APNIC

person:         ChinaUnicom Hostmaster
nic-hdl:        CH1302-AP
e-mail:         hqs-ipabuse@chinaunicom.cn
address:        No.21,Jin-Rong Street
address:        Beijing,100033
address:        P.R.China
phone:          +86-10-66259764
fax-no:         +86-10-66259764
country:        CN
mnt-by:         MAINT-CNCGROUP
last-modified:  2017-08-17T06:13:16Z
source:         APNIC

person:         Kong Lingfei
nic-hdl:        KL984-AP
e-mail:         konglf5@chinaunicom.cn
address:        45, Guang An Street, Shi Jiazhuang City, HeBei Province,050011,CN
phone:          +86-311-86681601
fax-no:         +86-311-86689210
country:        cn
mnt-by:         MAINT-CNCGROUP-HE
last-modified:  2009-02-06T02:31:32Z
source:         APNIC

% Information related to '119.248.0.0/14AS4837'

route:          119.248.0.0/14
descr:          China Unicom China169 Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2017-05-05T06:28:01Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.34 (WHOIS-AU4)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.249.100.109
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1705
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.249.100.109.		IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Oct 13 03:00:19 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 109.100.249.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 109.100.249.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.24.194.43 attack
Invalid user user from 85.24.194.43 port 42808
2020-06-15 15:03:25
68.183.181.7 attack
20 attempts against mh-ssh on echoip
2020-06-15 15:39:35
104.248.71.7 attackspambots
2020-06-15T03:49:31.150940dmca.cloudsearch.cf sshd[9593]: Invalid user wp from 104.248.71.7 port 54534
2020-06-15T03:49:31.156537dmca.cloudsearch.cf sshd[9593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
2020-06-15T03:49:31.150940dmca.cloudsearch.cf sshd[9593]: Invalid user wp from 104.248.71.7 port 54534
2020-06-15T03:49:33.708434dmca.cloudsearch.cf sshd[9593]: Failed password for invalid user wp from 104.248.71.7 port 54534 ssh2
2020-06-15T03:53:05.382633dmca.cloudsearch.cf sshd[10077]: Invalid user ec2-user from 104.248.71.7 port 52528
2020-06-15T03:53:05.388026dmca.cloudsearch.cf sshd[10077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
2020-06-15T03:53:05.382633dmca.cloudsearch.cf sshd[10077]: Invalid user ec2-user from 104.248.71.7 port 52528
2020-06-15T03:53:07.317751dmca.cloudsearch.cf sshd[10077]: Failed password for invalid user ec2-user from 104.248.71.7 port 525
...
2020-06-15 15:27:00
218.92.0.220 attackspambots
Jun 15 09:24:37 v22018053744266470 sshd[17320]: Failed password for root from 218.92.0.220 port 20171 ssh2
Jun 15 09:24:47 v22018053744266470 sshd[17330]: Failed password for root from 218.92.0.220 port 51646 ssh2
...
2020-06-15 15:38:25
92.207.180.50 attackspambots
Jun 14 20:32:46 Tower sshd[7292]: refused connect from 103.45.161.100 (103.45.161.100)
Jun 15 03:02:40 Tower sshd[7292]: Connection from 92.207.180.50 port 57062 on 192.168.10.220 port 22 rdomain ""
Jun 15 03:02:40 Tower sshd[7292]: Invalid user user from 92.207.180.50 port 57062
Jun 15 03:02:40 Tower sshd[7292]: error: Could not get shadow information for NOUSER
Jun 15 03:02:40 Tower sshd[7292]: Failed password for invalid user user from 92.207.180.50 port 57062 ssh2
Jun 15 03:02:41 Tower sshd[7292]: Received disconnect from 92.207.180.50 port 57062:11: Bye Bye [preauth]
Jun 15 03:02:41 Tower sshd[7292]: Disconnected from invalid user user 92.207.180.50 port 57062 [preauth]
2020-06-15 15:41:37
157.230.61.132 attack
Jun 15 10:49:59 itv-usvr-01 sshd[1742]: Invalid user deploy from 157.230.61.132
Jun 15 10:49:59 itv-usvr-01 sshd[1742]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.61.132
Jun 15 10:49:59 itv-usvr-01 sshd[1742]: Invalid user deploy from 157.230.61.132
Jun 15 10:50:00 itv-usvr-01 sshd[1742]: Failed password for invalid user deploy from 157.230.61.132 port 47066 ssh2
Jun 15 10:52:54 itv-usvr-01 sshd[1850]: Invalid user printer from 157.230.61.132
2020-06-15 15:39:19
113.184.216.127 attackbots
20/6/14@23:53:02: FAIL: Alarm-Network address from=113.184.216.127
20/6/14@23:53:02: FAIL: Alarm-Network address from=113.184.216.127
...
2020-06-15 15:30:26
35.201.140.93 attackbots
Jun 15 02:24:27 r.ca sshd[8309]: Failed password for root from 35.201.140.93 port 59894 ssh2
2020-06-15 15:13:46
222.186.180.130 attackbotsspam
(sshd) Failed SSH login from 222.186.180.130 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 15 09:45:46 amsweb01 sshd[27495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130  user=root
Jun 15 09:45:48 amsweb01 sshd[27495]: Failed password for root from 222.186.180.130 port 17606 ssh2
Jun 15 09:45:51 amsweb01 sshd[27495]: Failed password for root from 222.186.180.130 port 17606 ssh2
Jun 15 09:45:53 amsweb01 sshd[27495]: Failed password for root from 222.186.180.130 port 17606 ssh2
Jun 15 09:45:56 amsweb01 sshd[27497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130  user=root
2020-06-15 15:48:10
138.68.226.175 attackbots
2020-06-15 06:08:28,312 fail2ban.actions        [937]: NOTICE  [sshd] Ban 138.68.226.175
2020-06-15 06:41:37,027 fail2ban.actions        [937]: NOTICE  [sshd] Ban 138.68.226.175
2020-06-15 07:18:03,817 fail2ban.actions        [937]: NOTICE  [sshd] Ban 138.68.226.175
2020-06-15 07:52:19,283 fail2ban.actions        [937]: NOTICE  [sshd] Ban 138.68.226.175
2020-06-15 08:30:08,920 fail2ban.actions        [937]: NOTICE  [sshd] Ban 138.68.226.175
...
2020-06-15 15:14:12
144.172.79.5 attackbots
Jun 15 17:36:06 localhost sshd[2809670]: Invalid user honey from 144.172.79.5 port 35176
...
2020-06-15 15:46:04
61.133.232.250 attack
Jun 15 08:26:41 zulu412 sshd\[21638\]: Invalid user denis from 61.133.232.250 port 40681
Jun 15 08:26:41 zulu412 sshd\[21638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.250
Jun 15 08:26:43 zulu412 sshd\[21638\]: Failed password for invalid user denis from 61.133.232.250 port 40681 ssh2
...
2020-06-15 15:13:26
90.103.251.36 attack
Jun 15 08:53:50 pve1 sshd[1383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.103.251.36 
Jun 15 08:53:52 pve1 sshd[1383]: Failed password for invalid user no-reply from 90.103.251.36 port 38454 ssh2
...
2020-06-15 15:42:09
54.38.42.63 attackspambots
Invalid user scanner from 54.38.42.63 port 58588
2020-06-15 15:40:03
185.220.103.6 attackbots
"Restricted File Access Attempt - Matched Data: wp-config.php found within REQUEST_FILENAME: /wp-config.phppr"
2020-06-15 15:26:36

Recently Reported IPs

48.210.11.197 39.191.209.32 20.64.106.222 101.36.118.228
125.122.33.93 113.141.88.101 36.41.65.209 36.41.64.81
113.141.84.149 162.216.149.223 20.29.8.147 207.167.64.10
8.219.231.66 8.219.246.23 10.30.9.188 3.252.240.65
1.0.252.79 87.120.191.104 18.201.138.116 110.45.57.215