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

;; QUESTION SECTION:
;59.136.139.219.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 19:51:58 CST 2025
;; MSG SIZE  rcvd: 107
Host info
219.139.136.59.in-addr.arpa domain name pointer KD059136139219.ppp-bb.dion.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
219.139.136.59.in-addr.arpa	name = KD059136139219.ppp-bb.dion.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.6.113 attackbots
2019-10-01T06:58:44.135004shield sshd\[2730\]: Invalid user i2pd from 106.13.6.113 port 50458
2019-10-01T06:58:44.139653shield sshd\[2730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.6.113
2019-10-01T06:58:46.737073shield sshd\[2730\]: Failed password for invalid user i2pd from 106.13.6.113 port 50458 ssh2
2019-10-01T07:02:57.020032shield sshd\[3171\]: Invalid user faic from 106.13.6.113 port 51818
2019-10-01T07:02:57.024610shield sshd\[3171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.6.113
2019-10-01 16:59:13
49.207.180.197 attackspam
2019-10-01 11:00:26,681 fail2ban.actions: WARNING [ssh] Ban 49.207.180.197
2019-10-01 17:01:45
115.159.99.54 attack
SS5,WP GET /wp-login.php
2019-10-01 17:00:39
212.52.141.46 attackspambots
Brute force SMTP login attempts.
2019-10-01 17:30:29
42.200.66.164 attackbots
Oct  1 08:19:19 v22019058497090703 sshd[20495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.200.66.164
Oct  1 08:19:21 v22019058497090703 sshd[20495]: Failed password for invalid user klind from 42.200.66.164 port 53760 ssh2
Oct  1 08:23:43 v22019058497090703 sshd[20785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.200.66.164
...
2019-10-01 16:55:50
49.234.43.173 attackbots
Brute SSH
2019-10-01 17:30:07
92.222.34.211 attackspam
Oct  1 10:48:01 lnxweb61 sshd[18190]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.34.211
2019-10-01 16:57:58
66.70.189.209 attackspam
Invalid user support from 66.70.189.209 port 42632
2019-10-01 17:17:20
152.136.141.227 attackspambots
2019-10-01T10:48:23.637362centos sshd\[23044\]: Invalid user bi from 152.136.141.227 port 56124
2019-10-01T10:48:23.651361centos sshd\[23044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.141.227
2019-10-01T10:48:25.769563centos sshd\[23044\]: Failed password for invalid user bi from 152.136.141.227 port 56124 ssh2
2019-10-01 16:57:11
58.59.158.93 attack
Oct  1 05:49:31 host proftpd\[5669\]: 0.0.0.0 \(58.59.158.93\[58.59.158.93\]\) - USER anonymous: no such user found from 58.59.158.93 \[58.59.158.93\] to 62.210.146.38:21
...
2019-10-01 17:12:34
62.94.244.235 attack
$f2bV_matches
2019-10-01 17:06:22
34.237.218.120 attackbots
by Amazon Technologies Inc.
2019-10-01 17:19:02
94.176.141.57 attack
(Oct  1)  LEN=44 TTL=241 ID=61889 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=241 ID=20054 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=241 ID=51643 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=241 ID=63988 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=241 ID=35245 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=241 ID=22695 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=238 ID=38582 DF TCP DPT=23 WINDOW=14600 SYN 
 (Oct  1)  LEN=44 TTL=238 ID=12875 DF TCP DPT=23 WINDOW=14600 SYN 
 (Sep 30)  LEN=44 TTL=238 ID=42413 DF TCP DPT=23 WINDOW=14600 SYN 
 (Sep 30)  LEN=44 TTL=238 ID=12049 DF TCP DPT=23 WINDOW=14600 SYN
2019-10-01 16:57:42
193.112.6.241 attack
Sep 30 22:02:11 eddieflores sshd\[8327\]: Invalid user sasha from 193.112.6.241
Sep 30 22:02:11 eddieflores sshd\[8327\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.6.241
Sep 30 22:02:13 eddieflores sshd\[8327\]: Failed password for invalid user sasha from 193.112.6.241 port 42350 ssh2
Sep 30 22:07:10 eddieflores sshd\[8730\]: Invalid user ethos from 193.112.6.241
Sep 30 22:07:10 eddieflores sshd\[8730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.6.241
2019-10-01 17:33:31
50.203.164.134 attack
Connection by 50.203.164.134 on port: 139 got caught by honeypot at 9/30/2019 8:49:12 PM
2019-10-01 17:33:00

Recently Reported IPs

209.204.212.122 117.64.134.83 243.152.212.193 7.173.150.199
7.37.84.201 66.173.162.61 137.14.250.17 224.98.144.148
70.15.95.226 195.129.179.224 217.235.128.179 189.107.202.138
106.218.89.84 90.75.86.206 230.26.7.17 20.210.101.234
78.142.202.153 221.255.121.107 13.102.56.244 170.2.134.215