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

城市(city): unknown

省份(region): unknown

国家(country): Netherlands (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 145.131.34.241
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53658
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;145.131.34.241.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 02:50:42 CST 2025
;; MSG SIZE  rcvd: 107
HOST信息:
Host 241.34.131.145.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 241.34.131.145.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
106.52.26.30 attack
[Aegis] @ 2019-07-23 21:11:59  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-07-24 10:26:30
51.75.27.254 attackbots
Invalid user postgres from 51.75.27.254 port 50800
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.27.254
Failed password for invalid user postgres from 51.75.27.254 port 50800 ssh2
Invalid user setup from 51.75.27.254 port 47344
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.27.254
2019-07-24 10:47:51
86.191.61.55 attackspambots
Automatic report - Port Scan Attack
2019-07-24 10:10:31
106.110.17.60 attack
Automatic report - Port Scan Attack
2019-07-24 10:21:30
118.24.81.93 attackspambots
Jul 24 03:33:11 mail sshd\[9563\]: Invalid user yana from 118.24.81.93 port 48558
Jul 24 03:33:11 mail sshd\[9563\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.81.93
...
2019-07-24 10:42:53
185.220.101.25 attack
Jul 24 01:55:56 vpn01 sshd\[14432\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.25  user=root
Jul 24 01:55:58 vpn01 sshd\[14432\]: Failed password for root from 185.220.101.25 port 43028 ssh2
Jul 24 01:56:02 vpn01 sshd\[14434\]: Invalid user 666666 from 185.220.101.25
2019-07-24 10:45:33
103.207.2.204 attackspambots
Jul 24 03:39:10 eventyay sshd[32085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.207.2.204
Jul 24 03:39:12 eventyay sshd[32085]: Failed password for invalid user stats from 103.207.2.204 port 33756 ssh2
Jul 24 03:45:33 eventyay sshd[1201]: Failed password for root from 103.207.2.204 port 49250 ssh2
...
2019-07-24 09:58:11
89.100.11.18 attackbots
Jul 24 04:15:18 eventyay sshd[8739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.100.11.18
Jul 24 04:15:20 eventyay sshd[8739]: Failed password for invalid user docker from 89.100.11.18 port 47742 ssh2
Jul 24 04:20:23 eventyay sshd[10012]: Failed password for root from 89.100.11.18 port 44768 ssh2
...
2019-07-24 10:29:16
27.254.136.29 attackspam
Jul 24 03:38:29 debian sshd\[11248\]: Invalid user teamspeak from 27.254.136.29 port 53766
Jul 24 03:38:29 debian sshd\[11248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.254.136.29
...
2019-07-24 10:42:22
103.94.130.4 attack
2019-07-23T22:54:17.847222abusebot-4.cloudsearch.cf sshd\[1304\]: Invalid user test from 103.94.130.4 port 57256
2019-07-24 10:25:37
185.204.118.116 attack
DATE:2019-07-24 00:23:27, IP:185.204.118.116, PORT:ssh SSH brute force auth (thor)
2019-07-24 10:10:47
115.254.63.52 attack
Invalid user applmgr from 115.254.63.52 port 36451
2019-07-24 10:14:14
89.107.115.225 attack
[portscan] Port scan
2019-07-24 10:40:52
187.21.36.119 attack
Jul 23 22:00:48 mxgate1 postfix/postscreen[8780]: CONNECT from [187.21.36.119]:42288 to [176.31.12.44]:25
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8867]: addr 187.21.36.119 listed by domain bl.spamcop.net as 127.0.0.2
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8870]: addr 187.21.36.119 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8868]: addr 187.21.36.119 listed by domain zen.spamhaus.org as 127.0.0.11
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8868]: addr 187.21.36.119 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8871]: addr 187.21.36.119 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 23 22:00:48 mxgate1 postfix/dnsblog[8869]: addr 187.21.36.119 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 23 22:00:54 mxgate1 postfix/postscreen[8780]: DNSBL rank 6 for [187.21.36.119]:42288
Jul x@x
Jul 23 22:00:56 mxgate1 postfix/postscreen[8780]: HANGUP after 1.1 from [187.21.36.119]:42288 in........
-------------------------------
2019-07-24 10:05:17
83.29.53.47 attackbotsspam
Automatic report - Port Scan Attack
2019-07-24 10:12:59

最近上报的IP列表

101.40.109.158 161.140.14.159 249.192.187.103 145.141.234.161
7.104.150.202 34.117.33.139 100.217.158.202 30.167.129.178
59.122.13.216 204.215.61.90 122.131.23.196 13.150.68.138
30.8.117.225 24.140.253.131 34.195.158.3 97.224.156.163
33.2.136.71 242.161.204.121 33.30.147.105 46.158.194.135