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

;; QUESTION SECTION:
;27.139.240.252.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 22:47:19 CST 2025
;; MSG SIZE  rcvd: 107
Host info
252.240.139.27.in-addr.arpa domain name pointer 27-139-240-252.rev.home.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
252.240.139.27.in-addr.arpa	name = 27-139-240-252.rev.home.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.37.191.23 attackbotsspam
37215/tcp 52869/tcp...
[2020-01-13/02-26]3092pkt,2pt.(tcp)
2020-02-27 00:57:11
211.75.174.135 attackspambots
$f2bV_matches
2020-02-27 00:27:43
139.59.169.37 attack
Feb 26 17:00:13 vpn01 sshd[29446]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.169.37
Feb 26 17:00:15 vpn01 sshd[29446]: Failed password for invalid user narciso from 139.59.169.37 port 34436 ssh2
...
2020-02-27 00:43:15
211.58.11.234 attackbots
$f2bV_matches
2020-02-27 00:30:00
82.221.105.6 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 72 - port: 82 proto: TCP cat: Misc Attack
2020-02-27 00:59:56
176.113.115.203 attackbotsspam
scans 14 times in preceeding hours on the ports (in chronological order) 38535 38576 38662 38747 38970 38630 38691 38636 38746 38906 38786 38722 38633 38589 resulting in total of 65 scans from 176.113.115.0/24 block.
2020-02-27 01:12:45
103.130.71.254 attackbots
Telnetd brute force attack detected by fail2ban
2020-02-27 00:32:51
221.226.251.58 attackspambots
$f2bV_matches
2020-02-27 00:35:40
185.175.93.34 attackbots
Portscan or hack attempt detected by psad/fwsnort
2020-02-27 01:10:18
211.34.75.254 attackbots
$f2bV_matches
2020-02-27 00:42:11
49.247.203.22 attackspambots
Feb 26 17:53:25 MK-Soft-VM6 sshd[3359]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.247.203.22 
Feb 26 17:53:26 MK-Soft-VM6 sshd[3359]: Failed password for invalid user couchdb from 49.247.203.22 port 59124 ssh2
...
2020-02-27 01:02:41
128.199.81.66 attackbots
Port 12041 scan denied
2020-02-27 00:55:00
64.225.40.2 attackbots
RDP Brute-Force (honeypot 13)
2020-02-27 00:30:51
84.214.176.227 attackspambots
Feb 26 17:52:49 localhost sshd\[16892\]: Invalid user username from 84.214.176.227 port 41842
Feb 26 17:52:49 localhost sshd\[16892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.214.176.227
Feb 26 17:52:52 localhost sshd\[16892\]: Failed password for invalid user username from 84.214.176.227 port 41842 ssh2
2020-02-27 00:59:38
176.113.70.60 attack
176.113.70.60 was recorded 11 times by 5 hosts attempting to connect to the following ports: 1900. Incident counter (4h, 24h, all-time): 11, 68, 2939
2020-02-27 00:50:42

Recently Reported IPs

43.18.214.161 225.26.148.179 87.113.143.118 92.106.140.100
87.199.79.135 226.132.131.200 161.249.40.200 26.218.136.72
87.79.98.233 209.225.217.114 23.32.110.21 174.76.118.56
131.15.128.153 85.95.105.185 184.152.237.141 141.11.162.82
42.243.202.143 244.187.17.53 97.157.223.42 238.164.130.86