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

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;119.125.197.44.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 14:05:15 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
Host 44.197.125.119.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 44.197.125.119.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
66.243.219.227 attack
Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2019-10-26 00:50:05
37.186.130.54 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2019-10-26 00:19:08
117.83.147.48 attackbotsspam
Oct 25 07:43:31 esmtp postfix/smtpd[30672]: lost connection after AUTH from unknown[117.83.147.48]
Oct 25 07:43:33 esmtp postfix/smtpd[30673]: lost connection after AUTH from unknown[117.83.147.48]
Oct 25 07:43:34 esmtp postfix/smtpd[30672]: lost connection after AUTH from unknown[117.83.147.48]
Oct 25 07:43:35 esmtp postfix/smtpd[30672]: lost connection after AUTH from unknown[117.83.147.48]
Oct 25 07:43:36 esmtp postfix/smtpd[30673]: lost connection after AUTH from unknown[117.83.147.48]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=117.83.147.48
2019-10-26 00:29:09
2.122.217.252 attackbots
Autoban   2.122.217.252 AUTH/CONNECT
2019-10-26 00:36:43
123.21.33.151 attack
SSH Bruteforce attempt
2019-10-26 00:39:53
89.145.184.222 attackspambots
Oct 25 12:04:25 system,error,critical: login failure for user admin from 89.145.184.222 via telnet
Oct 25 12:04:26 system,error,critical: login failure for user root from 89.145.184.222 via telnet
Oct 25 12:04:28 system,error,critical: login failure for user administrator from 89.145.184.222 via telnet
Oct 25 12:04:32 system,error,critical: login failure for user root from 89.145.184.222 via telnet
Oct 25 12:04:34 system,error,critical: login failure for user admin from 89.145.184.222 via telnet
Oct 25 12:04:36 system,error,critical: login failure for user root from 89.145.184.222 via telnet
Oct 25 12:04:40 system,error,critical: login failure for user guest from 89.145.184.222 via telnet
Oct 25 12:04:41 system,error,critical: login failure for user root from 89.145.184.222 via telnet
Oct 25 12:04:43 system,error,critical: login failure for user root from 89.145.184.222 via telnet
Oct 25 12:04:48 system,error,critical: login failure for user root from 89.145.184.222 via telnet
2019-10-26 00:30:10
5.143.53.213 attack
45997 → 27895 Len=103
"d1:ad2:id20:.........<..>.$^ ...6:target20:(.3.......5A..&...O.e1:q9:find_node1:t4:FC..1:v4:UT.51:y1:qe"
2019-10-26 00:31:44
190.242.27.97 attackspambots
Oct 25 13:59:22 h2421860 postfix/postscreen[21600]: CONNECT from [190.242.27.97]:12525 to [85.214.119.52]:25
Oct 25 13:59:22 h2421860 postfix/dnsblog[21603]: addr 190.242.27.97 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 25 13:59:22 h2421860 postfix/dnsblog[21603]: addr 190.242.27.97 listed by domain zen.spamhaus.org as 127.0.0.3
Oct 25 13:59:22 h2421860 postfix/dnsblog[21603]: addr 190.242.27.97 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 25 13:59:22 h2421860 postfix/dnsblog[21602]: addr 190.242.27.97 listed by domain Unknown.trblspam.com as 185.53.179.7
Oct 25 13:59:22 h2421860 postfix/dnsblog[21605]: addr 190.242.27.97 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 25 13:59:28 h2421860 postfix/postscreen[21600]: DNSBL rank 6 for [190.242.27.97]:12525
Oct x@x
Oct 25 13:59:28 h2421860 postfix/postscreen[21600]: HANGUP after 0.83 from [190.242.27.97]:12525 in tests after SMTP handshake
Oct 25 13:59:28 h2421860 postfix/postscreen[21600]: DISCONNE........
-------------------------------
2019-10-26 00:37:21
37.187.25.138 attackspambots
SSH brutforce
2019-10-26 00:49:47
45.141.84.50 attack
Oct 25 17:53:26 h2177944 kernel: \[4894626.176733\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.141.84.50 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=21428 PROTO=TCP SPT=41612 DPT=6616 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 25 17:54:16 h2177944 kernel: \[4894676.660823\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.141.84.50 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=61292 PROTO=TCP SPT=41612 DPT=4167 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 25 17:57:34 h2177944 kernel: \[4894874.387777\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.141.84.50 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=55060 PROTO=TCP SPT=41612 DPT=6630 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 25 18:05:14 h2177944 kernel: \[4895334.313632\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.141.84.50 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=49906 PROTO=TCP SPT=41612 DPT=6160 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 25 18:29:27 h2177944 kernel: \[4896787.039702\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.141.84.50 DST=85.214.117.9 LEN=
2019-10-26 00:50:44
49.88.112.71 attackbotsspam
2019-10-25T16:11:45.787745abusebot-6.cloudsearch.cf sshd\[15309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.71  user=root
2019-10-26 00:32:19
116.110.117.42 attackbots
2019-10-25T18:32:38.496010shiva sshd[17166]: Invalid user user from 116.110.117.42 port 9558
2019-10-25T18:33:34.789606shiva sshd[17197]: Invalid user admin from 116.110.117.42 port 16132
2019-10-25T18:33:38.031447shiva sshd[17199]: Invalid user guest from 116.110.117.42 port 35472
...
2019-10-26 00:44:05
103.136.40.26 attackspam
Oct 25 13:51:32 fv15 postfix/smtpd[6735]: connect from unknown[103.136.40.26]
Oct 25 13:51:33 fv15 postgrey[1070]: action=greylist, reason=new, client_name=unknown, client_address=103.136.40.26, sender=x@x recipient=x@x
Oct x@x
Oct 25 13:51:39 fv15 postfix/smtpd[15560]: connect from unknown[103.136.40.26]
Oct 25 13:51:39 fv15 postgrey[1070]: action=greylist, reason=new, client_name=unknown, client_address=103.136.40.26, sender=x@x recipient=x@x
Oct x@x
Oct 25 13:51:40 fv15 postfix/smtpd[17342]: connect from unknown[103.136.40.26]
Oct 25 13:51:41 fv15 postgrey[1070]: action=greylist, reason=new, client_name=unknown, client_address=103.136.40.26, sender=x@x recipient=x@x
Oct x@x
Oct 25 13:51:54 fv15 postfix/smtpd[15014]: connect from unknown[103.136.40.26]
Oct 25 13:51:55 fv15 postgrey[1070]: action=greylist, reason=new, client_name=unknown, client_address=103.136.40.26, sender=x@x recipient=x@x
Oct x@x
Oct 25 13:52:13 fv15 postfix/smtpd[4925]: connect from unknown[103.13........
-------------------------------
2019-10-26 00:20:23
175.6.5.233 attackbotsspam
Oct 25 02:08:52 server sshd\[23834\]: Invalid user support from 175.6.5.233
Oct 25 02:08:52 server sshd\[23834\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.6.5.233 
Oct 25 02:08:54 server sshd\[23834\]: Failed password for invalid user support from 175.6.5.233 port 64615 ssh2
Oct 25 16:55:49 server sshd\[21957\]: Invalid user user from 175.6.5.233
Oct 25 16:55:49 server sshd\[21957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.6.5.233 
...
2019-10-26 00:33:19
198.108.66.80 attack
port scan and connect, tcp 8080 (http-proxy)
2019-10-26 01:05:00

最近上报的IP列表

119.125.70.157 119.127.52.43 119.128.235.242 119.125.104.36
119.129.99.168 119.123.76.160 119.13.78.168 119.13.104.249
119.129.98.62 119.130.106.115 119.13.107.252 119.131.91.34
119.131.222.195 119.131.180.87 119.133.0.66 119.133.139.57
119.133.210.46 119.130.70.75 119.132.11.57 119.134.101.73