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

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:
IP Type Details Datetime
116.109.139.66 attack
Automatic report - Port Scan Attack
2020-04-14 07:45:22
116.109.139.26 attackspam
DATE:2019-11-04 05:56:31, IP:116.109.139.26, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-11-04 13:44:34
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.109.139.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20068
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;116.109.139.92.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 11 03:46:13 CST 2023
;; MSG SIZE  rcvd: 107
Host info
92.139.109.116.in-addr.arpa has no PTR record
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
*** Can't find 92.139.109.116.in-addr.arpa.: No answer

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
128.199.133.201 attackbots
Mar 28 12:10:31: Invalid user mul from 128.199.133.201 port 49573
2020-03-29 07:33:59
209.200.15.168 attackbots
445/tcp 1433/tcp...
[2020-01-31/03-28]4pkt,2pt.(tcp)
2020-03-29 07:25:24
2.38.181.39 attack
Mar 28 16:14:49 mockhub sshd[4676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.38.181.39
Mar 28 16:14:51 mockhub sshd[4676]: Failed password for invalid user mba from 2.38.181.39 port 56553 ssh2
...
2020-03-29 07:16:12
200.69.250.253 attackspambots
Invalid user cacti from 200.69.250.253 port 52071
2020-03-29 07:30:43
106.13.114.228 attack
Mar 29 01:20:39 hosting sshd[22175]: Invalid user yxg from 106.13.114.228 port 50714
...
2020-03-29 07:22:31
45.40.201.5 attack
Invalid user dii from 45.40.201.5 port 48200
2020-03-29 07:19:44
187.3.139.213 attack
26/tcp 23/tcp
[2020-03-26/27]2pkt
2020-03-29 07:39:39
198.98.60.141 attackbotsspam
SSH Login Bruteforce
2020-03-29 07:14:28
180.168.141.246 attackspambots
Invalid user okk from 180.168.141.246 port 36472
2020-03-29 07:09:30
14.237.95.182 attack
23/tcp
[2020-03-28]1pkt
2020-03-29 07:45:09
132.148.17.97 attackbots
xmlrpc attack
2020-03-29 07:35:00
5.238.116.197 attackspam
37215/tcp 37215/tcp
[2020-03-26]2pkt
2020-03-29 07:43:07
45.141.84.29 attack
trying to access non-authorized port
2020-03-29 07:33:12
103.98.176.248 attack
Mar 28 23:36:46 vpn01 sshd[9503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.98.176.248
Mar 28 23:36:48 vpn01 sshd[9503]: Failed password for invalid user etownsley from 103.98.176.248 port 39886 ssh2
...
2020-03-29 07:08:26
218.56.161.69 attackspam
1433/tcp 1433/tcp 1433/tcp...
[2020-02-03/03-28]10pkt,1pt.(tcp)
2020-03-29 07:10:22

Recently Reported IPs

174.111.160.141 105.47.210.227 182.168.206.234 238.246.161.191
130.50.70.207 122.55.207.144 26.236.220.179 190.39.142.116
211.242.168.152 23.29.91.242 108.216.96.191 66.178.9.45
6.93.121.191 171.15.137.163 228.238.156.124 79.20.229.183
135.248.146.209 185.96.97.115 179.200.157.165 63.155.167.123