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

Region: West Java

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:
IP Type Details Datetime
45.64.128.160 attackbots
[N10.H2.VM2] Port Scanner Detected Blocked by UFW
2020-10-01 06:56:42
45.64.128.160 attack
Fail2Ban Ban Triggered
2020-09-30 23:20:41
45.64.126.103 attack
Sep 26 20:37:17 django-0 sshd[10035]: Invalid user gen from 45.64.126.103
...
2020-09-27 04:49:56
45.64.126.103 attack
Sep 26 08:29:48 ws12vmsma01 sshd[24920]: Invalid user cl from 45.64.126.103
Sep 26 08:29:51 ws12vmsma01 sshd[24920]: Failed password for invalid user cl from 45.64.126.103 port 36356 ssh2
Sep 26 08:32:31 ws12vmsma01 sshd[25347]: Invalid user mama from 45.64.126.103
...
2020-09-26 21:01:16
45.64.126.103 attackbotsspam
2020-09-26T04:35:45.352683abusebot-8.cloudsearch.cf sshd[29102]: Invalid user jane from 45.64.126.103 port 54200
2020-09-26T04:35:45.359599abusebot-8.cloudsearch.cf sshd[29102]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103
2020-09-26T04:35:45.352683abusebot-8.cloudsearch.cf sshd[29102]: Invalid user jane from 45.64.126.103 port 54200
2020-09-26T04:35:47.232058abusebot-8.cloudsearch.cf sshd[29102]: Failed password for invalid user jane from 45.64.126.103 port 54200 ssh2
2020-09-26T04:40:29.612516abusebot-8.cloudsearch.cf sshd[29228]: Invalid user mysql from 45.64.126.103 port 33360
2020-09-26T04:40:29.620013abusebot-8.cloudsearch.cf sshd[29228]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103
2020-09-26T04:40:29.612516abusebot-8.cloudsearch.cf sshd[29228]: Invalid user mysql from 45.64.126.103 port 33360
2020-09-26T04:40:31.478332abusebot-8.cloudsearch.cf sshd[29228]: Failed pa
...
2020-09-26 12:44:02
45.64.128.160 attack
 TCP (SYN) 45.64.128.160:60000 -> port 6003, len 44
