必须是合法有效的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 <<>> 67.94.144.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57306
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;67.94.144.20.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 23:30:06 CST 2025
;; MSG SIZE  rcvd: 105
HOST信息:
20.144.94.67.in-addr.arpa domain name pointer ip67-94-144-20.z144-94-67.customer.algx.net.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
20.144.94.67.in-addr.arpa	name = ip67-94-144-20.z144-94-67.customer.algx.net.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
89.252.160.125 attack
Jun 10 00:46:33 debian kernel: [641749.498785] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=89.252.160.125 DST=89.252.131.35 LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=25628 DF PROTO=TCP SPT=64792 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0
2020-06-10 06:21:14
182.16.174.166 attackbotsspam
ID_MNT-APJII-ID_<177>1591733932 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2]:  {TCP} 182.16.174.166:5652
2020-06-10 06:18:29
222.186.175.154 attack
Jun  9 22:15:19 localhost sshd[108157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Jun  9 22:15:21 localhost sshd[108157]: Failed password for root from 222.186.175.154 port 2090 ssh2
Jun  9 22:15:24 localhost sshd[108157]: Failed password for root from 222.186.175.154 port 2090 ssh2
Jun  9 22:15:19 localhost sshd[108157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Jun  9 22:15:21 localhost sshd[108157]: Failed password for root from 222.186.175.154 port 2090 ssh2
Jun  9 22:15:24 localhost sshd[108157]: Failed password for root from 222.186.175.154 port 2090 ssh2
Jun  9 22:15:19 localhost sshd[108157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Jun  9 22:15:21 localhost sshd[108157]: Failed password for root from 222.186.175.154 port 2090 ssh2
Jun  9 22:15:24 localhost sshd
...
2020-06-10 06:20:28
122.114.247.244 attack
Jun  9 23:21:14 sd1 sshd[2789]: Invalid user llin from 122.114.247.244
Jun  9 23:21:14 sd1 sshd[2789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.247.244
Jun  9 23:21:16 sd1 sshd[2789]: Failed password for invalid user llin from 122.114.247.244 port 35712 ssh2
Jun  9 23:43:52 sd1 sshd[3418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.247.244  user=r.r
Jun  9 23:43:54 sd1 sshd[3418]: Failed password for r.r from 122.114.247.244 port 47876 ssh2

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=122.114.247.244
2020-06-10 06:45:12
148.70.178.70 attackbotsspam
detected by Fail2Ban
2020-06-10 06:32:21
49.235.29.226 attackbots
Jun  9 16:18:30 mail sshd\[35436\]: Invalid user 2k17 from 49.235.29.226
Jun  9 16:18:30 mail sshd\[35436\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.29.226
...
2020-06-10 06:33:23
170.0.51.189 attackbotsspam
(smtpauth) Failed SMTP AUTH login from 170.0.51.189 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-06-10 00:48:31 plain authenticator failed for ([170.0.51.189]) [170.0.51.189]: 535 Incorrect authentication data (set_id=info)
2020-06-10 06:29:54
124.251.110.148 attackbots
2020-06-09T21:52:19.204423shield sshd\[19811\]: Invalid user murai1 from 124.251.110.148 port 52598
2020-06-09T21:52:19.208285shield sshd\[19811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.251.110.148
2020-06-09T21:52:21.108482shield sshd\[19811\]: Failed password for invalid user murai1 from 124.251.110.148 port 52598 ssh2
2020-06-09T21:54:51.649850shield sshd\[20972\]: Invalid user vmail from 124.251.110.148 port 49480
2020-06-09T21:54:51.653631shield sshd\[20972\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.251.110.148
2020-06-10 06:25:43
103.78.81.227 attackbotsspam
30. On Jun 9 2020 experienced a Brute Force SSH login attempt -> 24 unique times by 103.78.81.227.
2020-06-10 06:49:41
118.24.114.205 attackspambots
Jun  9 23:19:04 h1745522 sshd[29224]: Invalid user 123 from 118.24.114.205 port 44706
Jun  9 23:19:04 h1745522 sshd[29224]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.114.205
Jun  9 23:19:04 h1745522 sshd[29224]: Invalid user 123 from 118.24.114.205 port 44706
Jun  9 23:19:06 h1745522 sshd[29224]: Failed password for invalid user 123 from 118.24.114.205 port 44706 ssh2
Jun  9 23:23:25 h1745522 sshd[29473]: Invalid user call from 118.24.114.205 port 38134
Jun  9 23:23:25 h1745522 sshd[29473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.114.205
Jun  9 23:23:25 h1745522 sshd[29473]: Invalid user call from 118.24.114.205 port 38134
Jun  9 23:23:26 h1745522 sshd[29473]: Failed password for invalid user call from 118.24.114.205 port 38134 ssh2
Jun  9 23:27:39 h1745522 sshd[29747]: Invalid user letmein123 from 118.24.114.205 port 59788
...
2020-06-10 06:27:33
131.255.236.182 attack
20/6/9@16:18:34: FAIL: Alarm-Network address from=131.255.236.182
20/6/9@16:18:34: FAIL: Alarm-Network address from=131.255.236.182
...
2020-06-10 06:30:36
24.227.134.59 attackspam
SMB Server BruteForce Attack
2020-06-10 06:39:03
127.0.0.1 attackspam
Test Connectivity
2020-06-10 06:15:14
8.48.248.93 attackbotsspam
Brute forcing email accounts
2020-06-10 06:48:21
124.127.118.179 attackbots
2020-06-09T22:38:38.880673abusebot.cloudsearch.cf sshd[1599]: Invalid user redis from 124.127.118.179 port 41514
2020-06-09T22:38:38.886043abusebot.cloudsearch.cf sshd[1599]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.127.118.179
2020-06-09T22:38:38.880673abusebot.cloudsearch.cf sshd[1599]: Invalid user redis from 124.127.118.179 port 41514
2020-06-09T22:38:40.961455abusebot.cloudsearch.cf sshd[1599]: Failed password for invalid user redis from 124.127.118.179 port 41514 ssh2
2020-06-09T22:41:52.363873abusebot.cloudsearch.cf sshd[1891]: Invalid user bot from 124.127.118.179 port 47008
2020-06-09T22:41:52.369338abusebot.cloudsearch.cf sshd[1891]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.127.118.179
2020-06-09T22:41:52.363873abusebot.cloudsearch.cf sshd[1891]: Invalid user bot from 124.127.118.179 port 47008
2020-06-09T22:41:54.745696abusebot.cloudsearch.cf sshd[1891]: Failed password for 
...
2020-06-10 06:49:11

最近上报的IP列表

215.44.58.175 33.162.203.134 188.101.7.215 127.139.118.89
199.109.189.41 75.69.27.248 43.26.173.203 221.230.144.165
238.245.196.125 204.85.244.199 236.34.32.75 130.169.89.247
201.114.74.227 224.41.170.82 204.137.203.118 186.90.49.194
235.42.139.176 147.47.84.53 109.123.136.216 89.125.185.17