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: Nam-gu

Region: Ulsan

Country: South Korea

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

;; QUESTION SECTION:
;121.146.58.34.			IN	A

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

;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jul 14 06:58:53 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 34.58.146.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.58.146.121.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.224.219.111 attackspam
Unauthorized connection attempt detected from IP address 80.224.219.111 to port 8000 [J]
2020-01-07 13:09:43
222.186.175.217 attackbots
Jan  7 04:58:10 hcbbdb sshd\[32415\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.217  user=root
Jan  7 04:58:11 hcbbdb sshd\[32415\]: Failed password for root from 222.186.175.217 port 15750 ssh2
Jan  7 04:58:28 hcbbdb sshd\[32445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.217  user=root
Jan  7 04:58:30 hcbbdb sshd\[32445\]: Failed password for root from 222.186.175.217 port 50534 ssh2
Jan  7 04:58:47 hcbbdb sshd\[32445\]: Failed password for root from 222.186.175.217 port 50534 ssh2
2020-01-07 13:00:20
138.68.165.102 attackspambots
Unauthorized connection attempt detected from IP address 138.68.165.102 to port 2220 [J]
2020-01-07 13:05:09
132.255.149.187 attackspam
Unauthorized connection attempt detected from IP address 132.255.149.187 to port 80 [J]
2020-01-07 13:05:48
94.178.211.232 attackspambots
Unauthorized connection attempt detected from IP address 94.178.211.232 to port 5555 [J]
2020-01-07 09:17:16
177.9.111.231 attackspam
Unauthorized connection attempt detected from IP address 177.9.111.231 to port 80 [J]
2020-01-07 13:03:45
82.103.90.214 attackbotsspam
Unauthorized connection attempt detected from IP address 82.103.90.214 to port 4567 [J]
2020-01-07 13:09:23
75.69.43.192 attack
Unauthorized connection attempt detected from IP address 75.69.43.192 to port 23 [J]
2020-01-07 09:18:42
51.75.19.175 attackbots
Unauthorized connection attempt detected from IP address 51.75.19.175 to port 2220 [J]
2020-01-07 13:10:30
178.184.45.26 attack
Unauthorized connection attempt detected from IP address 178.184.45.26 to port 23 [J]
2020-01-07 09:29:35
189.210.53.42 attackspam
Unauthorized connection attempt detected from IP address 189.210.53.42 to port 23 [J]
2020-01-07 13:17:28
221.217.48.2 attackspambots
Unauthorized connection attempt detected from IP address 221.217.48.2 to port 2220 [J]
2020-01-07 13:00:37
213.138.196.194 attack
Unauthorized connection attempt detected from IP address 213.138.196.194 to port 80 [J]
2020-01-07 09:24:39
138.197.25.187 attackspam
Unauthorized connection attempt detected from IP address 138.197.25.187 to port 2220 [J]
2020-01-07 13:23:00
124.152.78.90 attackbotsspam
Unauthorized connection attempt detected from IP address 124.152.78.90 to port 5555 [J]
2020-01-07 13:07:08

Recently Reported IPs

23.230.21.194 189.101.172.187 121.227.208.112 94.232.17.84
134.209.29.114 40.115.79.250 13.213.40.157 179.172.15.60
95.181.151.204 50.217.22.105 148.66.99.54 181.215.190.243
71.213.94.7 190.39.51.172 189.187.46.56 186.22.19.90
111.118.114.34 223.10.10.20 136.33.247.88 190.59.205.196