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.217
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24551
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.217. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026072801 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jul 29 05:37:37 CST 2026
;; MSG SIZE rcvd: 106
Host 217.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 217.0.168.192.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 49.88.112.77 | attackbotsspam | 2019-11-03T13:52:30.621161abusebot-3.cloudsearch.cf sshd\[18740\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.77 user=root |
2019-11-03 21:56:29 |
| 206.81.11.216 | attack | Nov 3 13:56:21 legacy sshd[944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.81.11.216 Nov 3 13:56:23 legacy sshd[944]: Failed password for invalid user hulk from 206.81.11.216 port 44974 ssh2 Nov 3 14:00:04 legacy sshd[1110]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.81.11.216 ... |
2019-11-03 21:16:36 |
| 103.21.228.3 | attackspam | Automatic report - Banned IP Access |
2019-11-03 21:56:07 |
| 180.164.140.65 | attackspambots | Unauthorized connection attempt from IP address 180.164.140.65 on Port 445(SMB) |
2019-11-03 21:34:14 |
| 123.194.165.63 | attack | Unauthorized connection attempt from IP address 123.194.165.63 on Port 445(SMB) |
2019-11-03 21:28:48 |
| 222.112.65.55 | attackspambots | Nov 3 00:45:18 mockhub sshd[18344]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.112.65.55 Nov 3 00:45:19 mockhub sshd[18344]: Failed password for invalid user zxcpoi from 222.112.65.55 port 42266 ssh2 ... |
2019-11-03 21:17:33 |
| 51.38.224.46 | attackbots | Nov 3 08:31:09 localhost sshd[18888]: Failed password for root from 51.38.224.46 port 50906 ssh2 Nov 3 08:34:37 localhost sshd[18979]: Invalid user locamex from 51.38.224.46 port 60566 Nov 3 08:34:37 localhost sshd[18979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.224.46 Nov 3 08:34:37 localhost sshd[18979]: Invalid user locamex from 51.38.224.46 port 60566 Nov 3 08:34:39 localhost sshd[18979]: Failed password for invalid user locamex from 51.38.224.46 port 60566 ssh2 |
2019-11-03 21:48:51 |
| 186.147.35.76 | attack | Invalid user gozone from 186.147.35.76 port 53760 |
2019-11-03 21:36:30 |
| 139.59.81.223 | attackbotsspam | Fail2Ban Ban Triggered |
2019-11-03 21:55:49 |
| 113.22.236.105 | attackbotsspam | Unauthorized connection attempt from IP address 113.22.236.105 on Port 445(SMB) |
2019-11-03 21:17:20 |
| 182.71.119.170 | attack | Unauthorized connection attempt from IP address 182.71.119.170 on Port 445(SMB) |
2019-11-03 21:22:29 |
| 186.15.233.218 | attack | [ES hit] Tried to deliver spam. |
2019-11-03 21:41:13 |
| 121.138.213.2 | attack | Nov 3 14:23:53 ArkNodeAT sshd\[15964\]: Invalid user temp from 121.138.213.2 Nov 3 14:23:53 ArkNodeAT sshd\[15964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.138.213.2 Nov 3 14:23:55 ArkNodeAT sshd\[15964\]: Failed password for invalid user temp from 121.138.213.2 port 32376 ssh2 |
2019-11-03 21:43:23 |
| 219.91.207.210 | attackbots | Unauthorized connection attempt from IP address 219.91.207.210 on Port 445(SMB) |
2019-11-03 21:16:52 |
| 45.95.32.228 | attackspambots | Postfix RBL failed |
2019-11-03 21:55:18 |