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

;; QUESTION SECTION:
;54.249.81.195.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 04:31:56 CST 2025
;; MSG SIZE  rcvd: 106
Host info
195.81.249.54.in-addr.arpa domain name pointer ec2-54-249-81-195.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
195.81.249.54.in-addr.arpa	name = ec2-54-249-81-195.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
13.89.238.253 attack
Attempted WordPress login: "GET /wp-login.php"
2019-10-31 20:45:19
111.231.113.236 attack
Oct 31 13:34:30 legacy sshd[14920]: Failed password for root from 111.231.113.236 port 57956 ssh2
Oct 31 13:40:04 legacy sshd[15100]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.113.236
Oct 31 13:40:06 legacy sshd[15100]: Failed password for invalid user darklight from 111.231.113.236 port 38956 ssh2
...
2019-10-31 20:49:51
31.207.33.10 attackbots
B: Abusive content scan (301)
2019-10-31 20:36:45
104.25.91.11 attackbots
HTTP 503 XSS Attempt
2019-10-31 20:50:23
36.152.65.201 attack
10/31/2019-13:07:36.798515 36.152.65.201 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 25
2019-10-31 21:02:13
220.202.15.66 attackbots
Oct 31 12:53:15 root sshd[610]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.202.15.66 
Oct 31 12:53:16 root sshd[610]: Failed password for invalid user ftpuser from 220.202.15.66 port 18663 ssh2
Oct 31 13:07:54 root sshd[765]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.202.15.66 
...
2019-10-31 20:52:32
198.71.235.65 attack
abcdata-sys.de:80 198.71.235.65 - - \[31/Oct/2019:13:08:07 +0100\] "POST /xmlrpc.php HTTP/1.1" 301 441 "-" "WordPress/4.5.7\; http://dayvaweiss.com"
www.goldgier.de 198.71.235.65 \[31/Oct/2019:13:08:07 +0100\] "POST /xmlrpc.php HTTP/1.1" 200 4484 "-" "WordPress/4.5.7\; http://dayvaweiss.com"
2019-10-31 20:43:02
144.217.214.25 attackbotsspam
Oct 31 13:36:15 meumeu sshd[10289]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.214.25 
Oct 31 13:36:17 meumeu sshd[10289]: Failed password for invalid user ubuntu4 from 144.217.214.25 port 33198 ssh2
Oct 31 13:40:31 meumeu sshd[10965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.214.25 
...
2019-10-31 21:05:25
62.234.122.141 attackbotsspam
Oct 31 13:08:33 srv206 sshd[4178]: Invalid user renato from 62.234.122.141
Oct 31 13:08:33 srv206 sshd[4178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.122.141
Oct 31 13:08:33 srv206 sshd[4178]: Invalid user renato from 62.234.122.141
Oct 31 13:08:35 srv206 sshd[4178]: Failed password for invalid user renato from 62.234.122.141 port 57240 ssh2
...
2019-10-31 20:22:43
192.227.107.133 attack
HTTP 503 XSS Attempt
2019-10-31 20:34:17
149.56.107.105 attack
Oct 31 13:07:37 sd-53420 sshd\[29904\]: Invalid user abcdef from 149.56.107.105
Oct 31 13:07:37 sd-53420 sshd\[29904\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.107.105
Oct 31 13:07:39 sd-53420 sshd\[29904\]: Failed password for invalid user abcdef from 149.56.107.105 port 57946 ssh2
Oct 31 13:08:36 sd-53420 sshd\[29963\]: Invalid user alexander from 149.56.107.105
Oct 31 13:08:36 sd-53420 sshd\[29963\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.107.105
...
2019-10-31 20:21:29
62.210.252.184 attack
Oct 31 01:11:20 server sshd\[14112\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-252-184.rev.poneytelecom.eu  user=root
Oct 31 01:11:22 server sshd\[14112\]: Failed password for root from 62.210.252.184 port 60226 ssh2
Oct 31 15:07:36 server sshd\[13757\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-252-184.rev.poneytelecom.eu  user=root
Oct 31 15:07:38 server sshd\[13757\]: Failed password for root from 62.210.252.184 port 58316 ssh2
Oct 31 15:07:38 server sshd\[13762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-252-184.rev.poneytelecom.eu  user=root
...
2019-10-31 21:00:01
185.40.4.228 attack
10/31/2019-13:07:54.492880 185.40.4.228 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-31 20:53:21
109.202.117.30 attackspam
10/31/2019-08:08:21.695623 109.202.117.30 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-31 20:35:13
109.202.117.114 attack
10/31/2019-08:08:08.066559 109.202.117.114 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-31 20:44:25

Recently Reported IPs

86.43.82.6 167.195.124.195 27.95.15.29 246.168.17.122
36.21.121.35 21.112.131.191 17.128.9.215 171.129.153.15
233.98.220.63 242.26.166.183 119.229.4.91 244.126.212.128
44.248.229.98 153.246.11.42 57.204.221.78 46.246.4.148
88.184.201.230 154.188.205.64 220.59.247.26 90.87.170.108