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: Singapore

Region: unknown

Country: Singapore

Internet Service Provider: SingTel

Hostname: unknown

Organization: Singtel Fibre Broadband

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;116.14.54.80.			IN	A

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Aug 15 03:47:51 CST 2019
;; MSG SIZE  rcvd: 116
Host info
80.54.14.116.in-addr.arpa domain name pointer bb116-14-54-80.singnet.com.sg.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
80.54.14.116.in-addr.arpa	name = bb116-14-54-80.singnet.com.sg.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.139.12.24 attack
Brute force attempt
2019-10-09 06:47:21
181.63.245.127 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-10-09 07:07:09
103.91.120.42 attack
Unauthorized connection attempt from IP address 103.91.120.42 on Port 445(SMB)
2019-10-09 07:26:48
104.168.199.165 attack
Tried sshing with brute force.
2019-10-09 07:04:48
185.232.67.8 attackbotsspam
Oct  9 00:11:39 dedicated sshd[5356]: Invalid user admin from 185.232.67.8 port 44914
2019-10-09 06:47:01
188.208.120.234 attackbotsspam
Unauthorized connection attempt from IP address 188.208.120.234 on Port 445(SMB)
2019-10-09 06:53:16
164.132.58.33 attack
Oct  9 00:57:08 vps01 sshd[18485]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.58.33
Oct  9 00:57:10 vps01 sshd[18485]: Failed password for invalid user foo from 164.132.58.33 port 44559 ssh2
2019-10-09 07:10:17
46.101.27.6 attack
SSH Bruteforce attempt
2019-10-09 06:58:16
213.136.77.106 attackbots
Fail2Ban Ban Triggered
2019-10-09 07:18:14
178.44.171.43 attack
Unauthorized connection attempt from IP address 178.44.171.43 on Port 445(SMB)
2019-10-09 06:43:58
200.169.223.98 attackspambots
2019-10-08T22:44:14.160019abusebot-8.cloudsearch.cf sshd\[23239\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.169.223.98  user=root
2019-10-09 07:17:14
104.244.78.231 attackbots
09.10.2019 00:57:16 - Wordpress fail 
Detected by ELinOX-ALM
2019-10-09 07:20:07
222.186.175.163 attackspambots
Oct  9 01:59:13 pkdns2 sshd\[62180\]: Failed password for root from 222.186.175.163 port 47864 ssh2Oct  9 01:59:17 pkdns2 sshd\[62180\]: Failed password for root from 222.186.175.163 port 47864 ssh2Oct  9 01:59:21 pkdns2 sshd\[62180\]: Failed password for root from 222.186.175.163 port 47864 ssh2Oct  9 01:59:40 pkdns2 sshd\[62191\]: Failed password for root from 222.186.175.163 port 23462 ssh2Oct  9 02:00:02 pkdns2 sshd\[62191\]: Failed password for root from 222.186.175.163 port 23462 ssh2Oct  9 02:00:12 pkdns2 sshd\[62247\]: Failed password for root from 222.186.175.163 port 5376 ssh2
...
2019-10-09 07:05:53
58.254.132.41 attackbotsspam
k+ssh-bruteforce
2019-10-09 07:09:25
179.198.111.111 attackbots
Unauthorized connection attempt from IP address 179.198.111.111 on Port 445(SMB)
2019-10-09 06:57:16

Recently Reported IPs

2.115.184.166 85.43.210.245 154.59.152.67 134.193.137.111
13.210.177.21 222.119.168.54 60.225.35.32 102.247.221.91
66.247.65.206 145.8.201.226 45.133.156.91 49.200.188.147
206.219.219.115 60.20.112.163 110.121.57.12 120.247.252.236
68.221.136.151 106.52.155.197 5.154.109.157 77.30.194.62