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.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59406
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.140. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026012700 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 27 22:42:47 CST 2026
;; MSG SIZE rcvd: 106Host 140.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 140.0.168.192.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 36.103.243.247 | attackbotsspam | Oct 16 05:25:59 vpn01 sshd[29377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.103.243.247 Oct 16 05:26:00 vpn01 sshd[29377]: Failed password for invalid user jira from 36.103.243.247 port 48941 ssh2 ... |
2019-10-16 15:57:00 |
| 222.186.180.223 | attack | 2019-10-16T09:44:22.731061scmdmz1 sshd\[25252\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223 user=root 2019-10-16T09:44:24.772919scmdmz1 sshd\[25252\]: Failed password for root from 222.186.180.223 port 41306 ssh2 2019-10-16T09:44:28.757894scmdmz1 sshd\[25252\]: Failed password for root from 222.186.180.223 port 41306 ssh2 ... |
2019-10-16 15:57:14 |
| 176.31.128.45 | attackspambots | Oct 16 07:09:58 xeon sshd[63565]: Failed password for invalid user uftp from 176.31.128.45 port 46082 ssh2 |
2019-10-16 15:39:05 |
| 220.92.16.86 | attack | Oct 16 08:44:44 XXX sshd[43219]: Invalid user ofsaa from 220.92.16.86 port 38920 |
2019-10-16 16:04:15 |
| 210.242.157.12 | attackbotsspam | Brute force SMTP login attempted. ... |
2019-10-16 15:53:59 |
| 59.13.139.50 | attackspambots | Oct 16 07:08:13 icinga sshd[27574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.13.139.50 Oct 16 07:08:15 icinga sshd[27574]: Failed password for invalid user hp from 59.13.139.50 port 57092 ssh2 Oct 16 07:43:59 icinga sshd[51129]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.13.139.50 ... |
2019-10-16 15:42:51 |
| 71.6.199.23 | attack | 10/16/2019-08:35:13.626929 71.6.199.23 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 71 |
2019-10-16 15:27:26 |
| 41.89.160.13 | attackspam | Oct 16 10:06:53 areeb-Workstation sshd[28262]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.89.160.13 Oct 16 10:06:55 areeb-Workstation sshd[28262]: Failed password for invalid user yangzx456 from 41.89.160.13 port 60322 ssh2 ... |
2019-10-16 15:55:18 |
| 178.128.194.116 | attackbotsspam | Oct 16 11:24:13 areeb-Workstation sshd[11104]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.194.116 Oct 16 11:24:15 areeb-Workstation sshd[11104]: Failed password for invalid user debian@123 from 178.128.194.116 port 52488 ssh2 ... |
2019-10-16 16:02:56 |
| 182.139.134.107 | attack | Oct 16 08:51:20 vpn01 sshd[1330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.139.134.107 Oct 16 08:51:22 vpn01 sshd[1330]: Failed password for invalid user s3guridad from 182.139.134.107 port 56446 ssh2 ... |
2019-10-16 15:52:00 |
| 200.169.223.98 | attackbots | Oct 15 23:25:44 Tower sshd[21512]: Connection from 200.169.223.98 port 58916 on 192.168.10.220 port 22 Oct 15 23:25:46 Tower sshd[21512]: Failed password for root from 200.169.223.98 port 58916 ssh2 Oct 15 23:25:46 Tower sshd[21512]: Received disconnect from 200.169.223.98 port 58916:11: Bye Bye [preauth] Oct 15 23:25:46 Tower sshd[21512]: Disconnected from authenticating user root 200.169.223.98 port 58916 [preauth] |
2019-10-16 15:50:33 |
| 198.98.53.76 | attackbotsspam | Oct 16 09:07:27 MK-Soft-VM7 sshd[14111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.98.53.76 Oct 16 09:07:29 MK-Soft-VM7 sshd[14111]: Failed password for invalid user dm from 198.98.53.76 port 58632 ssh2 ... |
2019-10-16 16:01:54 |
| 23.129.64.209 | attackspam | Automatic report - XMLRPC Attack |
2019-10-16 15:26:50 |
| 109.224.22.34 | attackspam | postfix (unknown user, SPF fail or relay access denied) |
2019-10-16 15:46:24 |
| 36.155.115.137 | attackbots | Oct 15 21:19:09 wbs sshd\[17666\]: Invalid user guest from 36.155.115.137 Oct 15 21:19:09 wbs sshd\[17666\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.115.137 Oct 15 21:19:11 wbs sshd\[17666\]: Failed password for invalid user guest from 36.155.115.137 port 60667 ssh2 Oct 15 21:23:45 wbs sshd\[18055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.115.137 user=root Oct 15 21:23:47 wbs sshd\[18055\]: Failed password for root from 36.155.115.137 port 49949 ssh2 |
2019-10-16 15:36:44 |