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: United States

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

;; QUESTION SECTION:
;54.199.139.5.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 04:20:00 CST 2022
;; MSG SIZE  rcvd: 105
Host info
5.139.199.54.in-addr.arpa domain name pointer ec2-54-199-139-5.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
5.139.199.54.in-addr.arpa	name = ec2-54-199-139-5.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.236.75.4 attack
Caught in portsentry honeypot
2019-08-22 17:16:19
119.48.68.217 attackbots
Seq 2995002506
2019-08-22 16:21:00
175.150.250.136 attackbotsspam
Seq 2995002506
2019-08-22 16:15:28
117.86.132.218 attack
Seq 2995002506
2019-08-22 16:22:01
152.168.243.234 attack
Aug 21 22:42:24 web9 sshd\[31127\]: Invalid user yao from 152.168.243.234
Aug 21 22:42:24 web9 sshd\[31127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.168.243.234
Aug 21 22:42:26 web9 sshd\[31127\]: Failed password for invalid user yao from 152.168.243.234 port 35110 ssh2
Aug 21 22:47:55 web9 sshd\[32404\]: Invalid user miner from 152.168.243.234
Aug 21 22:47:55 web9 sshd\[32404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.168.243.234
2019-08-22 16:59:02
190.119.190.122 attackspambots
Aug 21 22:43:00 kapalua sshd\[8423\]: Invalid user sprd!@\#\$%sapphire from 190.119.190.122
Aug 21 22:43:00 kapalua sshd\[8423\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.119.190.122
Aug 21 22:43:02 kapalua sshd\[8423\]: Failed password for invalid user sprd!@\#\$%sapphire from 190.119.190.122 port 35964 ssh2
Aug 21 22:47:48 kapalua sshd\[8885\]: Invalid user 123456 from 190.119.190.122
Aug 21 22:47:48 kapalua sshd\[8885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.119.190.122
2019-08-22 17:06:30
101.21.106.124 attack
Seq 2995002506
2019-08-22 16:26:57
218.92.0.173 attackbots
$f2bV_matches
2019-08-22 17:11:22
60.22.194.127 attackspambots
Seq 2995002506
2019-08-22 16:27:49
27.209.157.211 attackspam
Seq 2995002506
2019-08-22 16:30:51
108.36.94.38 attackspambots
Aug 22 11:08:58 localhost sshd\[19576\]: Invalid user bp from 108.36.94.38 port 18519
Aug 22 11:08:58 localhost sshd\[19576\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.36.94.38
Aug 22 11:09:00 localhost sshd\[19576\]: Failed password for invalid user bp from 108.36.94.38 port 18519 ssh2
2019-08-22 17:13:44
116.20.231.114 attack
Seq 2995002506
2019-08-22 16:39:37
27.42.247.192 attackspambots
Seq 2995002506
2019-08-22 16:12:58
125.111.154.188 attackspam
Seq 2995002506
2019-08-22 16:35:11
115.216.230.252 attack
Seq 2995002506
2019-08-22 16:23:23

Recently Reported IPs

2.12.146.221 125.87.189.220 31.31.188.76 175.109.132.3
109.10.245.84 21.83.209.154 246.89.73.64 102.122.108.194
236.158.161.31 252.170.151.127 51.11.194.213 208.26.213.168
224.203.230.125 157.123.192.131 168.102.133.126 135.28.106.205
19.190.178.251 89.178.112.52 175.14.203.62 146.241.20.91