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

Region: Sichuan

Country: China

Internet Service Provider: ChinaNet Sichuan Province Network

Hostname: unknown

Organization: CHINANET SiChuan Telecom Internet Data Center

Usage Type: unknown

Comments:
Type Details Datetime
attackbotsspam
trying to access non-authorized port
2020-04-08 07:16:30
attackspam
514/tcp 10255/tcp 1610/tcp...
[2019-11-10/2020-01-10]649pkt,251pt.(tcp),55pt.(udp)
2020-01-11 04:15:52
attackbotsspam
12/25/2019-14:42:44.713087 125.64.94.212 Protocol: 17 ET SCAN HID VertX and Edge door controllers discover
2019-12-26 04:04:13
attack
24.12.2019 08:20:34 Connection to port 47808 blocked by firewall
2019-12-24 16:52:04
attackbots
24.12.2019 00:23:00 Connection to port 4911 blocked by firewall
2019-12-24 08:15:09
attack
125.64.94.212 was recorded 9 times by 9 hosts attempting to connect to the following ports: 9600,1962. Incident counter (4h, 24h, all-time): 9, 36, 4564
2019-12-24 01:31:46
attackbotsspam
Dec 21 19:44:26 debian-2gb-nbg1-2 kernel: \[606622.124258\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=125.64.94.212 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=54321 PROTO=TCP SPT=46262 DPT=1720 WINDOW=65535 RES=0x00 SYN URGP=0
2019-12-22 04:16:04
attackbots
firewall-block, port(s): 2095/tcp
2019-12-20 01:38:44
attack
125.64.94.212 was recorded 27 times by 27 hosts attempting to connect to the following ports: 1911,47808. Incident counter (4h, 24h, all-time): 27, 158, 4191
2019-12-17 03:26:44
attackbotsspam
UTC: 2019-12-13 pkts: 2
ports(tcp): 102, 502
2019-12-14 19:44:41
attack
Unauthorized connection attempt detected from IP address 125.64.94.212 to port 2404
2019-12-13 15:10:21
attackbots
Dec 12 10:04:18 debian-2gb-vpn-nbg1-1 kernel: [512638.585923] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=125.64.94.212 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=54321 PROTO=TCP SPT=41296 DPT=789 WINDOW=65535 RES=0x00 SYN URGP=0
2019-12-12 16:08:14
attack
Unauthorized connection attempt detected from IP address 125.64.94.212 to port 5984
2019-12-11 18:43:54
attackspam
04.12.2019 14:01:36 Connection to port 5007 blocked by firewall
2019-12-04 23:16:03
attackspambots
20.11.2019 22:56:30 Connection to port 3528 blocked by firewall
2019-11-21 08:51:57
attackspambots
Port scan: Attack repeated for 24 hours
2019-11-14 14:48:56
attackspam
Triggered: repeated knocking on closed ports.
2019-11-13 22:31:18
attackspam
125.64.94.212 was recorded 59 times by 23 hosts attempting to connect to the following ports: 6669,1091,6600,32795,8351,2123,5672,5353,540. Incident counter (4h, 24h, all-time): 59, 196, 1047
2019-11-12 22:45:05
attackspam
Portscan or hack attempt detected by psad/fwsnort
2019-11-12 17:54:30
attackspambots
Connection by 125.64.94.212 on port: 13013 got caught by honeypot at 11/6/2019 3:16:57 PM
2019-11-07 01:18:32
attackbots
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-11-02 16:20:15
attack
Connection by 125.64.94.212 on port: 14000 got caught by honeypot at 10/26/2019 10:26:56 PM
2019-10-27 14:47:15
attackspam
UTC: 2019-10-21 pkts: 3(2, 1)
ports(tcp): 102, 888
port (udp): 69
2019-10-22 17:01:51
attackspambots
21.10.2019 06:21:16 Connection to port 2181 blocked by firewall
2019-10-21 15:16:41
attackspambots
Port scan: Attack repeated for 24 hours
2019-10-17 03:42:13
attack
2 pkts, ports: TCP:1610, UDP:32780
2019-10-15 01:22:13
attackbotsspam
15.09.2019 13:27:23 Connection to port 27016 blocked by firewall
2019-09-15 22:15:37
attackspambots
11.09.2019 21:45:55 Connection to port 17988 blocked by firewall
2019-09-12 06:13:47
attack
Sep  9 22:14:21 postfix postfix/smtpd\[8190\]: lost connection after EHLO from unknown\[125.64.94.212\]
Sep  9 22:14:22 postfix postfix/smtpd\[8190\]: lost connection after UNKNOWN from unknown\[125.64.94.212\]
...
2019-09-12 01:56:17
attackbots
scan z
2019-09-11 11:21:07
Comments on same subnet:
IP Type Details Datetime
125.64.94.136 attackbots
 TCP (SYN) 125.64.94.136:40563 -> port 12000, len 44
2020-10-13 23:59:13
125.64.94.136 attackbots
=Multiport scan 187 ports : 1 13 22 31 32(x2) 38 70 82 111 113 123 280 322 497 510 517(x2) 518 523 548(x2) 556 587(x2) 620 623 636 731 783(x2) 898 990 994 995(x2) 1042(x2) 1080 1200 1241 1344 1400 1443 1503 1505 1521 1604 1830 1883 1900 1901 1967 2000 2010 2030 2052 2080(x3) 2086 2095 2181 2252 2332 2375(x2) 2404 2406(x2) 2443 2600 2601(x2) 2604 2715 2869 3075(x2) 3097 3260 3299 3310 3311 3333 3352 3372 3388 3390 3443 3520 3522 3525 3526 3529 3689 3774 3940 4022 4155 4430 4440 4444 4700 5007 5051 5061 5094 5269 5280 5353 5570 5672 5683 5900 5901 5902 5938 5984 6001(x2) 6112 6346 6443 6544 6666(x3) 6667 6669 6679 6697 6699 6881(x2) 6969 6998 7000 7001 7007 7077 7144 7199 7200(x2) 7778 8000 8001 8002 8004 8006 8007 8009(x2) 8030 8060 8069 8086 8123 8182 8332 8333 8500 8554 8880 8881(x2) 8884 8889 8899(x2) 9002 9030 9080 9300 9446(x3) 9595 9801 9944 9993 10000 10250 10255 10443 11371 12999 13666 13722 14534 15002 16514 16923 16993 19150 19999 20332 22335 25565 26470 27017(x2) 27018 31337 3....
2020-10-13 07:51:07
125.64.94.133 attack
scans once in preceeding hours on the ports (in chronological order) 32760 resulting in total of 3 scans from 125.64.0.0/13 block.
2020-10-11 01:32:26
125.64.94.136 attackbotsspam
 TCP (SYN) 125.64.94.136:41809 -> port 50200, len 44
2020-10-07 06:39:26
125.64.94.136 attackspambots
Automatic report - Banned IP Access
2020-10-06 22:57:41
125.64.94.136 attackspam
firewall-block, port(s): 5427/tcp, 50111/tcp
2020-10-06 14:42:44
125.64.94.136 attack
 TCP (SYN) 125.64.94.136:44297 -> port 50050, len 44
2020-09-22 20:55:43
125.64.94.136 attack
firewall-block, port(s): 1040/tcp, 4506/tcp, 5357/tcp, 40001/tcp
2020-09-22 05:04:54
125.64.94.136 attack
 TCP (SYN) 125.64.94.136:52792 -> port 901, len 44
2020-09-20 00:40:07
125.64.94.136 attackspam
proto=tcp  .  spt=40362  .  dpt=995  .  src=125.64.94.136  .  dst=xx.xx.4.1  .     Found on   Binary Defense       (40)
2020-09-19 16:28:15
125.64.94.136 attackspambots
scans 3 times in preceeding hours on the ports (in chronological order) 8800 4949 15001 resulting in total of 5 scans from 125.64.0.0/13 block.
2020-09-18 22:39:06
125.64.94.136 attackspam
Found on   Binary Defense     / proto=6  .  srcport=38676  .  dstport=16993  .     (77)
2020-09-18 14:53:34
125.64.94.136 attackbots
Hacking
2020-09-18 05:10:01
125.64.94.136 attack
firewall-block, port(s): 48649/tcp
2020-09-13 22:51:12
125.64.94.136 attackspambots
32/tcp 9864/tcp 32757/udp...
[2020-09-09/13]118pkt,92pt.(tcp),20pt.(udp)
2020-09-13 14:47:58
Whois info:
b
Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.64.94.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45995
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;125.64.94.212.			IN	A

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Fri Apr 12 07:01:21 +08 2019
;; MSG SIZE  rcvd: 117

Host info
Host 212.94.64.125.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 212.94.64.125.in-addr.arpa: NXDOMAIN

Related IP info:
Related comments:
IP Type Details Datetime
92.117.228.210 attackbotsspam
Jan 24 22:48:20 dallas01 sshd[14641]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.117.228.210
Jan 24 22:48:22 dallas01 sshd[14641]: Failed password for invalid user mag from 92.117.228.210 port 39528 ssh2
Jan 24 22:57:17 dallas01 sshd[21457]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.117.228.210
2020-01-25 13:21:32
145.239.7.54 attackspam
Jan 25 06:27:18 ns381471 sshd[3104]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.7.54
Jan 25 06:27:20 ns381471 sshd[3104]: Failed password for invalid user rdp from 145.239.7.54 port 46660 ssh2
2020-01-25 13:28:23
195.24.61.7 attackbotsspam
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-01-25 13:49:55
86.98.94.242 attack
Fail2Ban Ban Triggered
2020-01-25 13:41:23
35.201.243.170 attack
Unauthorized connection attempt detected from IP address 35.201.243.170 to port 2220 [J]
2020-01-25 13:43:58
45.134.146.5 attackbotsspam
Unauthorized connection attempt detected from IP address 45.134.146.5 to port 2220 [J]
2020-01-25 13:25:44
110.137.80.93 attack
Unauthorised access (Jan 25) SRC=110.137.80.93 LEN=40 TTL=245 ID=30243 DF TCP DPT=8080 WINDOW=14600 SYN
2020-01-25 13:46:16
222.186.175.161 attack
Jan 25 06:12:41 vmanager6029 sshd\[15012\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Jan 25 06:12:43 vmanager6029 sshd\[15012\]: Failed password for root from 222.186.175.161 port 65122 ssh2
Jan 25 06:12:46 vmanager6029 sshd\[15012\]: Failed password for root from 222.186.175.161 port 65122 ssh2
2020-01-25 13:13:26
222.186.173.154 attack
Jan 25 06:14:32 ns381471 sshd[2623]: Failed password for root from 222.186.173.154 port 50196 ssh2
Jan 25 06:14:43 ns381471 sshd[2623]: error: maximum authentication attempts exceeded for root from 222.186.173.154 port 50196 ssh2 [preauth]
2020-01-25 13:36:48
222.186.175.202 attackbotsspam
2020-01-25T06:06:50.384994ns386461 sshd\[23315\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.202  user=root
2020-01-25T06:06:52.230620ns386461 sshd\[23315\]: Failed password for root from 222.186.175.202 port 61756 ssh2
2020-01-25T06:06:55.058489ns386461 sshd\[23315\]: Failed password for root from 222.186.175.202 port 61756 ssh2
2020-01-25T06:06:58.970512ns386461 sshd\[23315\]: Failed password for root from 222.186.175.202 port 61756 ssh2
2020-01-25T06:07:02.418596ns386461 sshd\[23315\]: Failed password for root from 222.186.175.202 port 61756 ssh2
...
2020-01-25 13:20:41
218.92.0.158 attackbotsspam
01/25/2020-00:39:26.649412 218.92.0.158 Protocol: 6 ET SCAN Potential SSH Scan
2020-01-25 13:52:09
213.32.75.112 attackbots
Jan 24 19:39:56 eddieflores sshd\[1964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.75.112  user=root
Jan 24 19:39:58 eddieflores sshd\[1964\]: Failed password for root from 213.32.75.112 port 36124 ssh2
Jan 24 19:43:02 eddieflores sshd\[2437\]: Invalid user odoo11 from 213.32.75.112
Jan 24 19:43:02 eddieflores sshd\[2437\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.75.112
Jan 24 19:43:05 eddieflores sshd\[2437\]: Failed password for invalid user odoo11 from 213.32.75.112 port 38610 ssh2
2020-01-25 13:56:00
223.15.218.87 attackbots
Unauthorized connection attempt detected from IP address 223.15.218.87 to port 23 [J]
2020-01-25 13:35:56
222.186.173.238 attackbots
Jan 25 06:11:43 srv206 sshd[23182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
Jan 25 06:11:44 srv206 sshd[23182]: Failed password for root from 222.186.173.238 port 4092 ssh2
...
2020-01-25 13:14:34
36.68.55.67 attackspam
unauthorized connection attempt
2020-01-25 13:54:08

Recently Reported IPs

58.71.79.51 186.229.57.4 95.107.8.43 139.190.194.7
108.174.198.40 104.223.144.99 59.152.97.73 159.65.128.4
104.223.144.98 94.231.136.98 189.163.138.195 34.73.124.245
92.244.239.147 202.162.217.173 79.124.58.10 50.116.35.14
218.158.57.21 185.25.204.80 105.233.40.41 138.36.3.33