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: NTT docomo

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

;; QUESTION SECTION:
;27.230.139.45.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 08:05:43 CST 2025
;; MSG SIZE  rcvd: 106
Host info
45.139.230.27.in-addr.arpa domain name pointer mo27-230-139-45.air.mopera.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.139.230.27.in-addr.arpa	name = mo27-230-139-45.air.mopera.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
82.223.3.157 attackbotsspam
5x Failed Password
2019-10-18 05:50:38
184.30.210.217 attackspam
10/17/2019-23:41:07.544742 184.30.210.217 Protocol: 6 SURICATA TLS invalid record/traffic
2019-10-18 06:02:50
201.215.32.35 attack
Jan 27 19:20:32 odroid64 sshd\[27854\]: Invalid user ts3 from 201.215.32.35
Jan 27 19:20:32 odroid64 sshd\[27854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.215.32.35
Jan 27 19:20:33 odroid64 sshd\[27854\]: Failed password for invalid user ts3 from 201.215.32.35 port 45974 ssh2
...
2019-10-18 05:49:47
148.70.246.130 attack
2019-10-17T21:51:30.381598scmdmz1 sshd\[652\]: Invalid user gymnastics from 148.70.246.130 port 54920
2019-10-17T21:51:30.384381scmdmz1 sshd\[652\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.246.130
2019-10-17T21:51:32.671487scmdmz1 sshd\[652\]: Failed password for invalid user gymnastics from 148.70.246.130 port 54920 ssh2
...
2019-10-18 05:50:17
124.133.52.153 attack
2019-10-18T02:51:34.315447enmeeting.mahidol.ac.th sshd\[13277\]: User root from 124.133.52.153 not allowed because not listed in AllowUsers
2019-10-18T02:51:34.442101enmeeting.mahidol.ac.th sshd\[13277\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.133.52.153  user=root
2019-10-18T02:51:36.278411enmeeting.mahidol.ac.th sshd\[13277\]: Failed password for invalid user root from 124.133.52.153 port 34621 ssh2
...
2019-10-18 05:46:03
201.217.4.220 attack
Mar 20 02:52:10 odroid64 sshd\[5435\]: Invalid user admin from 201.217.4.220
Mar 20 02:52:10 odroid64 sshd\[5435\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.4.220
Mar 20 02:52:11 odroid64 sshd\[5435\]: Failed password for invalid user admin from 201.217.4.220 port 49234 ssh2
Mar 28 12:22:52 odroid64 sshd\[8399\]: Invalid user znc from 201.217.4.220
Mar 28 12:22:53 odroid64 sshd\[8399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.4.220
Mar 28 12:22:54 odroid64 sshd\[8399\]: Failed password for invalid user znc from 201.217.4.220 port 43032 ssh2
Apr  8 07:52:27 odroid64 sshd\[7817\]: Invalid user angel from 201.217.4.220
Apr  8 07:52:27 odroid64 sshd\[7817\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.4.220
Apr  8 07:52:29 odroid64 sshd\[7817\]: Failed password for invalid user angel from 201.217.4.220 port 47188 ssh2
Ap
...
2019-10-18 05:42:13
182.61.148.125 attackspam
Oct 17 15:51:44 Tower sshd[41666]: Connection from 182.61.148.125 port 47356 on 192.168.10.220 port 22
Oct 17 15:51:45 Tower sshd[41666]: Failed password for root from 182.61.148.125 port 47356 ssh2
Oct 17 15:51:45 Tower sshd[41666]: Received disconnect from 182.61.148.125 port 47356:11: Bye Bye [preauth]
Oct 17 15:51:45 Tower sshd[41666]: Disconnected from authenticating user root 182.61.148.125 port 47356 [preauth]
2019-10-18 05:37:26
201.216.208.195 attackbotsspam
Feb 22 17:24:55 odroid64 sshd\[6329\]: Invalid user teamspeak3 from 201.216.208.195
Feb 22 17:24:55 odroid64 sshd\[6329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.216.208.195
Feb 22 17:24:57 odroid64 sshd\[6329\]: Failed password for invalid user teamspeak3 from 201.216.208.195 port 40340 ssh2
...
2019-10-18 05:48:08
64.34.30.163 attackbotsspam
Oct 17 21:51:19 vpn01 sshd[30497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.34.30.163
Oct 17 21:51:21 vpn01 sshd[30497]: Failed password for invalid user fresco from 64.34.30.163 port 41362 ssh2
...
2019-10-18 06:01:38
45.55.206.241 attack
ssh failed login
2019-10-18 05:43:07
201.222.70.148 attack
May 22 20:10:39 odroid64 sshd\[1698\]: Invalid user user1 from 201.222.70.148
May 22 20:10:39 odroid64 sshd\[1698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.222.70.148
May 22 20:10:40 odroid64 sshd\[1698\]: Failed password for invalid user user1 from 201.222.70.148 port 42248 ssh2
...
2019-10-18 05:31:55
201.217.214.42 attack
Jun 22 12:50:14 odroid64 sshd\[14428\]: Invalid user postgres from 201.217.214.42
Jun 22 12:50:14 odroid64 sshd\[14428\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.214.42
Jun 22 12:50:16 odroid64 sshd\[14428\]: Failed password for invalid user postgres from 201.217.214.42 port 33124 ssh2
Jun 22 12:50:14 odroid64 sshd\[14428\]: Invalid user postgres from 201.217.214.42
Jun 22 12:50:14 odroid64 sshd\[14428\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.214.42
Jun 22 12:50:16 odroid64 sshd\[14428\]: Failed password for invalid user postgres from 201.217.214.42 port 33124 ssh2
...
2019-10-18 05:43:41
76.164.201.206 attackbots
Oct 17 22:51:09 server2 sshd\[9829\]: User root from 76.164.201.206 not allowed because not listed in AllowUsers
Oct 17 22:51:10 server2 sshd\[9831\]: Invalid user DUP from 76.164.201.206
Oct 17 22:51:11 server2 sshd\[9833\]: User root from 76.164.201.206 not allowed because not listed in AllowUsers
Oct 17 22:51:12 server2 sshd\[9835\]: Invalid user informix from 76.164.201.206
Oct 17 22:51:14 server2 sshd\[9837\]: Invalid user informix from 76.164.201.206
Oct 17 22:51:15 server2 sshd\[9839\]: User root from 76.164.201.206 not allowed because not listed in AllowUsers
2019-10-18 06:05:44
106.12.125.27 attackbots
SSH Brute-Force reported by Fail2Ban
2019-10-18 05:33:28
49.235.134.224 attackbotsspam
Invalid user anna from 49.235.134.224 port 52464
2019-10-18 05:44:39

Recently Reported IPs

93.166.196.141 220.205.196.36 4.254.157.193 200.40.222.150
251.49.115.242 207.100.149.158 18.233.70.39 100.247.231.75
238.119.73.31 155.36.9.171 82.154.18.107 19.59.83.96
236.33.185.234 114.63.85.28 134.125.32.93 180.189.61.92
52.184.255.43 30.19.208.89 251.154.182.145 56.239.246.4