Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 42.233.121.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38303
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.233.121.164.			IN	A

;; AUTHORITY SECTION:
.			287	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022021300 1800 900 604800 86400

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 17:31:51 CST 2022
;; MSG SIZE  rcvd: 107
Host info
164.121.233.42.in-addr.arpa domain name pointer hn.kd.ny.adsl.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
164.121.233.42.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.35.64.73 attackspambots
2020-03-24 01:08:17,294 fail2ban.actions        \[3524\]: NOTICE  \[ssh\] Ban 103.35.64.73
2020-03-24 01:24:51,124 fail2ban.actions        \[3524\]: NOTICE  \[ssh\] Ban 103.35.64.73
2020-03-24 01:41:09,009 fail2ban.actions        \[3524\]: NOTICE  \[ssh\] Ban 103.35.64.73
2020-03-24 01:57:19,551 fail2ban.actions        \[3524\]: NOTICE  \[ssh\] Ban 103.35.64.73
2020-03-24 02:13:49,115 fail2ban.actions        \[3524\]: NOTICE  \[ssh\] Ban 103.35.64.73
...
2020-03-27 19:53:54
185.171.88.47 attackspam
20/3/26@23:47:22: FAIL: Alarm-Network address from=185.171.88.47
20/3/26@23:47:22: FAIL: Alarm-Network address from=185.171.88.47
...
2020-03-27 20:00:55
106.13.228.62 attackspambots
Mar 27 07:26:03 vps sshd[13493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.228.62 
Mar 27 07:26:04 vps sshd[13493]: Failed password for invalid user orm from 106.13.228.62 port 59892 ssh2
Mar 27 07:34:01 vps sshd[13945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.228.62 
...
2020-03-27 20:01:23
49.233.134.31 attackbots
Brute force attempt
2020-03-27 19:29:36
180.168.95.234 attackbotsspam
Mar 27 11:51:58 vpn01 sshd[10193]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.168.95.234
Mar 27 11:52:00 vpn01 sshd[10193]: Failed password for invalid user ftpadmin from 180.168.95.234 port 34598 ssh2
...
2020-03-27 19:45:55
114.119.166.181 attack
[Fri Mar 27 18:37:43.686660 2020] [:error] [pid 10138:tid 140229637863168] [client 114.119.166.181:56556] [client 114.119.166.181] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/profil/meteorologi/list-all-categories/347-profil-kantor/pengaduan"] [unique_id "Xn3lhzmade8y4or@zXtEXgAAAfE"]
...
2020-03-27 19:43:54
181.48.155.149 attack
Mar 27 03:22:11 server1 sshd\[2490\]: Failed password for invalid user admin from 181.48.155.149 port 38262 ssh2
Mar 27 03:22:11 server1 sshd\[2491\]: Failed password for invalid user admin from 181.48.155.149 port 38264 ssh2
Mar 27 03:26:28 server1 sshd\[4279\]: Invalid user vdi from 181.48.155.149
Mar 27 03:26:28 server1 sshd\[4279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.155.149 
Mar 27 03:26:28 server1 sshd\[4280\]: Invalid user vdi from 181.48.155.149
...
2020-03-27 19:53:31
188.212.173.2 attack
port scan and connect, tcp 80 (http)
2020-03-27 19:56:19
106.13.117.101 attackbots
$f2bV_matches
2020-03-27 19:38:10
118.24.200.40 attackbotsspam
(sshd) Failed SSH login from 118.24.200.40 (CN/China/-): 5 in the last 3600 secs
2020-03-27 20:00:08
222.186.31.83 attackspam
SSH Authentication Attempts Exceeded
2020-03-27 19:36:03
104.236.81.204 attack
2020-03-26 UTC: (2x) - postgres,ubuntu
2020-03-27 19:54:51
129.205.7.67 attackbots
DATE:2020-03-27 11:48:32,IP:129.205.7.67,MATCHES:11,PORT:ssh
2020-03-27 19:40:12
31.210.177.57 spambotsattackproxynormal
HAHA
2020-03-27 20:10:46
49.234.179.127 attackspambots
3x Failed Password
2020-03-27 19:52:28

Recently Reported IPs

42.232.255.186 42.233.126.160 42.232.254.63 42.233.139.238
42.233.120.168 42.233.143.203 42.233.173.41 42.233.185.204
42.233.156.239 42.233.166.247 42.232.255.175 42.233.186.30
42.233.213.161 42.233.187.62 42.233.68.94 42.233.85.98
42.233.70.167 42.233.92.18 42.233.86.32 42.234.130.25