城市(city): unknown
省份(region): unknown
国家(country): Hong Kong
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '217.194.132.0 - 217.194.135.255'
% No abuse contact registered for 217.194.132.0 - 217.194.135.255
inetnum: 217.194.132.0 - 217.194.135.255
netname: NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK
descr: IPv4 address block not managed by the RIPE NCC
remarks: ------------------------------------------------------
remarks:
remarks: For registration information,
remarks: you can consult the following sources:
remarks:
remarks: IANA
remarks: http://www.iana.org/assignments/ipv4-address-space
remarks: http://www.iana.org/assignments/iana-ipv4-special-registry
remarks: http://www.iana.org/assignments/ipv4-recovered-address-space
remarks:
remarks: AFRINIC (Africa)
remarks: http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks: APNIC (Asia Pacific)
remarks: http://www.apnic.net/ whois.apnic.net
remarks:
remarks: ARIN (Northern America)
remarks: http://www.arin.net/ whois.arin.net
remarks:
remarks: LACNIC (Latin America and the Carribean)
remarks: http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks: ------------------------------------------------------
country: EU # Country is really world wide
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
status: ALLOCATED UNSPECIFIED
mnt-by: RIPE-NCC-HM-MNT
created: 2020-10-07T05:03:47Z
last-modified: 2020-10-07T05:03:47Z
source: RIPE
role: Internet Assigned Numbers Authority
address: see http://www.iana.org.
admin-c: IANA1-RIPE
tech-c: IANA1-RIPE
nic-hdl: IANA1-RIPE
remarks: For more information on IANA services
remarks: go to IANA web site at http://www.iana.org.
mnt-by: RIPE-NCC-MNT
created: 1970-01-01T00:00:00Z
last-modified: 2001-09-22T09:31:27Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.124.1 (ABERDEEN)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 217.194.133.254
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56931
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;217.194.133.254. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026110302 1800 900 604800 86400
;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Nov 04 02:55:56 CST 2026
;; MSG SIZE rcvd: 108
Host 254.133.194.217.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 254.133.194.217.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 178.170.146.65 | attackspambots | Feb 3 06:32:11 mout sshd[24491]: Invalid user eldora from 178.170.146.65 port 47674 |
2020-02-03 13:39:20 |
| 184.82.237.107 | attackspam | 1580705644 - 02/03/2020 05:54:04 Host: 184.82.237.107/184.82.237.107 Port: 445 TCP Blocked |
2020-02-03 14:10:20 |
| 189.114.33.112 | attack | Automatic report - Port Scan Attack |
2020-02-03 14:03:33 |
| 180.211.135.146 | attackbotsspam | 1580705642 - 02/03/2020 05:54:02 Host: 180.211.135.146/180.211.135.146 Port: 445 TCP Blocked |
2020-02-03 14:12:05 |
| 162.245.81.36 | attackbots | Unauthorized connection attempt detected from IP address 162.245.81.36 to port 3389 [J] |
2020-02-03 13:53:18 |
| 140.186.7.52 | attack | Brute forcing email accounts |
2020-02-03 13:53:54 |
| 117.32.216.117 | attackspam | Feb 3 08:14:33 tuotantolaitos sshd[4880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.32.216.117 Feb 3 08:14:36 tuotantolaitos sshd[4880]: Failed password for invalid user risher from 117.32.216.117 port 11668 ssh2 ... |
2020-02-03 14:21:05 |
| 170.80.36.146 | attackbotsspam | Unauthorized connection attempt detected from IP address 170.80.36.146 to port 445 |
2020-02-03 13:50:09 |
| 96.84.177.225 | attackspambots | Feb 3 06:53:47 sd-53420 sshd\[1853\]: Invalid user jenkins from 96.84.177.225 Feb 3 06:53:47 sd-53420 sshd\[1853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.84.177.225 Feb 3 06:53:50 sd-53420 sshd\[1853\]: Failed password for invalid user jenkins from 96.84.177.225 port 44478 ssh2 Feb 3 06:56:57 sd-53420 sshd\[2143\]: Invalid user ftptest from 96.84.177.225 Feb 3 06:56:57 sd-53420 sshd\[2143\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.84.177.225 ... |
2020-02-03 14:06:45 |
| 94.176.234.220 | attack | Feb 3 05:16:27 *** sshd[26824]: Invalid user student09 from 94.176.234.220 |
2020-02-03 13:47:44 |
| 51.38.186.180 | attackbotsspam | Unauthorized connection attempt detected from IP address 51.38.186.180 to port 2220 [J] |
2020-02-03 14:18:08 |
| 196.192.110.64 | attackspam | Unauthorized connection attempt detected from IP address 196.192.110.64 to port 2220 [J] |
2020-02-03 13:39:39 |
| 14.141.174.123 | attack | Feb 3 05:51:38 rotator sshd\[20838\]: Address 14.141.174.123 maps to 14.141.174.123.static-vsnl.net.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Feb 3 05:51:38 rotator sshd\[20838\]: Invalid user guai123 from 14.141.174.123Feb 3 05:51:40 rotator sshd\[20838\]: Failed password for invalid user guai123 from 14.141.174.123 port 39238 ssh2Feb 3 05:54:17 rotator sshd\[20850\]: Address 14.141.174.123 maps to 14.141.174.123.static-vsnl.net.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Feb 3 05:54:17 rotator sshd\[20850\]: Invalid user 1234 from 14.141.174.123Feb 3 05:54:19 rotator sshd\[20850\]: Failed password for invalid user 1234 from 14.141.174.123 port 48223 ssh2 ... |
2020-02-03 13:54:19 |
| 185.45.72.159 | attackbots | Attacks websites by trying to access known vulnerables of plugins, brute-force of backends or probing of administrative tools |
2020-02-03 14:22:04 |
| 139.59.153.133 | attackspambots | Automatic report - XMLRPC Attack |
2020-02-03 14:19:30 |