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

城市(city): Oklahoma City

省份(region): Oklahoma

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.97.221.235.			IN	A

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

;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Aug 01 09:05:51 CST 2020
;; MSG SIZE  rcvd: 117
HOST信息:
235.221.97.68.in-addr.arpa domain name pointer ip68-97-221-235.ok.ok.cox.net.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
235.221.97.68.in-addr.arpa	name = ip68-97-221-235.ok.ok.cox.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
122.245.173.75 attackspambots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/122.245.173.75/ 
 
 CN - 1H : (754)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4134 
 
 IP : 122.245.173.75 
 
 CIDR : 122.244.0.0/15 
 
 PREFIX COUNT : 5430 
 
 UNIQUE IP COUNT : 106919680 
 
 
 ATTACKS DETECTED ASN4134 :  
  1H - 11 
  3H - 39 
  6H - 75 
 12H - 150 
 24H - 306 
 
 DateTime : 2019-10-30 12:48:05 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-31 01:57:45
185.178.45.219 attackbotsspam
LGS,WP GET /wp-login.php
2019-10-31 01:57:08
13.93.86.6 attack
RDP Bruteforce
2019-10-31 01:36:24
34.80.183.219 attackbotsspam
Oct 30 15:42:30 vps647732 sshd[27043]: Failed password for root from 34.80.183.219 port 42116 ssh2
...
2019-10-31 02:08:59
186.31.116.78 attackspam
" "
2019-10-31 01:51:53
90.154.206.53 attackbots
Lines containing failures of 90.154.206.53
Oct 30 12:41:42 shared03 postfix/smtpd[13926]: connect from 90-154-206-53.ip.btc-net.bg[90.154.206.53]
Oct 30 12:41:43 shared03 policyd-spf[13951]: prepend Received-SPF: Softfail (mailfrom) identhostnamey=mailfrom; client-ip=90.154.206.53; helo=90-154-206-53.ip.btc-net.bg; envelope-from=x@x
Oct x@x
Oct 30 12:41:44 shared03 postfix/smtpd[13926]: lost connection after DATA from 90-154-206-53.ip.btc-net.bg[90.154.206.53]
Oct 30 12:41:44 shared03 postfix/smtpd[13926]: disconnect from 90-154-206-53.ip.btc-net.bg[90.154.206.53] ehlo=1 mail=1 rcpt=0/1 data=0/1 commands=2/4


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=90.154.206.53
2019-10-31 02:07:38
201.238.239.151 attackspambots
Oct 30 13:52:05 ns381471 sshd[12486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.238.239.151
Oct 30 13:52:07 ns381471 sshd[12486]: Failed password for invalid user q1w2e3r4t from 201.238.239.151 port 44086 ssh2
2019-10-31 01:40:25
119.203.240.76 attackbotsspam
Oct 30 13:49:35 web8 sshd\[31574\]: Invalid user Design@2017 from 119.203.240.76
Oct 30 13:49:35 web8 sshd\[31574\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76
Oct 30 13:49:37 web8 sshd\[31574\]: Failed password for invalid user Design@2017 from 119.203.240.76 port 28736 ssh2
Oct 30 13:55:35 web8 sshd\[2290\]: Invalid user technojazz from 119.203.240.76
Oct 30 13:55:35 web8 sshd\[2290\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76
2019-10-31 02:11:01
81.22.45.190 attackbots
Oct 30 18:24:33 mc1 kernel: \[3742595.702585\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.190 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=27151 PROTO=TCP SPT=46310 DPT=38916 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 30 18:26:40 mc1 kernel: \[3742722.656640\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.190 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=22092 PROTO=TCP SPT=46310 DPT=38883 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 30 18:27:26 mc1 kernel: \[3742769.218836\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.190 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=33320 PROTO=TCP SPT=46310 DPT=38697 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-31 01:54:28
159.203.201.143 attackbots
10/30/2019-12:48:44.444801 159.203.201.143 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-31 01:41:02
209.50.54.22 attack
Oct 30 18:42:50 docs sshd\[45573\]: Invalid user kdk from 209.50.54.22Oct 30 18:42:52 docs sshd\[45573\]: Failed password for invalid user kdk from 209.50.54.22 port 51604 ssh2Oct 30 18:46:40 docs sshd\[45683\]: Invalid user alinus from 209.50.54.22Oct 30 18:46:42 docs sshd\[45683\]: Failed password for invalid user alinus from 209.50.54.22 port 34918 ssh2Oct 30 18:50:29 docs sshd\[45788\]: Invalid user 123456789 from 209.50.54.22Oct 30 18:50:32 docs sshd\[45788\]: Failed password for invalid user 123456789 from 209.50.54.22 port 46462 ssh2
...
2019-10-31 01:43:18
58.219.127.217 attackbots
Oct 30 07:48:58 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[58.219.127.217]
Oct 30 07:49:00 esmtp postfix/smtpd[2798]: lost connection after AUTH from unknown[58.219.127.217]
Oct 30 07:49:05 esmtp postfix/smtpd[2783]: lost connection after AUTH from unknown[58.219.127.217]
Oct 30 07:49:08 esmtp postfix/smtpd[2783]: lost connection after AUTH from unknown[58.219.127.217]
Oct 30 07:49:10 esmtp postfix/smtpd[2783]: lost connection after AUTH from unknown[58.219.127.217]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=58.219.127.217
2019-10-31 01:28:25
189.7.25.34 attackspam
2019-10-30T14:00:40.281358  sshd[1214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.7.25.34  user=root
2019-10-30T14:00:42.349060  sshd[1214]: Failed password for root from 189.7.25.34 port 50901 ssh2
2019-10-30T14:06:26.502129  sshd[1261]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.7.25.34  user=root
2019-10-30T14:06:29.071335  sshd[1261]: Failed password for root from 189.7.25.34 port 42780 ssh2
2019-10-30T14:12:11.680512  sshd[1311]: Invalid user ld from 189.7.25.34 port 34664
...
2019-10-31 02:11:46
222.83.210.72 attackspambots
10/30/2019-12:49:05.860283 222.83.210.72 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-31 01:30:47
36.110.217.169 attack
Oct 30 15:32:00 localhost sshd\[26384\]: Invalid user ltidc2008 from 36.110.217.169
Oct 30 15:32:00 localhost sshd\[26384\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.217.169
Oct 30 15:32:02 localhost sshd\[26384\]: Failed password for invalid user ltidc2008 from 36.110.217.169 port 39326 ssh2
Oct 30 15:38:08 localhost sshd\[26743\]: Invalid user super8888 from 36.110.217.169
Oct 30 15:38:08 localhost sshd\[26743\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.217.169
...
2019-10-31 01:45:33

最近上报的IP列表

69.29.115.57 88.153.73.82 77.17.75.70 182.165.231.200
110.26.72.199 180.32.210.15 199.218.67.49 59.96.243.67
190.90.123.201 189.146.7.156 190.231.71.245 187.143.5.158
109.30.126.15 184.63.24.90 112.13.92.162 117.44.190.71
201.192.230.186 183.108.5.204 220.220.100.115 93.143.111.147