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

Region: Tainan

Country: Taiwan, China

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

;; QUESTION SECTION:
;140.116.189.20.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 13 16:15:30 CST 2023
;; MSG SIZE  rcvd: 107
Host info
Host 20.189.116.140.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 20.189.116.140.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
128.199.129.27 attack
WordPress wp-login brute force :: 128.199.129.27 0.152 BYPASS [03/Oct/2019:07:23:43  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-03 09:50:32
14.162.151.134 attack
445/tcp 445/tcp 445/tcp
[2019-10-03]3pkt
2019-10-03 12:11:05
200.105.183.118 attackbots
Oct  2 15:56:15 php1 sshd\[6989\]: Invalid user ow from 200.105.183.118
Oct  2 15:56:15 php1 sshd\[6989\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=static-200-105-183-118.acelerate.net
Oct  2 15:56:16 php1 sshd\[6989\]: Failed password for invalid user ow from 200.105.183.118 port 30625 ssh2
Oct  2 16:01:06 php1 sshd\[7907\]: Invalid user anon from 200.105.183.118
Oct  2 16:01:06 php1 sshd\[7907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=static-200-105-183-118.acelerate.net
2019-10-03 10:06:35
49.88.112.68 attack
Oct  3 04:56:29 intra sshd\[2142\]: Failed password for root from 49.88.112.68 port 38157 ssh2Oct  3 04:56:31 intra sshd\[2142\]: Failed password for root from 49.88.112.68 port 38157 ssh2Oct  3 04:56:34 intra sshd\[2142\]: Failed password for root from 49.88.112.68 port 38157 ssh2Oct  3 04:57:13 intra sshd\[2168\]: Failed password for root from 49.88.112.68 port 55148 ssh2Oct  3 04:57:16 intra sshd\[2168\]: Failed password for root from 49.88.112.68 port 55148 ssh2Oct  3 04:57:18 intra sshd\[2168\]: Failed password for root from 49.88.112.68 port 55148 ssh2
...
2019-10-03 10:06:12
182.72.162.2 attackbots
2019-10-03T03:55:28.398303shield sshd\[16991\]: Invalid user caja01 from 182.72.162.2 port 10000
2019-10-03T03:55:28.403691shield sshd\[16991\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.162.2
2019-10-03T03:55:29.872791shield sshd\[16991\]: Failed password for invalid user caja01 from 182.72.162.2 port 10000 ssh2
2019-10-03T03:59:57.357564shield sshd\[17825\]: Invalid user administrador from 182.72.162.2 port 10000
2019-10-03T03:59:57.363146shield sshd\[17825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.162.2
2019-10-03 12:09:19
217.133.99.111 attackbotsspam
Oct  2 17:23:06 Tower sshd[3004]: Connection from 217.133.99.111 port 51560 on 192.168.10.220 port 22
Oct  2 17:23:10 Tower sshd[3004]: Invalid user zeta from 217.133.99.111 port 51560
Oct  2 17:23:10 Tower sshd[3004]: error: Could not get shadow information for NOUSER
Oct  2 17:23:10 Tower sshd[3004]: Failed password for invalid user zeta from 217.133.99.111 port 51560 ssh2
Oct  2 17:23:10 Tower sshd[3004]: Received disconnect from 217.133.99.111 port 51560:11: Bye Bye [preauth]
Oct  2 17:23:10 Tower sshd[3004]: Disconnected from invalid user zeta 217.133.99.111 port 51560 [preauth]
2019-10-03 09:54:46
103.99.113.62 attackbots
Oct  3 05:00:25 XXX sshd[27883]: Invalid user react from 103.99.113.62 port 53112
2019-10-03 12:08:07
64.222.246.86 attack
19/10/2@17:23:17: FAIL: Alarm-SSH address from=64.222.246.86
...
2019-10-03 10:08:32
198.144.108.117 attack
Spamassassin_198.144.108.117
2019-10-03 10:00:57
185.53.91.70 attackbotsspam
10/03/2019-03:01:56.480253 185.53.91.70 Protocol: 17 ET SCAN Sipvicious Scan
2019-10-03 09:58:08
123.231.44.71 attackbots
2019-10-03T01:23:10.433743abusebot-3.cloudsearch.cf sshd\[9459\]: Invalid user init from 123.231.44.71 port 57064
2019-10-03 09:45:31
52.192.73.251 attackbotsspam
SS1,DEF GET /wp-login.php
2019-10-03 10:05:49
117.1.67.76 attackspam
Oct  2 23:23:13 andromeda sshd\[56675\]: Invalid user admin from 117.1.67.76 port 59344
Oct  2 23:23:13 andromeda sshd\[56675\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.1.67.76
Oct  2 23:23:16 andromeda sshd\[56675\]: Failed password for invalid user admin from 117.1.67.76 port 59344 ssh2
2019-10-03 10:09:39
178.176.175.148 attackspambots
10/03/2019-03:35:25.076905 178.176.175.148 Protocol: 6 SURICATA SMTP tls rejected
2019-10-03 10:11:41
94.103.85.227 attackbotsspam
10/02/2019-20:55:00.249947 94.103.85.227 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-03 09:49:48

Recently Reported IPs

140.96.196.130 131.215.225.38 79.123.150.28 129.132.103.149
195.37.46.252 143.160.13.208 140.116.157.14 140.116.245.103
140.116.36.51 158.170.180.131 140.123.56.94 147.32.242.10
193.54.215.242 140.116.66.36 120.101.42.17 205.175.106.170
168.131.37.68 140.116.63.253 146.155.148.166 152.249.209.227