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

Region: Tokyo

Country: Japan

Internet Service Provider: SoftBank

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;61.116.252.136.			IN	A

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 22 03:16:37 CST 2019
;; MSG SIZE  rcvd: 118
Host info
136.252.116.61.in-addr.arpa domain name pointer OFSfx-16p5-136.ppp11.odn.ad.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
136.252.116.61.in-addr.arpa	name = OFSfx-16p5-136.ppp11.odn.ad.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
27.254.136.29 attack
Repeated brute force against a port
2019-10-23 14:48:27
144.217.70.190 attackbots
WordPress wp-login brute force :: 144.217.70.190 0.144 BYPASS [23/Oct/2019:17:01:19  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-23 14:47:10
149.28.134.34 attack
villaromeo.de 149.28.134.34 \[23/Oct/2019:05:54:42 +0200\] "POST /wp-login.php HTTP/1.1" 200 2060 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
villaromeo.de 149.28.134.34 \[23/Oct/2019:05:54:43 +0200\] "POST /wp-login.php HTTP/1.1" 200 2023 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-10-23 14:51:16
117.67.156.37 attack
FTP: login Brute Force attempt, PTR: PTR record not found
2019-10-23 14:31:00
190.202.54.12 attackbotsspam
F2B jail: sshd. Time: 2019-10-23 08:42:41, Reported by: VKReport
2019-10-23 14:49:21
45.125.65.87 attackspambots
\[2019-10-23 02:33:43\] SECURITY\[2046\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-10-23T02:33:43.052-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="9684901148333554003",SessionID="0x7f61303c1848",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.65.87/56443",ACLName="no_extension_match"
\[2019-10-23 02:34:12\] SECURITY\[2046\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-10-23T02:34:12.121-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="9274001148857315004",SessionID="0x7f613013d028",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.65.87/50842",ACLName="no_extension_match"
\[2019-10-23 02:34:33\] SECURITY\[2046\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-10-23T02:34:33.079-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="8856801148833566011",SessionID="0x7f61300a2fa8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.125.65.87/60679",ACLNam
2019-10-23 14:46:46
117.50.67.214 attack
Oct 23 06:02:31 venus sshd\[30466\]: Invalid user seidel from 117.50.67.214 port 41522
Oct 23 06:02:31 venus sshd\[30466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.67.214
Oct 23 06:02:33 venus sshd\[30466\]: Failed password for invalid user seidel from 117.50.67.214 port 41522 ssh2
...
2019-10-23 14:26:39
36.111.36.83 attackspambots
SSH invalid-user multiple login try
2019-10-23 14:43:21
146.88.240.4 attackbots
23.10.2019 06:16:07 Connection to port 5093 blocked by firewall
2019-10-23 14:19:52
58.221.101.182 attackspambots
2019-10-23T06:09:25.689898abusebot-2.cloudsearch.cf sshd\[8934\]: Invalid user trendimsa1.0 from 58.221.101.182 port 45866
2019-10-23 14:36:11
92.119.160.90 attack
Oct 23 08:04:25 mc1 kernel: \[3097013.092359\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.90 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=45276 PROTO=TCP SPT=50663 DPT=949 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 23 08:10:01 mc1 kernel: \[3097348.898777\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.90 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=46283 PROTO=TCP SPT=50663 DPT=966 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 23 08:10:49 mc1 kernel: \[3097397.524200\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.90 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=11916 PROTO=TCP SPT=50659 DPT=9265 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-23 14:21:12
118.25.103.132 attackbots
Oct 23 00:55:25 ws19vmsma01 sshd[31476]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.103.132
Oct 23 00:55:27 ws19vmsma01 sshd[31476]: Failed password for invalid user user from 118.25.103.132 port 57040 ssh2
...
2019-10-23 14:22:30
185.156.73.27 attackspambots
Automatic report - Port Scan
2019-10-23 14:49:44
148.70.77.22 attackbots
ssh failed login
2019-10-23 14:13:48
154.127.141.126 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-10-23 14:28:22

Recently Reported IPs

156.208.133.151 89.142.166.163 18.230.61.111 1.239.119.98
193.51.118.74 159.224.86.105 128.108.42.82 93.172.215.221
83.72.99.176 56.184.155.190 52.221.100.200 37.23.12.2
36.202.191.82 134.36.7.139 76.206.191.83 63.90.171.239
179.199.142.222 175.139.180.241 178.40.160.101 124.97.122.184