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: Cape Town

Region: Western Cape

Country: South Africa

Internet Service Provider: unknown

Hostname: unknown

Organization: UCT

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

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

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

;; Query time: 0 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Wed Aug 14 01:19:53 CST 2019
;; MSG SIZE  rcvd: 119
Host info
245.116.158.137.in-addr.arpa domain name pointer 3c-52-82-8a-aa-4f.lan.uct.ac.za.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
245.116.158.137.in-addr.arpa	name = 3c-52-82-8a-aa-4f.lan.uct.ac.za.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
78.186.24.218 attack
Automatic report - Port Scan Attack
2020-02-19 02:07:12
59.126.123.192 attackbotsspam
Feb 18 13:22:07 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:14 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:16 system,error,critical: login failure for user Administrator from 59.126.123.192 via telnet
Feb 18 13:22:21 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:27 system,error,critical: login failure for user guest from 59.126.123.192 via telnet
Feb 18 13:22:29 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:35 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
Feb 18 13:22:44 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:46 system,error,critical: login failure for user root from 59.126.123.192 via telnet
Feb 18 13:22:48 system,error,critical: login failure for user admin from 59.126.123.192 via telnet
2020-02-19 01:59:37
202.91.15.3 attackbots
Automatic report - XMLRPC Attack
2020-02-19 02:36:58
103.104.112.80 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-19 02:44:35
49.235.10.177 attackspam
2020-02-18T07:51:10.1203561495-001 sshd[7189]: Invalid user device from 49.235.10.177 port 47200
2020-02-18T07:51:10.1238191495-001 sshd[7189]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.10.177
2020-02-18T07:51:10.1203561495-001 sshd[7189]: Invalid user device from 49.235.10.177 port 47200
2020-02-18T07:51:12.1602571495-001 sshd[7189]: Failed password for invalid user device from 49.235.10.177 port 47200 ssh2
2020-02-18T07:59:48.7504001495-001 sshd[7589]: Invalid user kamal from 49.235.10.177 port 60902
2020-02-18T07:59:48.7545081495-001 sshd[7589]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.10.177
2020-02-18T07:59:48.7504001495-001 sshd[7589]: Invalid user kamal from 49.235.10.177 port 60902
2020-02-18T07:59:50.2386381495-001 sshd[7589]: Failed password for invalid user kamal from 49.235.10.177 port 60902 ssh2
2020-02-18T08:08:19.9997701495-001 sshd[8117]: Invalid user prueba from 4
...
2020-02-19 02:39:15
92.222.84.34 attack
Feb 18 14:22:13 amit sshd\[7294\]: Invalid user testuser from 92.222.84.34
Feb 18 14:22:13 amit sshd\[7294\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.84.34
Feb 18 14:22:15 amit sshd\[7294\]: Failed password for invalid user testuser from 92.222.84.34 port 33528 ssh2
...
2020-02-19 02:03:16
173.201.196.210 attackbots
Automatic report - XMLRPC Attack
2020-02-19 01:59:16
137.74.171.160 attack
Brute-force attempt banned
2020-02-19 02:04:08
110.43.208.244 attack
firewall-block, port(s): 88/tcp, 8080/tcp, 9520/tcp, 9527/tcp, 60001/tcp
2020-02-19 02:41:33
188.0.147.56 attack
Port 2323 (Mirai botnet) access denied
2020-02-19 02:38:50
192.241.237.71 attackbotsspam
Honeypot hit: misc
2020-02-19 02:26:21
37.194.179.100 attackbotsspam
2020-02-18T13:50:31.809933ldap.arvenenaske.de sshd[4625]: Connection from 37.194.179.100 port 54600 on 5.199.128.55 port 22
2020-02-18T13:50:32.498528ldap.arvenenaske.de sshd[4625]: Invalid user jeanette from 37.194.179.100 port 54600
2020-02-18T13:50:32.508030ldap.arvenenaske.de sshd[4625]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.194.179.100 user=jeanette
2020-02-18T13:50:32.509164ldap.arvenenaske.de sshd[4625]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.194.179.100
2020-02-18T13:50:31.809933ldap.arvenenaske.de sshd[4625]: Connection from 37.194.179.100 port 54600 on 5.199.128.55 port 22
2020-02-18T13:50:32.498528ldap.arvenenaske.de sshd[4625]: Invalid user jeanette from 37.194.179.100 port 54600
2020-02-18T13:50:33.993659ldap.arvenenaske.de sshd[4625]: Failed password for invalid user jeanette from 37.194.179.100 port 54600 ssh2
2020-02-18T13:57:50.026312ldap.arvenenaske.d........
------------------------------
2020-02-19 02:46:13
45.154.255.44 attackspam
02/18/2020-14:22:37.403044 45.154.255.44 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 67
2020-02-19 02:12:49
223.197.161.43 attackspam
Port probing on unauthorized port 81
2020-02-19 02:26:54
110.227.108.104 attackspambots
scan z
2020-02-19 02:12:17

Recently Reported IPs

108.161.131.13 106.153.75.25 100.220.47.8 67.242.117.38
18.124.52.68 223.242.228.155 95.165.53.215 149.153.163.248
102.115.16.208 108.161.131.16 84.108.3.255 54.166.240.166
200.209.34.34 31.185.169.28 203.205.18.94 188.102.239.157
97.10.206.103 82.19.190.232 165.117.108.217 181.118.186.8