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: Japan

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 <<>> 133.94.122.144
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1149
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;133.94.122.144.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 02:50:44 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 144.122.94.133.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 144.122.94.133.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
141.98.80.138 attack
SMTP nagging
2020-02-13 16:11:09
106.13.130.66 attackbots
$f2bV_matches
2020-02-13 16:04:35
113.184.50.178 attack
1581569466 - 02/13/2020 05:51:06 Host: 113.184.50.178/113.184.50.178 Port: 445 TCP Blocked
2020-02-13 16:32:53
188.166.60.174 attackspam
Automatic report - XMLRPC Attack
2020-02-13 16:14:04
122.164.223.80 attackspam
$f2bV_matches
2020-02-13 15:55:58
54.36.189.113 attack
Feb 13 08:50:05 SilenceServices sshd[14787]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.113
Feb 13 08:50:05 SilenceServices sshd[14790]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.113
2020-02-13 16:21:34
118.24.208.253 attackspam
Feb 13 08:58:47 lukav-desktop sshd\[17466\]: Invalid user 123456 from 118.24.208.253
Feb 13 08:58:47 lukav-desktop sshd\[17466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.208.253
Feb 13 08:58:49 lukav-desktop sshd\[17466\]: Failed password for invalid user 123456 from 118.24.208.253 port 37702 ssh2
Feb 13 09:01:54 lukav-desktop sshd\[18949\]: Invalid user jupyter2 from 118.24.208.253
Feb 13 09:01:54 lukav-desktop sshd\[18949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.208.253
2020-02-13 15:59:50
165.22.191.129 attack
165.22.191.129 - - \[13/Feb/2020:08:38:42 +0100\] "POST /wp-login.php HTTP/1.0" 200 6640 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.191.129 - - \[13/Feb/2020:08:38:45 +0100\] "POST /wp-login.php HTTP/1.0" 200 6453 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
165.22.191.129 - - \[13/Feb/2020:08:38:47 +0100\] "POST /wp-login.php HTTP/1.0" 200 6453 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-02-13 15:54:02
180.191.135.117 attackbotsspam
Wordpress login attempts
2020-02-13 16:07:17
96.41.163.7 attackbotsspam
Automatic report - Port Scan Attack
2020-02-13 16:26:14
200.160.121.97 attack
Feb 13 09:28:28 vmanager6029 sshd\[25851\]: Invalid user sayama from 200.160.121.97 port 31583
Feb 13 09:28:28 vmanager6029 sshd\[25851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.160.121.97
Feb 13 09:28:30 vmanager6029 sshd\[25851\]: Failed password for invalid user sayama from 200.160.121.97 port 31583 ssh2
2020-02-13 16:30:10
140.143.196.66 attackbotsspam
Feb 12 11:34:23 server sshd\[26903\]: Invalid user ruehl from 140.143.196.66
Feb 12 11:34:23 server sshd\[26903\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.196.66 
Feb 12 11:34:26 server sshd\[26903\]: Failed password for invalid user ruehl from 140.143.196.66 port 39120 ssh2
Feb 13 08:38:28 server sshd\[31473\]: Invalid user rosana from 140.143.196.66
Feb 13 08:38:28 server sshd\[31473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.196.66 
...
2020-02-13 15:57:58
157.55.39.140 attack
Automatic report - Banned IP Access
2020-02-13 16:25:03
134.209.159.10 attackspam
Invalid user call from 134.209.159.10 port 53972
2020-02-13 16:00:42
95.216.100.229 attackbotsspam
[Thu Feb 13 11:51:00.340319 2020] [:error] [pid 29304:tid 140024279488256] [client 95.216.100.229:48400] [client 95.216.100.229] ModSecurity: Access denied with code 403 (phase 1). Match of "within %{tx.allowed_http_versions}" against "REQUEST_PROTOCOL" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "972"] [id "920430"] [msg "HTTP protocol version is not allowed by policy"] [data "HTTP/1.0"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/POLICY/PROTOCOL_NOT_ALLOWED"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.10"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/profil/meteorologi/list-of-all-tags/buku"] [unique_id "XkTVtDQXVcBnYDbj8RmbXgAAARQ"]
...
2020-02-13 16:37:06

Recently Reported IPs

246.85.136.237 223.5.123.27 247.79.214.42 80.203.197.82
202.105.112.31 200.21.144.179 51.170.174.68 127.85.180.141
131.209.123.221 231.164.89.72 240.14.91.193 52.153.119.192
238.101.143.241 107.119.77.180 19.229.137.15 239.173.42.196
103.253.22.114 43.233.60.31 152.160.132.237 180.151.246.43