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: Korea Republic of

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

;; QUESTION SECTION:
;121.168.64.34.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 13:58:53 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 34.64.168.121.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.64.168.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
183.6.155.145 attackspam
Unauthorized connection attempt detected from IP address 183.6.155.145 to port 80
2019-12-30 09:04:05
42.117.32.32 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-12-30 09:17:53
172.81.250.106 attackspambots
Dec 30 01:43:32 server sshd\[7464\]: Invalid user devarea from 172.81.250.106
Dec 30 01:43:32 server sshd\[7464\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.250.106 
Dec 30 01:43:35 server sshd\[7464\]: Failed password for invalid user devarea from 172.81.250.106 port 47628 ssh2
Dec 30 02:02:10 server sshd\[12077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=172.81.250.106  user=root
Dec 30 02:02:12 server sshd\[12077\]: Failed password for root from 172.81.250.106 port 35400 ssh2
...
2019-12-30 08:48:25
111.40.5.114 attackbots
Unauthorized connection attempt detected from IP address 111.40.5.114 to port 23
2019-12-30 09:11:44
115.206.0.29 attack
Unauthorized connection attempt detected from IP address 115.206.0.29 to port 7574
2019-12-30 09:10:08
42.118.169.21 attackbots
Unauthorized connection attempt detected from IP address 42.118.169.21 to port 23
2019-12-30 09:17:35
117.102.73.98 attackbotsspam
SSH authentication failure x 6 reported by Fail2Ban
...
2019-12-30 08:55:32
110.167.168.66 attackspambots
Unauthorized connection attempt detected from IP address 110.167.168.66 to port 445
2019-12-30 09:12:46
183.88.8.80 attackspambots
Unauthorized connection attempt detected from IP address 183.88.8.80 to port 9090
2019-12-30 09:25:01
175.166.228.231 attackbotsspam
Unauthorized connection attempt detected from IP address 175.166.228.231 to port 23
2019-12-30 09:27:29
111.2.95.191 attack
Unauthorized connection attempt detected from IP address 111.2.95.191 to port 23
2019-12-30 09:12:16
119.193.246.76 attackspam
Dec 30 00:01:59 debian-2gb-nbg1-2 kernel: \[1313229.593401\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=119.193.246.76 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=62123 PROTO=TCP SPT=11801 DPT=23 WINDOW=32065 RES=0x00 SYN URGP=0
2019-12-30 08:57:04
51.15.108.142 attackbots
WordpressAttack
2019-12-30 08:54:25
120.203.15.155 attack
Unauthorized connection attempt detected from IP address 120.203.15.155 to port 1433
2019-12-30 09:08:37
182.151.175.126 attackbots
Unauthorized connection attempt detected from IP address 182.151.175.126 to port 445
2019-12-30 09:26:08

Recently Reported IPs

182.114.84.216 202.166.206.242 192.241.116.32 116.13.193.11
212.192.246.207 79.50.197.140 167.172.50.59 125.162.209.60
123.10.223.155 162.223.18.81 109.237.102.61 103.156.75.42
201.156.6.34 186.47.207.198 76.87.120.136 186.126.53.139
123.245.25.128 197.246.202.234 36.142.179.50 42.232.169.32