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

城市(city): unknown

省份(region): unknown

国家(country): unknown

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;120.40.134.12.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 17:36:17 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
12.134.40.120.in-addr.arpa domain name pointer 12.134.40.120.broad.pt.fj.dynamic.163data.com.cn.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
12.134.40.120.in-addr.arpa	name = 12.134.40.120.broad.pt.fj.dynamic.163data.com.cn.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
106.12.216.155 attackbots
generic web scan
2020-07-04 09:50:57
185.143.73.162 attackbotsspam
Jul  4 03:22:18 relay postfix/smtpd\[24797\]: warning: unknown\[185.143.73.162\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  4 03:22:57 relay postfix/smtpd\[19779\]: warning: unknown\[185.143.73.162\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  4 03:23:36 relay postfix/smtpd\[24826\]: warning: unknown\[185.143.73.162\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  4 03:24:12 relay postfix/smtpd\[28270\]: warning: unknown\[185.143.73.162\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  4 03:24:53 relay postfix/smtpd\[28274\]: warning: unknown\[185.143.73.162\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-07-04 09:29:46
61.177.172.168 attackbotsspam
Jul  4 03:18:18 server sshd[20619]: Failed none for root from 61.177.172.168 port 27744 ssh2
Jul  4 03:18:21 server sshd[20619]: Failed password for root from 61.177.172.168 port 27744 ssh2
Jul  4 03:18:25 server sshd[20619]: Failed password for root from 61.177.172.168 port 27744 ssh2
2020-07-04 09:21:05
85.185.149.28 attackspambots
Jul  4 02:17:04 santamaria sshd\[22464\]: Invalid user prometey from 85.185.149.28
Jul  4 02:17:04 santamaria sshd\[22464\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.185.149.28
Jul  4 02:17:06 santamaria sshd\[22464\]: Failed password for invalid user prometey from 85.185.149.28 port 37414 ssh2
...
2020-07-04 09:18:22
178.62.9.122 attackbotsspam
178.62.9.122 - - [04/Jul/2020:03:42:38 +0200] "GET /wp-login.php HTTP/1.1" 200 5990 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
178.62.9.122 - - [04/Jul/2020:03:42:40 +0200] "POST /wp-login.php HTTP/1.1" 200 6220 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
178.62.9.122 - - [04/Jul/2020:03:42:40 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-07-04 09:44:55
1.192.94.61 attackbotsspam
Jul  4 03:17:34 dev0-dcde-rnet sshd[15348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.192.94.61
Jul  4 03:17:36 dev0-dcde-rnet sshd[15348]: Failed password for invalid user write from 1.192.94.61 port 42270 ssh2
Jul  4 03:20:27 dev0-dcde-rnet sshd[15361]: Failed password for nobody from 1.192.94.61 port 52914 ssh2
2020-07-04 09:26:07
27.78.71.238 attack
Honeypot attack, port: 81, PTR: localhost.
2020-07-04 09:23:15
46.38.150.191 attack
2020-07-04 01:18:25 auth_plain authenticator failed for (User) [46.38.150.191]: 535 Incorrect authentication data (set_id=auth2@mail.csmailer.org)
2020-07-04 01:19:02 auth_plain authenticator failed for (User) [46.38.150.191]: 535 Incorrect authentication data (set_id=1qaz2wsx@mail.csmailer.org)
2020-07-04 01:19:38 auth_plain authenticator failed for (User) [46.38.150.191]: 535 Incorrect authentication data (set_id=c21@mail.csmailer.org)
2020-07-04 01:20:25 auth_plain authenticator failed for (User) [46.38.150.191]: 535 Incorrect authentication data (set_id=margret@mail.csmailer.org)
2020-07-04 01:20:55 auth_plain authenticator failed for (User) [46.38.150.191]: 535 Incorrect authentication data (set_id=pacific@mail.csmailer.org)
...
2020-07-04 09:25:38
51.75.52.127 attackbotsspam
Jul  4 03:18:05 debian-2gb-nbg1-2 kernel: \[16084106.510357\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.75.52.127 DST=195.201.40.59 LEN=44 TOS=0x10 PREC=0x00 TTL=113 ID=45027 PROTO=TCP SPT=26200 DPT=3552 WINDOW=47392 RES=0x00 SYN URGP=0
2020-07-04 09:43:04
222.186.169.194 attack
Jul  4 03:22:32 sshgateway sshd\[29495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Jul  4 03:22:34 sshgateway sshd\[29495\]: Failed password for root from 222.186.169.194 port 12212 ssh2
Jul  4 03:22:47 sshgateway sshd\[29495\]: error: maximum authentication attempts exceeded for root from 222.186.169.194 port 12212 ssh2 \[preauth\]
2020-07-04 09:29:13
178.62.214.85 attackspambots
(sshd) Failed SSH login from 178.62.214.85 (NL/Netherlands/-): 5 in the last 3600 secs
2020-07-04 09:28:30
182.61.40.227 attackspam
Jul  4 01:15:43 gestao sshd[17610]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.227 
Jul  4 01:15:46 gestao sshd[17610]: Failed password for invalid user ts3 from 182.61.40.227 port 51786 ssh2
Jul  4 01:18:32 gestao sshd[17695]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.227 
...
2020-07-04 09:30:31
185.143.73.58 attackspam
2020-07-04 04:07:07 dovecot_login authenticator failed for \(User\) \[185.143.73.58\]: 535 Incorrect authentication data \(set_id=markus@org.ua\)2020-07-04 04:07:46 dovecot_login authenticator failed for \(User\) \[185.143.73.58\]: 535 Incorrect authentication data \(set_id=itest@org.ua\)2020-07-04 04:08:25 dovecot_login authenticator failed for \(User\) \[185.143.73.58\]: 535 Incorrect authentication data \(set_id=julietta@org.ua\)
...
2020-07-04 09:19:24
51.38.70.175 attack
2020-07-04T00:49:37.900186shield sshd\[6126\]: Invalid user stefan from 51.38.70.175 port 49284
2020-07-04T00:49:37.904287shield sshd\[6126\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.ip-51-38-70.eu
2020-07-04T00:49:40.389466shield sshd\[6126\]: Failed password for invalid user stefan from 51.38.70.175 port 49284 ssh2
2020-07-04T00:52:44.894940shield sshd\[6758\]: Invalid user krish from 51.38.70.175 port 47006
2020-07-04T00:52:44.899085shield sshd\[6758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.ip-51-38-70.eu
2020-07-04 09:25:02
23.94.5.104 attack
(From wanda.kellermann@msn.com) Hi,

Do you have a Website? Of course you do because I am looking at your website expresslifechiro.com now.

Are you struggling for Leads and Sales?

You’re not the only one.

So many Website owners struggle to convert their Visitors into Leads & Sales.

There’s a simple way to fix this problem.

You could use a Live Chat app on your Website expresslifechiro.com and hire Chat Agents.

But only if you’ve got deep pockets and you’re happy to fork out THOUSANDS of dollars for the quality you need.

=====

But what if you could automate Live Chat so it’s HUMAN-FREE?

What if you could exploit NEW “AI” Technology to engage with your Visitors INSTANTLY.

And AUTOMATICALLY convert them into Leads & Sales.

WITHOUT spending THOUSANDS of dollars on Live Chat Agents.

And WITHOUT hiring expensive coders.

In fact, all you need to do to activate this LATEST “AI” Website Tech..

..is to COPY & PASTE a single line of “Website Code”.

==> http://www.zoomsoft.n
2020-07-04 09:52:53

最近上报的IP列表

120.40.134.107 120.40.134.120 129.2.9.97 120.40.134.167
175.176.24.94 120.40.134.173 120.40.134.182 120.40.134.19
120.40.134.228 120.40.134.242 120.40.134.248 120.40.135.11
120.40.135.111 120.40.135.13 120.40.135.200 120.40.135.236
120.40.135.252 120.40.135.26 120.40.135.29 120.40.135.42