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

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

;; QUESTION SECTION:
;103.14.97.80.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 01:20:50 CST 2022
;; MSG SIZE  rcvd: 105
Host info
80.97.14.103.in-addr.arpa domain name pointer server80.managedns.org.
80.97.14.103.in-addr.arpa domain name pointer 80.97.trunkoz.com.
80.97.14.103.in-addr.arpa domain name pointer inrl1.managedns.org.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.97.14.103.in-addr.arpa	name = 80.97.trunkoz.com.
80.97.14.103.in-addr.arpa	name = inrl1.managedns.org.
80.97.14.103.in-addr.arpa	name = server80.managedns.org.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.89.154.19 attackbots
Nov 16 16:18:26 localhost sshd\[88553\]: Invalid user mceachern from 159.89.154.19 port 38808
Nov 16 16:18:26 localhost sshd\[88553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.154.19
Nov 16 16:18:28 localhost sshd\[88553\]: Failed password for invalid user mceachern from 159.89.154.19 port 38808 ssh2
Nov 16 16:22:18 localhost sshd\[88650\]: Invalid user wisconsin123 from 159.89.154.19 port 46820
Nov 16 16:22:18 localhost sshd\[88650\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.154.19
...
2019-11-17 00:38:29
1.109.111.62 attackspambots
5555/tcp
[2019-11-16]1pkt
2019-11-17 00:32:02
106.255.84.110 attackspam
Triggered by Fail2Ban at Vostok web server
2019-11-17 00:36:49
159.65.89.92 attackbotsspam
159.65.89.92 was recorded 5 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 5, 5, 60
2019-11-17 00:14:15
103.105.179.189 attackbots
23/tcp
[2019-11-16]1pkt
2019-11-17 00:39:38
118.25.25.207 attackbots
Nov 16 16:52:31 tux-35-217 sshd\[8521\]: Invalid user contents from 118.25.25.207 port 46962
Nov 16 16:52:31 tux-35-217 sshd\[8521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.25.207
Nov 16 16:52:33 tux-35-217 sshd\[8521\]: Failed password for invalid user contents from 118.25.25.207 port 46962 ssh2
Nov 16 16:57:50 tux-35-217 sshd\[8548\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.25.207  user=root
...
2019-11-17 00:52:26
195.175.58.154 attack
Unauthorized access or intrusion attempt detected from Thor banned IP
2019-11-17 00:47:30
190.214.76.204 attackspam
60001/tcp
[2019-11-16]1pkt
2019-11-17 00:22:16
94.23.41.222 attackspam
Nov 16 17:40:48 server sshd\[15053\]: Invalid user dck from 94.23.41.222
Nov 16 17:40:48 server sshd\[15053\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns323499.ip-94-23-41.eu 
Nov 16 17:40:50 server sshd\[15053\]: Failed password for invalid user dck from 94.23.41.222 port 33166 ssh2
Nov 16 17:54:38 server sshd\[18662\]: Invalid user iv from 94.23.41.222
Nov 16 17:54:38 server sshd\[18662\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns323499.ip-94-23-41.eu 
...
2019-11-17 00:33:23
115.59.7.202 attackbots
port scan and connect, tcp 23 (telnet)
2019-11-17 00:19:44
182.113.192.25 attackbots
1024/tcp
[2019-11-16]1pkt
2019-11-17 00:47:47
185.143.223.133 attackspambots
185.143.223.133 was recorded 73 times by 18 hosts attempting to connect to the following ports: 20039,51974,41038,37475,59,43433,922,55755,39,42912,780,830,63233,44488,805,36465,62829,40402,46469,55522,53333,818,53031,20116,25254,883,1201,39394,5014,1103,42834,24245,37543,9349,54434,3459,89,41362,40385,64354,58549,53532,51511,19198,42429,47172,3893,22922,41819,63883,59216,2901,9449,5881,992,3213,766,320,57578,46701,20207,55916,41213,85,27177,1333,39091,50502,34518,42428,69,36061. Incident counter (4h, 24h, all-time): 73, 379, 1172
2019-11-17 00:30:18
91.193.102.106 attack
Nov 16 17:36:54 sd-53420 sshd\[7075\]: User backup from 91.193.102.106 not allowed because none of user's groups are listed in AllowGroups
Nov 16 17:36:54 sd-53420 sshd\[7075\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.193.102.106  user=backup
Nov 16 17:36:56 sd-53420 sshd\[7075\]: Failed password for invalid user backup from 91.193.102.106 port 48193 ssh2
Nov 16 17:40:54 sd-53420 sshd\[8284\]: Invalid user vbox from 91.193.102.106
Nov 16 17:40:54 sd-53420 sshd\[8284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.193.102.106
...
2019-11-17 00:48:09
45.229.154.100 attack
60001/tcp
[2019-11-16]1pkt
2019-11-17 00:52:47
111.93.242.226 attackbots
2019-11-16T15:13:05.092420shield sshd\[17409\]: Invalid user ubuntu from 111.93.242.226 port 14833
2019-11-16T15:13:05.098258shield sshd\[17409\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.242.226
2019-11-16T15:13:07.536398shield sshd\[17409\]: Failed password for invalid user ubuntu from 111.93.242.226 port 14833 ssh2
2019-11-16T15:13:15.259193shield sshd\[17450\]: Invalid user ubuntu from 111.93.242.226 port 7641
2019-11-16T15:13:15.264880shield sshd\[17450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.242.226
2019-11-17 00:24:14

Recently Reported IPs

103.14.97.125 103.14.97.82 103.14.97.91 103.14.98.161
103.14.98.202 103.14.99.202 103.14.99.237 212.58.244.57
103.140.108.50 103.140.126.101 103.140.132.16 103.140.180.145
103.140.180.152 103.140.188.61 193.236.52.240 103.140.205.136
103.140.238.166 103.140.238.36 103.140.238.40 103.140.238.44