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

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:
IP Type Details Datetime
94.140.114.17 attackbots
Firewall Dropped Connection
2020-05-12 22:21:08
94.140.114.17 attackbotsspam
[Mon May 11 11:18:28.446478 2020] [:error] [pid 23098:tid 140213493257984] [client 94.140.114.17:443] [client 94.140.114.17] 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 "/"] [unique_id "XrjSFJOY0tIJkGtidjyfxwAAAhw"]
...
2020-05-11 14:11:37
94.140.114.17 attack
User-Agent : Pandalytics/1.0 (https://domainsbot.com/pandalytics/)
2020-05-04 00:15:10
94.140.114.17 attackbotsspam
[02/May/2020:11:35:31 -0400] "GET / HTTP/1.0" "Pandalytics/1.0 (https://domainsbot.com/pandalytics/)"
2020-05-03 18:07:19
94.140.114.17 attackspam
Unauthorized connection attempt detected from IP address 94.140.114.17 to port 443
2020-04-27 19:07:54
94.140.114.17 attackspam
Unauthorized connection attempt detected from IP address 94.140.114.17 to port 443
2020-04-20 02:03:33
94.140.114.53 attackbotsspam
SIP/5060 Probe, BF, Hack -
2020-03-29 00:56:04
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 94.140.114.239
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40365
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;94.140.114.239.			IN	A

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

;; Query time: 75 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Apr 24 20:54:46 CST 2023
;; MSG SIZE  rcvd: 107
Host info
Host 239.114.140.94.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 239.114.140.94.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
141.98.80.89 attackspam
3389BruteforceFW23
2019-11-02 04:08:57
182.254.234.53 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-02 04:12:00
117.1.64.136 attackbots
Nov  1 21:15:55 mail sshd\[30738\]: Invalid user admin from 117.1.64.136
Nov  1 21:15:55 mail sshd\[30738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.1.64.136
Nov  1 21:15:58 mail sshd\[30738\]: Failed password for invalid user admin from 117.1.64.136 port 35223 ssh2
...
2019-11-02 04:23:28
178.128.52.97 attackbots
Nov  1 20:15:48 *** sshd[10277]: User root from 178.128.52.97 not allowed because not listed in AllowUsers
2019-11-02 04:35:20
78.153.102.202 attackspam
Unauthorized connection attempt from IP address 78.153.102.202 on Port 445(SMB)
2019-11-02 04:22:37
77.42.111.51 attack
Automatic report - Port Scan Attack
2019-11-02 04:00:11
45.185.216.158 attack
23/tcp
[2019-11-01]1pkt
2019-11-02 04:25:44
106.12.185.58 attackbotsspam
Invalid user www from 106.12.185.58 port 52954
2019-11-02 04:12:54
222.186.175.150 attack
Nov  1 20:18:37 MK-Soft-VM5 sshd[17090]: Failed password for root from 222.186.175.150 port 34362 ssh2
Nov  1 20:18:42 MK-Soft-VM5 sshd[17090]: Failed password for root from 222.186.175.150 port 34362 ssh2
...
2019-11-02 03:57:11
106.51.80.198 attackbotsspam
Nov  1 11:03:16 TORMINT sshd\[19043\]: Invalid user P@r0la12 from 106.51.80.198
Nov  1 11:03:16 TORMINT sshd\[19043\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.51.80.198
Nov  1 11:03:19 TORMINT sshd\[19043\]: Failed password for invalid user P@r0la12 from 106.51.80.198 port 57356 ssh2
...
2019-11-02 04:17:54
167.71.61.57 attackbots
windhundgang.de 167.71.61.57 \[01/Nov/2019:12:43:58 +0100\] "POST /wp-login.php HTTP/1.1" 200 8411 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
windhundgang.de 167.71.61.57 \[01/Nov/2019:12:43:59 +0100\] "POST /xmlrpc.php HTTP/1.1" 200 4216 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-02 04:04:38
122.228.19.80 attackspam
Web application attack detected by fail2ban
2019-11-02 04:13:57
117.63.81.182 attack
SASL broute force
2019-11-02 04:24:59
61.141.64.64 attackbotsspam
1433/tcp
[2019-11-01]1pkt
2019-11-02 04:31:12
119.146.150.134 attackspam
Nov  1 15:45:26 DAAP sshd[30257]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.150.134  user=root
Nov  1 15:45:28 DAAP sshd[30257]: Failed password for root from 119.146.150.134 port 44843 ssh2
Nov  1 15:52:13 DAAP sshd[30322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.150.134  user=root
Nov  1 15:52:15 DAAP sshd[30322]: Failed password for root from 119.146.150.134 port 35071 ssh2
...
2019-11-02 04:05:09

Recently Reported IPs

199.241.200.172 3.158.41.10 37.2.40.198 88.241.216.63
129.24.0.199 75.252.69.18 30.17.64.157 181.187.235.176
228.220.78.39 21.225.53.82 139.99.6.159 164.52.66.246
234.152.15.112 209.86.39.101 219.155.214.60 88.253.146.142
122.50.208.35 33.57.251.36 229.67.4.109 66.83.58.120