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

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

;; QUESTION SECTION:
;117.74.122.114.			IN	A

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

;; Query time: 98 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 22:42:19 CST 2022
;; MSG SIZE  rcvd: 107
Host info
114.122.74.117.in-addr.arpa domain name pointer ip-122-114.grahamedia.net.id.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
114.122.74.117.in-addr.arpa	name = ip-122-114.grahamedia.net.id.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.148.87.125 attack
HTTP SQL Injection Attempt, PTR: edm12.vteexcx.com.
2019-11-09 08:56:21
164.77.119.18 attackspambots
SSH Brute-Force reported by Fail2Ban
2019-11-09 08:58:55
45.228.213.65 attackspambots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/45.228.213.65/ 
 
 BR - 1H : (149)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN267098 
 
 IP : 45.228.213.65 
 
 CIDR : 45.228.212.0/23 
 
 PREFIX COUNT : 3 
 
 UNIQUE IP COUNT : 1024 
 
 
 ATTACKS DETECTED ASN267098 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-09 05:55:31 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-09 13:23:33
185.162.235.98 attack
(smtpauth) Failed SMTP AUTH login from 185.162.235.98 (NL/Netherlands/-): 5 in the last 3600 secs
2019-11-09 13:30:23
222.186.180.223 attackbotsspam
Nov  9 07:10:06 pkdns2 sshd\[63041\]: Failed password for root from 222.186.180.223 port 24106 ssh2Nov  9 07:10:11 pkdns2 sshd\[63041\]: Failed password for root from 222.186.180.223 port 24106 ssh2Nov  9 07:10:36 pkdns2 sshd\[63113\]: Failed password for root from 222.186.180.223 port 31080 ssh2Nov  9 07:10:54 pkdns2 sshd\[63113\]: Failed password for root from 222.186.180.223 port 31080 ssh2Nov  9 07:10:59 pkdns2 sshd\[63113\]: Failed password for root from 222.186.180.223 port 31080 ssh2Nov  9 07:11:10 pkdns2 sshd\[63135\]: Failed password for root from 222.186.180.223 port 5062 ssh2
...
2019-11-09 13:13:55
35.226.91.251 attack
Bot ignores robot.txt restrictions
2019-11-09 13:06:51
189.115.92.79 attackbots
Nov  9 01:15:53 ns37 sshd[16968]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.115.92.79
2019-11-09 09:00:09
222.186.175.169 attackspam
$f2bV_matches
2019-11-09 13:19:42
46.38.144.17 attackbotsspam
2019-11-09T05:55:52.230135mail01 postfix/smtpd[10121]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-09T05:55:54.231440mail01 postfix/smtpd[10119]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-09T05:56:04.077561mail01 postfix/smtpd[9771]: warning: unknown[46.38.144.17]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-09 13:01:40
120.71.146.45 attackspam
Nov  9 05:49:47 MK-Soft-VM3 sshd[30394]: Failed password for root from 120.71.146.45 port 46236 ssh2
Nov  9 05:55:35 MK-Soft-VM3 sshd[30637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.71.146.45 
...
2019-11-09 13:21:50
41.84.131.10 attackspam
Nov  9 06:09:40 legacy sshd[3111]: Failed password for root from 41.84.131.10 port 17008 ssh2
Nov  9 06:14:31 legacy sshd[3182]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.84.131.10
Nov  9 06:14:33 legacy sshd[3182]: Failed password for invalid user 00 from 41.84.131.10 port 36338 ssh2
...
2019-11-09 13:24:48
222.186.190.92 attackspam
2019-11-09T04:55:48.210575abusebot-5.cloudsearch.cf sshd\[8473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92  user=root
2019-11-09 13:11:02
222.186.175.147 attackspambots
Nov  9 04:57:31 hcbbdb sshd\[3704\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.147  user=root
Nov  9 04:57:33 hcbbdb sshd\[3704\]: Failed password for root from 222.186.175.147 port 60306 ssh2
Nov  9 04:57:37 hcbbdb sshd\[3704\]: Failed password for root from 222.186.175.147 port 60306 ssh2
Nov  9 04:57:41 hcbbdb sshd\[3704\]: Failed password for root from 222.186.175.147 port 60306 ssh2
Nov  9 04:57:46 hcbbdb sshd\[3704\]: Failed password for root from 222.186.175.147 port 60306 ssh2
2019-11-09 13:03:27
74.82.47.59 attack
74.82.47.59 was recorded 5 times by 4 hosts attempting to connect to the following ports: 53413,10001. Incident counter (4h, 24h, all-time): 5, 7, 24
2019-11-09 13:14:52
194.61.26.34 attackspam
Nov  8 23:41:05 host sshd\[30789\]: Invalid user  from 194.61.26.34Nov  8 23:49:33 host sshd\[3232\]: Invalid user  from 194.61.26.34Nov  8 23:57:29 host sshd\[7662\]: Invalid user  from 194.61.26.34
...
2019-11-09 13:00:47

Recently Reported IPs

114.233.122.248 117.74.121.69 117.74.122.17 117.74.121.79
117.74.121.70 117.74.122.122 117.74.122.42 117.74.122.8
117.74.123.122 117.74.122.38 114.233.122.44 117.74.123.162
117.74.122.46 117.74.124.100 117.74.123.233 117.74.124.99
117.74.124.101 117.74.124.129 117.74.125.1 114.233.123.109