城市(city): unknown
省份(region): unknown
国家(country): IANA Special-Purpose Address
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 192.168.0.1 | attacknormal | Key |
2022-05-06 06:58:56 |
| 192.168.0.1 | attack | Key |
2022-05-06 06:58:42 |
| 192.168.0.1 | attack | Key |
2022-05-06 06:58:34 |
| 192.168.0.1 | spambotsattackproxynormal | Lik@ |
2022-03-13 23:19:12 |
| 192.168.0.1 | spambotsattackproxynormal | M@lik@12 |
2022-03-13 23:18:45 |
| 192.168.0.10 | normal | Olá nego |
2021-08-12 23:02:04 |
| 192.168.0.11 | attack | Port Scan ... |
2020-08-26 23:17:23 |
| 192.168.0.11 | attackspambots | Port Scan ... |
2020-08-22 03:58:19 |
| 192.168.0.100 | spambotsproxynormal | Aparelhos conectados |
2020-08-18 10:20:03 |
| 192.168.0.100 | spambotsattackproxynormal | Aparelhos conectados |
2020-08-18 10:17:15 |
| 192.168.0.1 | attackbotsspam | Port scan |
2020-08-10 15:32:09 |
| 192.168.0.1 | attack | Port scan |
2020-07-03 23:47:45 |
| 192.168.0.1 | attackspambots | Port scan |
2020-06-09 15:06:45 |
| 192.168.0.186 | attackbotsspam | fire |
2019-11-17 02:37:09 |
| 192.168.0.101 | attackspam | Port 1433 Scan |
2019-10-24 02:25:48 |
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 192.168.0.0 - 192.168.255.255
CIDR: 192.168.0.0/16
NetName: PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
NetHandle: NET-192-168-0-0-1
Parent: NET192 (NET-192-0-0-0-0)
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1994-03-15
Updated: 2024-05-24
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
Comment:
Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment: http://datatracker.ietf.org/doc/rfc1918
Ref: https://rdap.arin.net/registry/ip/192.168.0.0
OrgName: Internet Assigned Numbers Authority
OrgId: IANA
Address: 12025 Waterfront Drive
Address: Suite 300
City: Los Angeles
StateProv: CA
PostalCode: 90292
Country: US
RegDate:
Updated: 2024-05-24
Ref: https://rdap.arin.net/registry/entity/IANA
OrgTechHandle: IANA-IP-ARIN
OrgTechName: ICANN
OrgTechPhone: +1-310-301-5820
OrgTechEmail: abuse@iana.org
OrgTechRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: ICANN
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: abuse@iana.org
OrgAbuseRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.168.0.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3139
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.214. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026031300 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 13 19:26:15 CST 2026
;; MSG SIZE rcvd: 106Host 214.0.168.192.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 214.0.168.192.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 106.13.45.243 | attack | Dec 7 05:39:47 Ubuntu-1404-trusty-64-minimal sshd\[27135\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.243 user=root Dec 7 05:39:49 Ubuntu-1404-trusty-64-minimal sshd\[27135\]: Failed password for root from 106.13.45.243 port 52796 ssh2 Dec 7 05:54:47 Ubuntu-1404-trusty-64-minimal sshd\[2353\]: Invalid user server from 106.13.45.243 Dec 7 05:54:47 Ubuntu-1404-trusty-64-minimal sshd\[2353\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.243 Dec 7 05:54:49 Ubuntu-1404-trusty-64-minimal sshd\[2353\]: Failed password for invalid user server from 106.13.45.243 port 53442 ssh2 |
2019-12-07 13:29:23 |
| 46.0.203.166 | attack | Dec 7 07:54:27 hosting sshd[30904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166 user=root Dec 7 07:54:29 hosting sshd[30904]: Failed password for root from 46.0.203.166 port 46642 ssh2 ... |
2019-12-07 13:46:29 |
| 116.196.80.104 | attack | Dec 6 23:03:54 mail sshd[1431]: Failed password for root from 116.196.80.104 port 47674 ssh2 Dec 6 23:11:08 mail sshd[3259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.196.80.104 Dec 6 23:11:10 mail sshd[3259]: Failed password for invalid user awhite from 116.196.80.104 port 48976 ssh2 |
2019-12-07 13:28:20 |
| 14.248.116.174 | attack | Dec 7 05:54:49 dev sshd\[1512\]: Invalid user admin from 14.248.116.174 port 54205 Dec 7 05:54:49 dev sshd\[1512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.248.116.174 Dec 7 05:54:51 dev sshd\[1512\]: Failed password for invalid user admin from 14.248.116.174 port 54205 ssh2 |
2019-12-07 13:25:26 |
| 222.186.173.180 | attack | Dec 7 05:43:31 thevastnessof sshd[14609]: Failed password for root from 222.186.173.180 port 7810 ssh2 ... |
2019-12-07 13:44:43 |
| 94.191.48.152 | attackspam | Dec 7 07:44:14 server sshd\[7773\]: Invalid user guest from 94.191.48.152 Dec 7 07:44:14 server sshd\[7773\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.48.152 Dec 7 07:44:16 server sshd\[7773\]: Failed password for invalid user guest from 94.191.48.152 port 56130 ssh2 Dec 7 07:54:30 server sshd\[10819\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.48.152 user=root Dec 7 07:54:31 server sshd\[10819\]: Failed password for root from 94.191.48.152 port 53646 ssh2 ... |
2019-12-07 13:39:52 |
| 129.204.76.34 | attackbotsspam | Dec 6 19:08:52 php1 sshd\[7037\]: Invalid user user from 129.204.76.34 Dec 6 19:08:52 php1 sshd\[7037\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.76.34 Dec 6 19:08:55 php1 sshd\[7037\]: Failed password for invalid user user from 129.204.76.34 port 44006 ssh2 Dec 6 19:16:12 php1 sshd\[7898\]: Invalid user liddiard from 129.204.76.34 Dec 6 19:16:12 php1 sshd\[7898\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.76.34 |
2019-12-07 13:27:22 |
| 142.93.101.148 | attackbotsspam | Triggered by Fail2Ban at Vostok web server |
2019-12-07 13:47:35 |
| 144.48.110.182 | attackspam | Dec 7 06:44:52 MK-Soft-VM4 sshd[26915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.48.110.182 Dec 7 06:44:54 MK-Soft-VM4 sshd[26915]: Failed password for invalid user ubnt from 144.48.110.182 port 55210 ssh2 ... |
2019-12-07 13:54:40 |
| 147.135.255.107 | attackbots | Dec 7 00:29:29 plusreed sshd[23714]: Invalid user culleyb from 147.135.255.107 ... |
2019-12-07 13:41:13 |
| 167.172.203.211 | attack | 2019-12-07T05:32:20.415792shield sshd\[9736\]: Invalid user ts3bot from 167.172.203.211 port 51836 2019-12-07T05:32:20.421331shield sshd\[9736\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.203.211 2019-12-07T05:32:22.099550shield sshd\[9736\]: Failed password for invalid user ts3bot from 167.172.203.211 port 51836 ssh2 2019-12-07T05:32:55.647957shield sshd\[9965\]: Invalid user bng from 167.172.203.211 port 50106 2019-12-07T05:32:55.653839shield sshd\[9965\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.203.211 |
2019-12-07 13:37:08 |
| 91.234.194.246 | attackbots | xmlrpc attack |
2019-12-07 13:45:11 |
| 84.201.175.164 | attack | $f2bV_matches |
2019-12-07 13:46:55 |
| 165.22.58.247 | attackbotsspam | Dec 7 05:54:25 * sshd[7995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.58.247 Dec 7 05:54:27 * sshd[7995]: Failed password for invalid user sennewald from 165.22.58.247 port 58670 ssh2 |
2019-12-07 13:48:51 |
| 188.166.228.244 | attackbots | Dec 7 01:42:28 ws24vmsma01 sshd[174874]: Failed password for root from 188.166.228.244 port 55736 ssh2 ... |
2019-12-07 13:50:21 |