2020-09-25 03:35:13
45.64.128.160 attackbotsspam
Fail2Ban Ban Triggered
2020-09-24 19:20:54
45.64.126.103 attackbots
TCP ports : 421 / 7323 / 14757 / 17327 / 21039
2020-09-06 22:00:06
45.64.126.103 attackbotsspam
ET CINS Active Threat Intelligence Poor Reputation IP group 25 - port: 21039 proto: tcp cat: Misc Attackbytes: 60
2020-09-06 13:35:47
45.64.126.103 attackspambots
Sep  5 18:49:03 h2646465 sshd[28993]: Invalid user gangadhar from 45.64.126.103
Sep  5 18:49:03 h2646465 sshd[28993]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103
Sep  5 18:49:03 h2646465 sshd[28993]: Invalid user gangadhar from 45.64.126.103
Sep  5 18:49:05 h2646465 sshd[28993]: Failed password for invalid user gangadhar from 45.64.126.103 port 51228 ssh2
Sep  5 18:50:44 h2646465 sshd[29502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103  user=root
Sep  5 18:50:46 h2646465 sshd[29502]: Failed password for root from 45.64.126.103 port 35662 ssh2
Sep  5 18:51:51 h2646465 sshd[29533]: Invalid user monte from 45.64.126.103
Sep  5 18:51:51 h2646465 sshd[29533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103
Sep  5 18:51:51 h2646465 sshd[29533]: Invalid user monte from 45.64.126.103
Sep  5 18:51:53 h2646465 sshd[29533]: Failed password for invalid u
2020-09-06 05:50:46
45.64.179.202 attackbotsspam
Attempted connection to port 8080.
2020-08-24 21:09:59
45.64.126.103 attackbotsspam
Automatic Fail2ban report - Trying login SSH
2020-08-20 20:21:58
45.64.126.103 attack
Aug 19 15:44:56 journals sshd\[38921\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103  user=root
Aug 19 15:44:57 journals sshd\[38921\]: Failed password for root from 45.64.126.103 port 55884 ssh2
Aug 19 15:48:17 journals sshd\[39293\]: Invalid user sai from 45.64.126.103
Aug 19 15:48:17 journals sshd\[39293\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.64.126.103
Aug 19 15:48:19 journals sshd\[39293\]: Failed password for invalid user sai from 45.64.126.103 port 41510 ssh2
...
2020-08-19 21:05:07
45.64.126.103 attack
2020-08-18T23:56:01.992956mail.thespaminator.com sshd[12900]: Invalid user kevin from 45.64.126.103 port 58240
2020-08-18T23:56:04.564299mail.thespaminator.com sshd[12900]: Failed password for invalid user kevin from 45.64.126.103 port 58240 ssh2
...
2020-08-19 12:34:39
45.64.126.103 attack
SSH Brute Force
2020-08-15 17:55:53
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.64.1.199
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46412
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;45.64.1.199.			IN	A

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

;; Query time: 114 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 02 19:13:26 CST 2020
;; MSG SIZE  rcvd: 115
Host info
199.1.64.45.in-addr.arpa domain name pointer 64.1.199.static-45.masterweb.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
199.1.64.45.in-addr.arpa	name = 64.1.199.static-45.masterweb.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.140 attack
Brute-force attempt banned
2020-01-29 01:26:36
198.100.146.67 attack
Jan 28 17:07:03 SilenceServices sshd[10505]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.100.146.67
Jan 28 17:07:05 SilenceServices sshd[10505]: Failed password for invalid user charusheela from 198.100.146.67 port 60516 ssh2
Jan 28 17:09:06 SilenceServices sshd[12918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.100.146.67
2020-01-29 01:18:47
51.75.29.61 attackbotsspam
Unauthorized connection attempt detected from IP address 51.75.29.61 to port 2220 [J]
2020-01-29 00:46:55
63.230.156.139 attack
"Fail2Ban detected SSH brute force attempt"
2020-01-29 00:45:23
94.38.73.131 attackspam
Unauthorized connection attempt detected from IP address 94.38.73.131 to port 85 [J]
2020-01-29 01:36:11
194.88.62.80 attack
Unauthorized connection attempt detected from IP address 194.88.62.80 to port 2220 [J]
2020-01-29 01:28:39
167.99.46.145 attackbotsspam
Unauthorized connection attempt detected from IP address 167.99.46.145 to port 2220 [J]
2020-01-29 00:59:32
1.214.220.227 attack
Unauthorized connection attempt detected from IP address 1.214.220.227 to port 2220 [J]
2020-01-29 01:14:54
95.105.234.228 attackspambots
Unauthorized connection attempt detected from IP address 95.105.234.228 to port 2220 [J]
2020-01-29 00:43:09
179.156.19.152 attack
Unauthorized connection attempt detected from IP address 179.156.19.152 to port 23 [J]
2020-01-29 01:20:20
101.50.57.47 attack
Unauthorized connection attempt detected from IP address 101.50.57.47 to port 1433 [J]
2020-01-29 01:35:42
61.178.81.109 attackbotsspam
Unauthorized connection attempt detected from IP address 61.178.81.109 to port 1433 [J]
2020-01-29 00:45:54
45.227.255.75 attack
Unauthorized connection attempt detected from IP address 45.227.255.75 to port 3388 [J]
2020-01-29 00:47:58
220.255.134.9 attack
Unauthorized connection attempt detected from IP address 220.255.134.9 to port 5555 [J]
2020-01-29 01:27:51
45.67.14.150 attack
Unauthorized connection attempt detected from IP address 45.67.14.150 to port 22 [J]
2020-01-29 00:48:47

Recently Reported IPs

132.14.118.99 218.23.82.253 214.220.251.95 212.223.89.133
75.160.118.140 43.44.148.127 42.42.2.61 183.5.80.91
179.134.7.157 136.122.91.143 75.149.234.97 106.13.41.93
133.71.57.67 52.35.87.255 129.200.244.189 165.171.226.209
155.62.202.117 220.190.13.30 154.195.167.187 90.223.157.51