必须是合法有效的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所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.166.52.126
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;125.166.52.126.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 03:05:05 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
Host 126.52.166.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 126.52.166.125.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
181.48.95.130 attackspam
Oct 14 06:55:03 pkdns2 sshd\[3495\]: Address 181.48.95.130 maps to foodmanager.com.co, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Oct 14 06:55:03 pkdns2 sshd\[3495\]: Invalid user Betrieb-123 from 181.48.95.130Oct 14 06:55:05 pkdns2 sshd\[3495\]: Failed password for invalid user Betrieb-123 from 181.48.95.130 port 42346 ssh2Oct 14 06:58:57 pkdns2 sshd\[3682\]: Address 181.48.95.130 maps to foodmanager.com.co, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Oct 14 06:58:57 pkdns2 sshd\[3682\]: Invalid user Bizz123 from 181.48.95.130Oct 14 06:58:59 pkdns2 sshd\[3682\]: Failed password for invalid user Bizz123 from 181.48.95.130 port 52738 ssh2
...
2019-10-14 12:01:35
45.224.105.74 attackspam
Automatic report - Banned IP Access
2019-10-14 12:14:46
167.71.229.184 attackbotsspam
Oct 14 05:54:24 bouncer sshd\[8330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.229.184  user=root
Oct 14 05:54:26 bouncer sshd\[8330\]: Failed password for root from 167.71.229.184 port 56698 ssh2
Oct 14 05:58:47 bouncer sshd\[8385\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.229.184  user=root
...
2019-10-14 12:06:59
167.71.197.133 attackspambots
Sep 21 02:57:05 yesfletchmain sshd\[6814\]: Invalid user tq from 167.71.197.133 port 42266
Sep 21 02:57:05 yesfletchmain sshd\[6814\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.197.133
Sep 21 02:57:07 yesfletchmain sshd\[6814\]: Failed password for invalid user tq from 167.71.197.133 port 42266 ssh2
Sep 21 03:01:17 yesfletchmain sshd\[6935\]: Invalid user testuser from 167.71.197.133 port 55168
Sep 21 03:01:17 yesfletchmain sshd\[6935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.197.133
...
2019-10-14 08:09:48
167.114.231.174 attackspambots
Apr 24 07:07:05 yesfletchmain sshd\[12549\]: Invalid user ftpadmin from 167.114.231.174 port 36332
Apr 24 07:07:05 yesfletchmain sshd\[12549\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.231.174
Apr 24 07:07:06 yesfletchmain sshd\[12549\]: Failed password for invalid user ftpadmin from 167.114.231.174 port 36332 ssh2
Apr 24 07:13:09 yesfletchmain sshd\[12775\]: Invalid user wellington from 167.114.231.174 port 35362
Apr 24 07:13:09 yesfletchmain sshd\[12775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.231.174
...
2019-10-14 08:20:35
88.214.26.45 attackbotsspam
10/13/2019-22:11:29.811124 88.214.26.45 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 96
2019-10-14 08:14:35
139.215.217.181 attackspambots
Oct 13 23:11:59 MK-Soft-VM7 sshd[6700]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.215.217.181 
Oct 13 23:12:01 MK-Soft-VM7 sshd[6700]: Failed password for invalid user Par0la1! from 139.215.217.181 port 51684 ssh2
...
2019-10-14 08:10:50
116.85.11.19 attackbots
Oct 13 16:11:25 Tower sshd[19748]: Connection from 116.85.11.19 port 48396 on 192.168.10.220 port 22
Oct 13 16:11:27 Tower sshd[19748]: Invalid user Album@321 from 116.85.11.19 port 48396
Oct 13 16:11:27 Tower sshd[19748]: error: Could not get shadow information for NOUSER
Oct 13 16:11:27 Tower sshd[19748]: Failed password for invalid user Album@321 from 116.85.11.19 port 48396 ssh2
Oct 13 16:11:27 Tower sshd[19748]: Received disconnect from 116.85.11.19 port 48396:11: Bye Bye [preauth]
Oct 13 16:11:27 Tower sshd[19748]: Disconnected from invalid user Album@321 116.85.11.19 port 48396 [preauth]
2019-10-14 08:13:14
185.90.118.20 attackspam
10/13/2019-20:09:01.914534 185.90.118.20 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 08:12:44
159.203.201.112 attack
10/14/2019-05:59:03.488419 159.203.201.112 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-14 12:00:06
180.168.76.222 attack
Oct 14 05:54:43 vps691689 sshd[15683]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.168.76.222
Oct 14 05:54:44 vps691689 sshd[15683]: Failed password for invalid user P4rol4_1@3 from 180.168.76.222 port 19316 ssh2
Oct 14 05:58:46 vps691689 sshd[15737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.168.76.222
...
2019-10-14 12:08:45
167.71.199.22 attackbotsspam
Sep 27 08:11:31 yesfletchmain sshd\[24108\]: Invalid user demo from 167.71.199.22 port 40568
Sep 27 08:11:31 yesfletchmain sshd\[24108\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.199.22
Sep 27 08:11:34 yesfletchmain sshd\[24108\]: Failed password for invalid user demo from 167.71.199.22 port 40568 ssh2
Sep 27 08:16:07 yesfletchmain sshd\[24387\]: Invalid user ll from 167.71.199.22 port 54184
Sep 27 08:16:07 yesfletchmain sshd\[24387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.199.22
...
2019-10-14 08:07:31
118.69.55.167 attackbots
Unauthorised access (Oct 14) SRC=118.69.55.167 LEN=52 TTL=114 ID=26940 DF TCP DPT=445 WINDOW=8192 SYN
2019-10-14 12:14:00
114.227.14.138 attackspambots
Oct 13 23:58:29 esmtp postfix/smtpd[25202]: lost connection after AUTH from unknown[114.227.14.138]
Oct 13 23:58:30 esmtp postfix/smtpd[25213]: lost connection after AUTH from unknown[114.227.14.138]
Oct 13 23:58:32 esmtp postfix/smtpd[24995]: lost connection after AUTH from unknown[114.227.14.138]
Oct 13 23:58:32 esmtp postfix/smtpd[25200]: lost connection after AUTH from unknown[114.227.14.138]
Oct 13 23:58:33 esmtp postfix/smtpd[25202]: lost connection after AUTH from unknown[114.227.14.138]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=114.227.14.138
2019-10-14 12:14:34
45.80.64.127 attackbots
Oct 13 17:51:44 sachi sshd\[15300\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.64.127  user=root
Oct 13 17:51:46 sachi sshd\[15300\]: Failed password for root from 45.80.64.127 port 44294 ssh2
Oct 13 17:55:14 sachi sshd\[15578\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.64.127  user=root
Oct 13 17:55:15 sachi sshd\[15578\]: Failed password for root from 45.80.64.127 port 54598 ssh2
Oct 13 17:58:55 sachi sshd\[15889\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.64.127  user=root
2019-10-14 12:03:19

最近上报的IP列表

125.166.51.56 125.166.51.197 125.166.53.0 125.166.52.17
125.166.6.171 125.166.59.187 125.166.59.138 125.166.59.86
125.166.6.33 125.166.60.252 125.166.61.101 125.166.65.164
125.166.67.152 125.166.65.210 125.166.69.123 117.92.144.92
125.166.67.210 125.166.69.0 125.166.68.188 125.166.69.46