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

;; QUESTION SECTION:
;118.27.80.242.			IN	A

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

;; Query time: 108 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 17:23:56 CST 2022
;; MSG SIZE  rcvd: 106
Host info
242.80.27.118.in-addr.arpa domain name pointer v118-27-80-242.d1xu.static.cnode.io.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.80.27.118.in-addr.arpa	name = v118-27-80-242.d1xu.static.cnode.io.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
121.122.49.234 attack
Mar 12 12:25:38 ny01 sshd[29708]: Failed password for root from 121.122.49.234 port 51302 ssh2
Mar 12 12:29:09 ny01 sshd[31308]: Failed password for root from 121.122.49.234 port 50451 ssh2
2020-03-13 02:11:08
64.227.19.68 attack
2020-02-28T14:55:25.553Z CLOSE host=64.227.19.68 port=54808 fd=4 time=20.012 bytes=18
...
2020-03-13 02:22:10
74.208.173.91 attackbots
2019-11-09T21:53:11.092Z CLOSE host=74.208.173.91 port=53896 fd=4 time=30594.234 bytes=53157
...
2020-03-13 02:00:11
77.133.38.42 attackbots
2020-01-24T04:10:42.081Z CLOSE host=77.133.38.42 port=48730 fd=4 time=20.017 bytes=11
...
2020-03-13 01:55:34
83.97.20.160 attackbotsspam
83.97.20.160 was recorded 5 times by 1 hosts attempting to connect to the following ports: 111. Incident counter (4h, 24h, all-time): 5, 13, 1065
2020-03-13 02:26:26
62.2.86.48 attack
2020-01-29T15:04:01.720Z CLOSE host=62.2.86.48 port=44545 fd=4 time=40.031 bytes=33
...
2020-03-13 02:28:04
67.253.114.22 attackbotsspam
suspicious action Thu, 12 Mar 2020 11:14:04 -0300
2020-03-13 02:09:11
65.49.20.69 attackbots
2020-03-04T03:50:45.974Z CLOSE host=65.49.20.69 port=40338 fd=5 time=20.002 bytes=18
...
2020-03-13 02:14:25
185.21.41.71 attackbots
185.21.41.71 - - [12/Mar/2020:13:52:59 +0100] "GET /wp-login.php HTTP/1.1" 200 5347 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
185.21.41.71 - - [12/Mar/2020:13:53:00 +0100] "POST /wp-login.php HTTP/1.1" 200 6246 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
185.21.41.71 - - [12/Mar/2020:13:53:01 +0100] "POST /xmlrpc.php HTTP/1.1" 200 438 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-03-13 01:53:30
59.13.125.142 attackbots
suspicious action Thu, 12 Mar 2020 12:39:27 -0300
2020-03-13 02:31:01
66.181.167.53 attackspam
2020-01-25T19:02:48.629Z CLOSE host=66.181.167.53 port=50900 fd=4 time=20.010 bytes=8
...
2020-03-13 02:13:34
164.39.137.214 attackbots
Automatic report - Banned IP Access
2020-03-13 02:24:40
112.85.42.229 attackspambots
SSH auth scanning - multiple failed logins
2020-03-13 02:16:06
62.235.147.126 attack
2019-12-17T06:49:00.247Z CLOSE host=62.235.147.126 port=34012 fd=4 time=20.011 bytes=14
2019-12-17T06:49:00.247Z CLOSE host=62.235.147.126 port=34014 fd=5 time=20.010 bytes=4
...
2020-03-13 02:26:43
64.52.173.98 attackbotsspam
2020-01-13T04:27:29.130Z CLOSE host=64.52.173.98 port=58856 fd=4 time=20.020 bytes=30
...
2020-03-13 02:17:58

Recently Reported IPs

118.27.8.198 118.27.9.235 118.27.9.162 115.58.89.163
118.27.8.42 118.27.8.169 118.27.9.236 118.27.9.54
115.58.93.149 201.172.47.238 115.59.0.56 115.59.200.124
118.31.38.121 118.31.37.153 118.31.38.93 115.59.208.23
118.31.39.60 118.31.39.203 118.31.39.59 118.31.40.52