必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): unknown

省份(region): unknown

国家(country): None

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
IP 类型 评论内容 时间
125.164.145.52 attack
Unauthorized connection attempt from IP address 125.164.145.52 on Port 445(SMB)
2019-08-20 00:22:54
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.164.145.34
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17772
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;125.164.145.34.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 02:52:01 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
Host 34.145.164.125.in-addr.arpa not found: 2(SERVFAIL)
NSLOOKUP信息:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 34.145.164.125.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
121.142.87.218 attackbots
$f2bV_matches
2020-04-08 02:12:10
112.85.42.195 attackspam
Jun 23 08:46:30 mail1 sshd\[12079\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.195  user=root
Jun 23 08:46:32 mail1 sshd\[12079\]: Failed password for root from 112.85.42.195 port 34399 ssh2
Jun 23 08:46:34 mail1 sshd\[12079\]: Failed password for root from 112.85.42.195 port 34399 ssh2
Jun 23 08:46:36 mail1 sshd\[12079\]: Failed password for root from 112.85.42.195 port 34399 ssh2
Jun 23 08:59:01 mail1 sshd\[17947\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.195  user=root
...
2020-04-08 02:39:13
167.114.210.124 attackspam
Attempted connection to port 22.
2020-04-08 02:40:09
190.128.230.206 attackbotsspam
Apr  7 17:12:56 *** sshd[29993]: Invalid user cacti from 190.128.230.206
2020-04-08 02:03:05
51.75.248.241 attack
$f2bV_matches
2020-04-08 02:16:59
222.186.15.114 attack
Apr  7 20:35:39 vmd38886 sshd\[27267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.114  user=root
Apr  7 20:35:41 vmd38886 sshd\[27267\]: Failed password for root from 222.186.15.114 port 56602 ssh2
Apr  7 20:35:43 vmd38886 sshd\[27267\]: Failed password for root from 222.186.15.114 port 56602 ssh2
2020-04-08 02:37:43
68.183.48.172 attack
Apr  7 19:21:42 pve sshd[18112]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.48.172 
Apr  7 19:21:44 pve sshd[18112]: Failed password for invalid user elcabo from 68.183.48.172 port 35676 ssh2
Apr  7 19:23:37 pve sshd[18405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.48.172
2020-04-08 01:57:20
24.234.159.109 attackbotsspam
Web Server Attack
2020-04-08 02:05:29
106.13.142.115 attackspam
k+ssh-bruteforce
2020-04-08 02:26:01
112.85.42.180 attackbotsspam
(sshd) Failed SSH login from 112.85.42.180 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  7 19:55:51 amsweb01 sshd[16727]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.180  user=root
Apr  7 19:55:52 amsweb01 sshd[16727]: Failed password for root from 112.85.42.180 port 51088 ssh2
Apr  7 19:55:57 amsweb01 sshd[16727]: Failed password for root from 112.85.42.180 port 51088 ssh2
Apr  7 19:56:00 amsweb01 sshd[16727]: Failed password for root from 112.85.42.180 port 51088 ssh2
Apr  7 19:56:04 amsweb01 sshd[16727]: Failed password for root from 112.85.42.180 port 51088 ssh2
2020-04-08 02:13:39
49.228.160.43 attackbots
bruteforce detected
2020-04-08 02:39:35
139.199.18.200 attack
Apr  7 18:30:02 srv-ubuntu-dev3 sshd[48447]: Invalid user user from 139.199.18.200
Apr  7 18:30:02 srv-ubuntu-dev3 sshd[48447]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.18.200
Apr  7 18:30:02 srv-ubuntu-dev3 sshd[48447]: Invalid user user from 139.199.18.200
Apr  7 18:30:04 srv-ubuntu-dev3 sshd[48447]: Failed password for invalid user user from 139.199.18.200 port 51748 ssh2
Apr  7 18:38:31 srv-ubuntu-dev3 sshd[49912]: Invalid user ts from 139.199.18.200
...
2020-04-08 02:22:08
91.134.173.100 attack
Lines containing failures of 91.134.173.100
Apr  7 00:44:19 kmh-wmh-002-nbg03 sshd[1050]: Invalid user test2 from 91.134.173.100 port 52288
Apr  7 00:44:19 kmh-wmh-002-nbg03 sshd[1050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.173.100 
Apr  7 00:44:21 kmh-wmh-002-nbg03 sshd[1050]: Failed password for invalid user test2 from 91.134.173.100 port 52288 ssh2
Apr  7 00:44:22 kmh-wmh-002-nbg03 sshd[1050]: Received disconnect from 91.134.173.100 port 52288:11: Bye Bye [preauth]
Apr  7 00:44:22 kmh-wmh-002-nbg03 sshd[1050]: Disconnected from invalid user test2 91.134.173.100 port 52288 [preauth]
Apr  7 00:57:23 kmh-wmh-002-nbg03 sshd[2467]: Invalid user deploy from 91.134.173.100 port 49758
Apr  7 00:57:23 kmh-wmh-002-nbg03 sshd[2467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.173.100 
Apr  7 00:57:25 kmh-wmh-002-nbg03 sshd[2467]: Failed password for invalid user deploy fro........
------------------------------
2020-04-08 02:01:43
36.92.132.98 attack
Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found
2020-04-08 02:10:50
179.222.178.234 attack
Draytek Vigor Remote Command Execution Vulnerability, PTR: b3deb2ea.virtua.com.br.
2020-04-08 02:01:15

最近上报的IP列表

117.90.4.47 125.164.146.110 125.164.146.147 125.164.146.200
125.164.146.163 117.90.4.5 125.164.146.55 125.164.146.32
125.164.146.244 125.164.146.44 125.164.146.108 125.164.146.238
125.164.146.94 125.164.146.219 10.155.96.22 125.164.147.10
125.164.147.2 117.90.4.50 125.164.147.115 125.164.147.245