City: unknown
Region: unknown
Country: IANA Special-Purpose Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 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
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
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
#
# 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.64
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37795
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.64. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026012600 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 26 19:56:30 CST 2026
;; MSG SIZE rcvd: 105Host 64.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 64.0.168.192.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 41.235.46.51 | attack | Jul 7 15:47:03 [munged] sshd[13424]: Invalid user admin from 41.235.46.51 port 50629 Jul 7 15:47:03 [munged] sshd[13424]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.235.46.51 |
2019-07-07 22:22:18 |
| 103.114.104.86 | attack | RDP Scan |
2019-07-07 22:14:54 |
| 183.89.4.203 | attack | Attempted to connect 3 times to port 81 TCP |
2019-07-07 23:09:12 |
| 58.244.188.78 | attackspambots | Jul 7 15:47:24 ns3042688 courier-imapd: LOGIN FAILED, method=PLAIN, ip=\[::ffff:58.244.188.78\] ... |
2019-07-07 22:09:11 |
| 46.14.230.202 | attack | Jul 7 15:43:42 Ubuntu-1404-trusty-64-minimal sshd\[20436\]: Invalid user usuario from 46.14.230.202 Jul 7 15:43:42 Ubuntu-1404-trusty-64-minimal sshd\[20436\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.14.230.202 Jul 7 15:43:44 Ubuntu-1404-trusty-64-minimal sshd\[20436\]: Failed password for invalid user usuario from 46.14.230.202 port 41121 ssh2 Jul 7 15:46:19 Ubuntu-1404-trusty-64-minimal sshd\[21881\]: Invalid user job from 46.14.230.202 Jul 7 15:46:19 Ubuntu-1404-trusty-64-minimal sshd\[21881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.14.230.202 |
2019-07-07 22:45:34 |
| 179.167.50.62 | attack | SSH/22 MH Probe, BF, Hack - |
2019-07-07 22:23:59 |
| 112.4.172.182 | attackbotsspam | failed_logins |
2019-07-07 22:38:00 |
| 151.80.203.32 | attack | Jul 5 18:58:15 twattle sshd[6503]: Did not receive identification stri= ng from 151.80.203.32 Jul 5 18:59:45 twattle sshd[6504]: Invalid user t from 151.80.203.32 Jul 5 18:59:45 twattle sshd[6504]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:00:25 twattle sshd[6912]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:01:22 twattle sshd[6914]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:02:03 twattle sshd[6917]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:02:46 twattle sshd[6919]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:03:42 twattle sshd[6921]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:04:24 twattle sshd[6923]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:06:03 twattle sshd[7315]: Received disconnect from 151.80.203= .32: 11: Bye Bye [preauth] Jul 5 19:06:46 twa........ ------------------------------- |
2019-07-07 22:49:32 |
| 96.9.88.50 | attackspam | Trying ports that it shouldn't be. |
2019-07-07 22:40:28 |
| 125.115.178.149 | attackbots | 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x 2019-07-07 x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=125.115.178.149 |
2019-07-07 22:39:55 |
| 128.199.182.235 | attackspambots | 2019-07-07T14:18:33.494523abusebot-6.cloudsearch.cf sshd\[11210\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.182.235 user=root |
2019-07-07 23:05:55 |
| 137.74.176.208 | attack | Jul 7 16:16:38 vmd17057 sshd\[18908\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.176.208 user=root Jul 7 16:16:40 vmd17057 sshd\[18908\]: Failed password for root from 137.74.176.208 port 49448 ssh2 Jul 7 16:20:18 vmd17057 sshd\[19184\]: Invalid user peter from 137.74.176.208 port 54072 ... |
2019-07-07 22:24:36 |
| 222.186.52.123 | attack | 19/7/7@10:49:13: FAIL: IoT-SSH address from=222.186.52.123 ... |
2019-07-07 22:53:54 |
| 159.69.221.40 | attack | Jul 7 15:46:08 dcd-gentoo sshd[14154]: Invalid user Stockholm from 159.69.221.40 port 58027 Jul 7 15:46:10 dcd-gentoo sshd[14154]: error: PAM: Authentication failure for illegal user Stockholm from 159.69.221.40 Jul 7 15:46:08 dcd-gentoo sshd[14154]: Invalid user Stockholm from 159.69.221.40 port 58027 Jul 7 15:46:10 dcd-gentoo sshd[14154]: error: PAM: Authentication failure for illegal user Stockholm from 159.69.221.40 Jul 7 15:46:08 dcd-gentoo sshd[14154]: Invalid user Stockholm from 159.69.221.40 port 58027 Jul 7 15:46:10 dcd-gentoo sshd[14154]: error: PAM: Authentication failure for illegal user Stockholm from 159.69.221.40 Jul 7 15:46:10 dcd-gentoo sshd[14154]: Failed keyboard-interactive/pam for invalid user Stockholm from 159.69.221.40 port 58027 ssh2 ... |
2019-07-07 22:49:10 |
| 81.1.244.182 | attackspambots | TCP port 5555 (Trojan) attempt blocked by firewall. [2019-07-07 15:45:31] |
2019-07-07 22:19:30 |