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: Viet Nam

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

;; QUESTION SECTION:
;116.104.69.16.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 23:55:59 CST 2022
;; MSG SIZE  rcvd: 106
Host info
16.69.104.116.in-addr.arpa domain name pointer dynamic-ip-adsl.viettel.vn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
16.69.104.116.in-addr.arpa	name = dynamic-ip-adsl.viettel.vn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
202.53.165.218 attackbots
2019-07-23 15:19:46 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/query/ip/202.53.165.218)
2019-07-23 15:19:46 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/query/ip/202.53.165.218)
2019-07-23 15:19:47 H=(liveus.it) [202.53.165.218]:46016 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/sbl/query/SBLCSS)
...
2019-07-24 06:32:00
104.248.254.222 attack
Jul 23 16:20:58 aat-srv002 sshd[27176]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.254.222
Jul 23 16:20:59 aat-srv002 sshd[27176]: Failed password for invalid user r from 104.248.254.222 port 47210 ssh2
Jul 23 16:25:18 aat-srv002 sshd[27273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.254.222
Jul 23 16:25:20 aat-srv002 sshd[27273]: Failed password for invalid user traffic from 104.248.254.222 port 46060 ssh2
...
2019-07-24 05:46:10
148.66.152.175 attackbots
fail2ban honeypot
2019-07-24 05:52:27
178.128.3.152 attackbots
IP attempted unauthorised action
2019-07-24 05:49:58
185.74.39.111 attackspambots
Automatic report - Port Scan Attack
2019-07-24 06:18:00
89.222.164.191 attackspambots
[portscan] Port scan
2019-07-24 05:53:00
103.129.221.62 attack
Jul 24 00:01:20 mail sshd\[4420\]: Invalid user vbox from 103.129.221.62 port 43972
Jul 24 00:01:20 mail sshd\[4420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.129.221.62
Jul 24 00:01:22 mail sshd\[4420\]: Failed password for invalid user vbox from 103.129.221.62 port 43972 ssh2
Jul 24 00:06:19 mail sshd\[5241\]: Invalid user support from 103.129.221.62 port 38290
Jul 24 00:06:19 mail sshd\[5241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.129.221.62
2019-07-24 06:12:06
185.175.93.105 attackspam
23.07.2019 20:47:14 Connection to port 17901 blocked by firewall
2019-07-24 05:54:28
210.51.50.119 attackbots
Jul 23 23:21:06 tux-35-217 sshd\[25336\]: Invalid user justin from 210.51.50.119 port 1412
Jul 23 23:21:06 tux-35-217 sshd\[25336\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.51.50.119
Jul 23 23:21:08 tux-35-217 sshd\[25336\]: Failed password for invalid user justin from 210.51.50.119 port 1412 ssh2
Jul 23 23:24:29 tux-35-217 sshd\[25343\]: Invalid user admin from 210.51.50.119 port 41979
Jul 23 23:24:29 tux-35-217 sshd\[25343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.51.50.119
...
2019-07-24 05:59:41
118.172.229.184 attackspam
2019-07-23T21:30:55.309672abusebot-6.cloudsearch.cf sshd\[4868\]: Invalid user tj from 118.172.229.184 port 53700
2019-07-24 05:47:28
187.237.130.98 attackbots
Jul 23 21:23:14 ip-172-31-62-245 sshd\[2489\]: Invalid user angelica from 187.237.130.98\
Jul 23 21:23:15 ip-172-31-62-245 sshd\[2489\]: Failed password for invalid user angelica from 187.237.130.98 port 34072 ssh2\
Jul 23 21:28:00 ip-172-31-62-245 sshd\[2528\]: Invalid user dpn from 187.237.130.98\
Jul 23 21:28:02 ip-172-31-62-245 sshd\[2528\]: Failed password for invalid user dpn from 187.237.130.98 port 56834 ssh2\
Jul 23 21:32:53 ip-172-31-62-245 sshd\[2558\]: Invalid user apagar from 187.237.130.98\
2019-07-24 05:44:59
209.17.97.18 attack
Automatic report - Banned IP Access
2019-07-24 06:25:52
23.225.177.245 attack
HTTP/S authentication failure x 8 reported by Fail2Ban
...
2019-07-24 06:13:10
182.160.114.45 attackbots
Jul 23 23:49:23 eventyay sshd[6463]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.160.114.45
Jul 23 23:49:25 eventyay sshd[6463]: Failed password for invalid user culture from 182.160.114.45 port 48594 ssh2
Jul 23 23:54:38 eventyay sshd[7704]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.160.114.45
...
2019-07-24 05:58:48
107.170.199.82 attackbots
Portscan or hack attempt detected by psad/fwsnort
2019-07-24 06:08:19

Recently Reported IPs

83.202.219.180 117.5.140.221 103.144.14.194 193.233.230.110
186.24.45.114 46.109.89.73 172.241.214.245 236.64.65.148
47.243.252.15 178.45.66.242 81.163.8.252 191.36.147.53
45.83.65.211 191.240.118.51 201.184.50.254 183.93.134.158
144.126.208.202 175.5.11.148 119.204.200.183 200.38.231.136