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: South Africa

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

;; QUESTION SECTION:
;102.64.122.34.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 04:11:33 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 34.122.64.102.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 34.122.64.102.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.12.80.204 attack
Jul  3 09:05:37 MK-Soft-VM6 sshd\[27015\]: Invalid user WinD3str0y from 106.12.80.204 port 58590
Jul  3 09:05:37 MK-Soft-VM6 sshd\[27015\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.80.204
Jul  3 09:05:39 MK-Soft-VM6 sshd\[27015\]: Failed password for invalid user WinD3str0y from 106.12.80.204 port 58590 ssh2
...
2019-07-03 18:50:39
206.189.131.213 attackbotsspam
Fail2Ban Ban Triggered
2019-07-03 19:18:40
193.32.163.123 attackspambots
2019-07-03T18:12:22.488180enmeeting.mahidol.ac.th sshd\[31462\]: Invalid user admin from 193.32.163.123 port 36382
2019-07-03T18:12:22.505699enmeeting.mahidol.ac.th sshd\[31462\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.32.163.123
2019-07-03T18:12:24.238443enmeeting.mahidol.ac.th sshd\[31462\]: Failed password for invalid user admin from 193.32.163.123 port 36382 ssh2
...
2019-07-03 19:28:18
188.84.189.235 attackspambots
Jul  3 06:46:45 icinga sshd[7369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.84.189.235
Jul  3 06:46:47 icinga sshd[7369]: Failed password for invalid user server from 188.84.189.235 port 40602 ssh2
...
2019-07-03 19:05:20
134.255.159.220 attackbots
23/tcp
[2019-07-03]1pkt
2019-07-03 18:49:39
203.160.63.180 attackspam
Jul  1 20:51:05 xb3 sshd[10305]: reveeclipse mapping checking getaddrinfo for 180.sub-63-160-203.hanastar.net.id [203.160.63.180] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul  1 20:51:07 xb3 sshd[10305]: Failed password for invalid user web from 203.160.63.180 port 42050 ssh2
Jul  1 20:51:07 xb3 sshd[10305]: Received disconnect from 203.160.63.180: 11: Bye Bye [preauth]
Jul  1 20:53:37 xb3 sshd[16163]: reveeclipse mapping checking getaddrinfo for 180.sub-63-160-203.hanastar.net.id [203.160.63.180] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul  1 20:53:39 xb3 sshd[16163]: Failed password for invalid user test from 203.160.63.180 port 54071 ssh2
Jul  1 20:53:39 xb3 sshd[16163]: Received disconnect from 203.160.63.180: 11: Bye Bye [preauth]
Jul  1 20:55:23 xb3 sshd[6250]: reveeclipse mapping checking getaddrinfo for 180.sub-63-160-203.hanastar.net.id [203.160.63.180] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul  1 20:55:25 xb3 sshd[6250]: Failed password for invalid user dw from 203.160.6........
-------------------------------
2019-07-03 18:37:13
114.45.51.184 attack
37215/tcp
[2019-07-03]1pkt
2019-07-03 18:58:34
213.208.169.245 attackbots
Wordpress XMLRPC attack
2019-07-03 19:11:29
138.197.156.202 attackspam
Jul  3 06:44:47 server2 sshd\[10038\]: User root from 138.197.156.202 not allowed because not listed in AllowUsers
Jul  3 06:44:48 server2 sshd\[10040\]: Invalid user admin from 138.197.156.202
Jul  3 06:44:49 server2 sshd\[10042\]: Invalid user admin from 138.197.156.202
Jul  3 06:44:49 server2 sshd\[10044\]: Invalid user user from 138.197.156.202
Jul  3 06:44:50 server2 sshd\[10046\]: Invalid user ubnt from 138.197.156.202
Jul  3 06:44:51 server2 sshd\[10048\]: Invalid user admin from 138.197.156.202
2019-07-03 19:13:29
187.16.96.35 attack
Jul  3 06:48:53 core01 sshd\[13824\]: Invalid user zai from 187.16.96.35 port 42142
Jul  3 06:48:53 core01 sshd\[13824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.16.96.35
...
2019-07-03 18:40:29
78.245.118.141 attack
Jul  3 09:31:11 tanzim-HP-Z238-Microtower-Workstation sshd\[15889\]: Invalid user antonio from 78.245.118.141
Jul  3 09:31:11 tanzim-HP-Z238-Microtower-Workstation sshd\[15889\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.245.118.141
Jul  3 09:31:13 tanzim-HP-Z238-Microtower-Workstation sshd\[15889\]: Failed password for invalid user antonio from 78.245.118.141 port 34532 ssh2
...
2019-07-03 19:31:00
113.238.66.179 attack
23/tcp
[2019-07-03]1pkt
2019-07-03 19:00:57
5.143.134.151 attackspambots
23/tcp
[2019-07-03]1pkt
2019-07-03 19:25:56
106.75.60.142 attackbots
SSH Brute-Force attacks
2019-07-03 19:30:42
201.139.111.202 attack
2019-07-03T10:16:34.996558abusebot-2.cloudsearch.cf sshd\[3990\]: Invalid user charlott from 201.139.111.202 port 39924
2019-07-03 18:53:41

Recently Reported IPs

102.64.122.186 102.64.122.59 102.64.122.94 102.64.123.178
102.64.123.209 102.64.123.218 102.64.123.45 102.64.123.58
102.64.123.78 102.64.123.86 102.65.9.246 189.252.30.23
102.66.228.123 126.190.147.130 135.14.90.54 102.67.68.230
102.68.134.94 103.1.195.4 103.1.95.47 225.88.67.238