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

城市(city): unknown

省份(region): unknown

国家(country): Hong Kong

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;152.104.49.160.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 21:29:00 CST 2025
;; MSG SIZE  rcvd: 107
HOST信息:
160.49.104.152.in-addr.arpa domain name pointer static-ip-160-49-104-152.rev.dyxnet.com.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
160.49.104.152.in-addr.arpa	name = static-ip-160-49-104-152.rev.dyxnet.com.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
129.204.119.122 attack
Jul 30 19:43:01 debian sshd\[6349\]: Invalid user yh from 129.204.119.122 port 49970
Jul 30 19:43:01 debian sshd\[6349\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.119.122
Jul 30 19:43:03 debian sshd\[6349\]: Failed password for invalid user yh from 129.204.119.122 port 49970 ssh2
...
2019-07-31 08:18:28
106.13.23.77 attackbots
Jul 31 01:36:24 dedicated sshd[9036]: Invalid user ys from 106.13.23.77 port 60308
2019-07-31 07:47:36
178.128.117.55 attack
30.07.2019 23:59:51 SSH access blocked by firewall
2019-07-31 08:21:15
134.209.100.31 attackbots
2019-07-30T23:53:27.826417abusebot.cloudsearch.cf sshd\[26586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.100.31  user=ftp
2019-07-31 07:57:24
2001:67c:289c::20 attackbots
Jul 31 00:41:33 nginx sshd[50600]: Failed keyboard-interactive/pam for root from 171.25.193.20 port 50327 ssh2
Jul 31 00:41:34 nginx sshd[50600]: error: PAM: authentication error for root from tor-exit0-readme.dfri.se
2019-07-31 08:11:59
77.247.181.162 attackbotsspam
[ssh] SSH attack
2019-07-31 08:04:35
182.74.217.122 attackbotsspam
2019-07-30T23:44:57.406894abusebot-6.cloudsearch.cf sshd\[14741\]: Invalid user test from 182.74.217.122 port 36319
2019-07-31 07:50:33
200.80.247.40 attackspambots
fail2ban
2019-07-31 07:41:37
114.224.75.7 attack
firewall-block, port(s): 23/tcp
2019-07-31 08:11:27
121.175.154.23 attackbotsspam
20 attempts against mh-ssh on creek.magehost.pro
2019-07-31 08:14:47
139.99.107.166 attackbots
Jul 31 02:33:09 yabzik sshd[31177]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.107.166
Jul 31 02:33:11 yabzik sshd[31177]: Failed password for invalid user tomcat from 139.99.107.166 port 57602 ssh2
Jul 31 02:37:55 yabzik sshd[32668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.107.166
2019-07-31 08:12:16
181.111.58.173 attackspambots
Jul 30 22:45:03 marvibiene postfix/smtpd[11645]: warning: unknown[181.111.58.173]: SASL PLAIN authentication failed:
Jul 30 22:45:12 marvibiene postfix/smtpd[11645]: warning: unknown[181.111.58.173]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-07-31 07:53:25
222.161.56.248 attackspambots
Jul 31 02:44:23 server sshd\[8979\]: Invalid user uftp from 222.161.56.248 port 50767
Jul 31 02:44:23 server sshd\[8979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.161.56.248
Jul 31 02:44:25 server sshd\[8979\]: Failed password for invalid user uftp from 222.161.56.248 port 50767 ssh2
Jul 31 02:47:47 server sshd\[18944\]: Invalid user test2 from 222.161.56.248 port 39878
Jul 31 02:47:47 server sshd\[18944\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.161.56.248
2019-07-31 08:08:04
37.59.47.80 attackbotsspam
WordPress (CMS) attack attempts.
Date: 2019 Jul 30. 23:15:32
Source IP: 37.59.47.80

Portion of the log(s):
37.59.47.80 - [30/Jul/2019:23:15:31 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
37.59.47.80 - [30/Jul/2019:23:15:30 +0200] "GET /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
37.59.47.80 - [30/Jul/2019:23:15:30 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
37.59.47.80 - [30/Jul/2019:23:15:30 +0200] "GET /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
37.59.47.80 - [30/Jul/2019:23:15:30 +0200] "POST /wp-login.php HTTP/1.1" 404 118 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
37.59.47.80 - [30/Jul/2019:23:15:30 +0200] "GET /wp-login.php
2019-07-31 07:55:05
219.144.245.34 attack
SMB Server BruteForce Attack
2019-07-31 07:35:06

最近上报的IP列表

45.231.24.248 220.152.196.86 32.49.198.31 186.12.19.175
53.250.76.229 5.26.31.243 60.231.191.32 136.160.26.132
235.203.148.26 63.209.237.44 230.171.202.0 178.232.37.86
93.86.2.14 238.181.109.82 202.140.171.235 202.165.62.111
114.224.64.35 36.59.110.103 54.91.92.61 225.61.139.192