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
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.44
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64044
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.44. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026050800 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 08 14:53:26 CST 2026
;; MSG SIZE rcvd: 105Host 44.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 44.0.168.192.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 119.29.174.51 | attack | Connection by 119.29.174.51 on port: 23 got caught by honeypot at 11/2/2019 7:35:20 AM |
2019-11-02 18:24:29 |
| 51.77.148.248 | attack | Nov 2 10:06:43 MK-Soft-VM7 sshd[1960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.148.248 Nov 2 10:06:44 MK-Soft-VM7 sshd[1960]: Failed password for invalid user P@55w0rd from 51.77.148.248 port 37698 ssh2 ... |
2019-11-02 18:29:13 |
| 192.227.128.241 | attackspambots | pixelfritteuse.de 192.227.128.241 \[02/Nov/2019:07:23:26 +0100\] "POST /wp-login.php HTTP/1.1" 200 5627 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" pixelfritteuse.de 192.227.128.241 \[02/Nov/2019:07:23:27 +0100\] "POST /xmlrpc.php HTTP/1.1" 200 4120 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2019-11-02 18:24:05 |
| 109.87.200.193 | attack | [munged]::443 109.87.200.193 - - [02/Nov/2019:10:52:14 +0100] "POST /[munged]: HTTP/1.1" 200 6626 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2019-11-02 18:28:44 |
| 117.132.175.25 | attack | Oct 5 14:50:07 localhost sshd\[19269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.132.175.25 user=root Oct 5 14:50:09 localhost sshd\[19269\]: Failed password for root from 117.132.175.25 port 40768 ssh2 Oct 5 15:25:06 localhost sshd\[19606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.132.175.25 user=root Oct 5 15:25:08 localhost sshd\[19606\]: Failed password for root from 117.132.175.25 port 53121 ssh2 |
2019-11-02 18:19:47 |
| 54.39.50.204 | attackbotsspam | Nov 2 10:58:33 ns381471 sshd[1191]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.50.204 Nov 2 10:58:35 ns381471 sshd[1191]: Failed password for invalid user ftpuser from 54.39.50.204 port 12890 ssh2 |
2019-11-02 18:19:07 |
| 192.144.151.30 | attack | Nov 2 13:07:49 server sshd\[18486\]: Invalid user test from 192.144.151.30 Nov 2 13:07:49 server sshd\[18486\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.151.30 Nov 2 13:07:51 server sshd\[18486\]: Failed password for invalid user test from 192.144.151.30 port 43478 ssh2 Nov 2 13:21:08 server sshd\[21748\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.151.30 user=root Nov 2 13:21:09 server sshd\[21748\]: Failed password for root from 192.144.151.30 port 60242 ssh2 ... |
2019-11-02 18:35:57 |
| 116.196.85.71 | attackspam | Invalid user oprofile from 116.196.85.71 port 43672 |
2019-11-02 18:34:35 |
| 106.75.17.91 | attackspam | 2019-11-02T09:16:12.207244abusebot-5.cloudsearch.cf sshd\[22656\]: Invalid user dice from 106.75.17.91 port 38444 |
2019-11-02 18:38:07 |
| 180.76.142.91 | attackbotsspam | Invalid user ftpuser from 180.76.142.91 port 60624 |
2019-11-02 18:43:27 |
| 106.13.48.20 | attack | Invalid user murai1 from 106.13.48.20 port 57416 |
2019-11-02 18:30:49 |
| 81.22.45.253 | attack | Nov 2 09:48:35 TCP Attack: SRC=81.22.45.253 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=240 PROTO=TCP SPT=56079 DPT=41446 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-11-02 18:49:33 |
| 91.121.103.175 | attackspam | Invalid user ki from 91.121.103.175 port 49224 |
2019-11-02 18:33:47 |
| 54.149.143.4 | attackspambots | Automatic report - Web App Attack |
2019-11-02 18:28:04 |
| 52.232.31.246 | attackspambots | SSH brutforce |
2019-11-02 18:38:23 |