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

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

;; QUESTION SECTION:
;58.94.122.213.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 22:03:57 CST 2025
;; MSG SIZE  rcvd: 106
Host info
213.122.94.58.in-addr.arpa domain name pointer i58-94-122-213.s41.a028.ap.plala.or.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
213.122.94.58.in-addr.arpa	name = i58-94-122-213.s41.a028.ap.plala.or.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
187.120.145.220 attackspam
Brute force attempt
2019-10-04 05:00:16
129.204.67.235 attack
2019-10-03T22:07:39.746783  sshd[3303]: Invalid user db from 129.204.67.235 port 43000
2019-10-03T22:07:39.757930  sshd[3303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.67.235
2019-10-03T22:07:39.746783  sshd[3303]: Invalid user db from 129.204.67.235 port 43000
2019-10-03T22:07:41.390861  sshd[3303]: Failed password for invalid user db from 129.204.67.235 port 43000 ssh2
2019-10-03T22:13:07.307352  sshd[3401]: Invalid user ubnt from 129.204.67.235 port 55050
...
2019-10-04 04:51:41
113.190.235.143 attackbotsspam
Attempt to attack host OS, exploiting network vulnerabilities, on 03-10-2019 13:20:23.
2019-10-04 04:47:06
104.248.115.231 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2019-10-04 04:30:16
197.44.136.193 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 03-10-2019 13:20:29.
2019-10-04 04:39:57
78.57.158.151 attackbots
Automatic report - Port Scan Attack
2019-10-04 04:52:55
187.49.83.194 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 03-10-2019 13:20:28.
2019-10-04 04:40:29
52.65.15.196 attack
Hit on CMS login honeypot
2019-10-04 05:05:40
187.222.70.10 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 03-10-2019 13:20:28.
2019-10-04 04:40:59
51.254.95.139 attackspam
2019-10-03 16:10:34,975 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 16:44:20,818 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 17:15:55,565 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 17:46:44,063 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 18:21:03,279 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
...
2019-10-04 04:28:08
139.199.6.107 attack
Oct  3 10:49:02 auw2 sshd\[29588\]: Invalid user ilie from 139.199.6.107
Oct  3 10:49:02 auw2 sshd\[29588\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.6.107
Oct  3 10:49:04 auw2 sshd\[29588\]: Failed password for invalid user ilie from 139.199.6.107 port 50101 ssh2
Oct  3 10:53:59 auw2 sshd\[30021\]: Invalid user gozone from 139.199.6.107
Oct  3 10:53:59 auw2 sshd\[30021\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.6.107
2019-10-04 05:01:21
152.136.225.47 attackspambots
Oct  3 17:40:10 tux-35-217 sshd\[27767\]: Invalid user ftpuser from 152.136.225.47 port 50794
Oct  3 17:40:10 tux-35-217 sshd\[27767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.225.47
Oct  3 17:40:12 tux-35-217 sshd\[27767\]: Failed password for invalid user ftpuser from 152.136.225.47 port 50794 ssh2
Oct  3 17:46:50 tux-35-217 sshd\[27810\]: Invalid user ubnt from 152.136.225.47 port 34490
Oct  3 17:46:50 tux-35-217 sshd\[27810\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.225.47
...
2019-10-04 04:29:29
124.16.139.243 attack
Automated report - ssh fail2ban:
Oct 3 22:49:32 authentication failure 
Oct 3 22:49:34 wrong password, user=danuser, port=39318, ssh2
Oct 3 22:53:51 authentication failure
2019-10-04 05:06:29
185.234.219.83 attack
Oct  3 23:09:45 elektron postfix/smtpd\[32109\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  3 23:23:29 elektron postfix/smtpd\[2062\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  3 23:37:06 elektron postfix/smtpd\[964\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-04 04:41:44
221.139.178.16 attackbotsspam
Automated reporting of SSH Vulnerability scanning
2019-10-04 04:48:01

Recently Reported IPs

183.72.7.60 55.13.56.42 56.72.68.144 150.12.233.226
207.153.32.232 74.116.74.220 214.20.143.6 28.178.235.244
164.116.222.99 204.90.95.179 241.156.242.39 38.111.100.7
168.235.85.241 148.13.253.180 119.92.153.220 181.98.58.177
181.210.42.168 236.144.217.136 62.61.60.252 133.204.196.140