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

城市(city): unknown

省份(region): unknown

国家(country): United States of America (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;68.138.40.140.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 03:27:46 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 140.40.138.68.in-addr.arpa not found: 2(SERVFAIL)
NSLOOKUP信息:
server can't find 68.138.40.140.in-addr.arpa: SERVFAIL
相关IP信息:
最新评论:
IP 类型 评论内容 时间
142.93.141.59 attackspambots
2019-07-11T23:07:45.019230scmdmz1 sshd\[6725\]: Invalid user eirik from 142.93.141.59 port 58754
2019-07-11T23:07:45.022033scmdmz1 sshd\[6725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=device-proxy.hosting.autoenterprise.com.ua
2019-07-11T23:07:46.620513scmdmz1 sshd\[6725\]: Failed password for invalid user eirik from 142.93.141.59 port 58754 ssh2
...
2019-07-12 05:08:28
142.4.213.95 attack
k+ssh-bruteforce
2019-07-12 05:23:02
141.226.2.231 attackbotsspam
May 16 10:11:37 server sshd\[62054\]: Invalid user byu from 141.226.2.231
May 16 10:11:37 server sshd\[62054\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.226.2.231
May 16 10:11:39 server sshd\[62054\]: Failed password for invalid user byu from 141.226.2.231 port 50700 ssh2
...
2019-07-12 05:30:14
139.59.59.90 attack
Jul 11 21:53:07 core01 sshd\[3284\]: Invalid user setup from 139.59.59.90 port 15452
Jul 11 21:53:07 core01 sshd\[3284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.59.90
...
2019-07-12 05:35:47
139.59.95.244 attack
2019-07-11T19:19:43.489391abusebot-2.cloudsearch.cf sshd\[16094\]: Invalid user web from 139.59.95.244 port 47856
2019-07-12 05:13:04
140.143.53.145 attack
Jul 12 03:00:00 vibhu-HP-Z238-Microtower-Workstation sshd\[23051\]: Invalid user ftpuser from 140.143.53.145
Jul 12 03:00:00 vibhu-HP-Z238-Microtower-Workstation sshd\[23051\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.53.145
Jul 12 03:00:03 vibhu-HP-Z238-Microtower-Workstation sshd\[23051\]: Failed password for invalid user ftpuser from 140.143.53.145 port 60394 ssh2
Jul 12 03:05:46 vibhu-HP-Z238-Microtower-Workstation sshd\[24195\]: Invalid user web3 from 140.143.53.145
Jul 12 03:05:46 vibhu-HP-Z238-Microtower-Workstation sshd\[24195\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.53.145
...
2019-07-12 05:38:01
142.44.137.62 attackspam
Triggered by Fail2Ban at Vostok web server
2019-07-12 05:19:38
191.53.221.234 attack
Currently 7 failed/unauthorized logins attempts via SMTP/IMAP whostnameh 6 different usernames and wrong password:
2019-07-11T15:43:02+02:00 x@x
2019-06-23T12:16:54+02:00 x@x
2018-02-20T00:48:05+01:00 Access from 191.53.221.234 whostnameh username "info" (Unknown account)
2018-02-03T11:15:11+01:00 Access from 191.53.221.234 whostnameh username "michael.haberler" (Unknown account)
2018-01-27T07:34:57+01:00 Access from 191.53.221.234 whostnameh username "michael.haberler" (Unknown account)
2017-12-31T06:22:55+01:00 Access from 191.53.221.234 whostnameh username "test" (Unknown account)
2017-12-10T02:38:16+01:00 Access from 191.53.221.234 whostnameh username "myspace" (Unknown account)

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=191.53.221.234
2019-07-12 05:14:52
140.143.26.232 attack
Jun 22 16:54:54 server sshd\[236287\]: Invalid user resolve from 140.143.26.232
Jun 22 16:54:54 server sshd\[236287\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.26.232
Jun 22 16:54:57 server sshd\[236287\]: Failed password for invalid user resolve from 140.143.26.232 port 44068 ssh2
...
2019-07-12 05:39:50
142.58.249.184 attackspam
Jun 10 07:51:15 server sshd\[143650\]: Invalid user admin from 142.58.249.184
Jun 10 07:51:15 server sshd\[143650\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.58.249.184
Jun 10 07:51:17 server sshd\[143650\]: Failed password for invalid user admin from 142.58.249.184 port 59653 ssh2
...
2019-07-12 05:14:32
76.24.160.205 attack
Unauthorized SSH login attempts
2019-07-12 05:13:21
140.206.32.247 attackspambots
Jun 14 07:39:06 server sshd\[141334\]: Invalid user hadoop from 140.206.32.247
Jun 14 07:39:06 server sshd\[141334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.206.32.247
Jun 14 07:39:09 server sshd\[141334\]: Failed password for invalid user hadoop from 140.206.32.247 port 34062 ssh2
...
2019-07-12 05:33:39
78.206.153.68 attack
SSH Brute-Force reported by Fail2Ban
2019-07-12 05:46:46
167.71.173.103 attackspam
10s of requests to none existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined
node-superagent/4.1.0
2019-07-12 05:43:50
45.122.220.167 attack
WordPress wp-login brute force :: 45.122.220.167 0.048 BYPASS [12/Jul/2019:00:08:20  1000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-12 05:23:32

最近上报的IP列表

116.73.66.74 77.45.182.158 152.194.190.130 37.35.131.106
202.150.238.105 16.131.69.9 20.191.137.175 84.97.90.0
12.116.197.184 155.172.245.166 234.28.210.137 159.174.103.208
46.221.37.2 31.72.142.235 23.1.64.53 147.134.109.49
201.48.177.83 202.141.20.136 91.87.217.226 165.53.135.158