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

;; QUESTION SECTION:
;134.245.13.20.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:08:33 CST 2022
;; MSG SIZE  rcvd: 106
Host info
20.13.245.134.in-addr.arpa domain name pointer uk-s4.uni-kiel.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
20.13.245.134.in-addr.arpa	name = uk-s4.uni-kiel.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.28.191.35 attackbotsspam
Mar 19 22:36:08 ns382633 sshd\[11343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.191.35  user=root
Mar 19 22:36:10 ns382633 sshd\[11343\]: Failed password for root from 129.28.191.35 port 47290 ssh2
Mar 19 22:51:09 ns382633 sshd\[14375\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.191.35  user=root
Mar 19 22:51:10 ns382633 sshd\[14375\]: Failed password for root from 129.28.191.35 port 57054 ssh2
Mar 19 22:54:27 ns382633 sshd\[14661\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.191.35  user=root
2020-03-20 06:09:21
222.186.15.10 attack
19.03.2020 22:08:46 SSH access blocked by firewall
2020-03-20 05:58:36
138.197.148.135 attackbots
Mar 19 22:15:21 163-172-32-151 sshd[29932]: Invalid user ubuntu from 138.197.148.135 port 46606
...
2020-03-20 05:55:15
178.33.229.120 attack
SSH Invalid Login
2020-03-20 05:50:04
52.224.180.67 attackbotsspam
Mar 19 21:42:40 XXXXXX sshd[28882]: Invalid user gitlab-psql from 52.224.180.67 port 26502
2020-03-20 06:16:19
222.186.42.75 attackspam
19.03.2020 21:55:34 SSH access blocked by firewall
2020-03-20 05:58:04
157.230.190.1 attackspam
frenzy
2020-03-20 06:09:04
173.211.31.234 attackspambots
(From keithhoff@imail.party) 
Hello,

I have not received an update regarding measures you're taking to combat COVID-19. I hope you'll assure us that you are following all recently released guidelines and taking every precaution to protect our community?

I'm very concerned that countless young people are not taking COVID-19 seriously (ex. the Spring Break beaches are still packed). I think the only way to combat this 'whatever attitude' is by sharing as much information as possible. 

I hope you will add an alert banner with a link to the CDC's coronavirus page (https://www.cdc.gov/coronavirus/2019-ncov/index.html) or the WHO's page. More importantly, please consider copy & pasting this Creative Commons 4.0 (free to re-publish) article to your site (https://covidblog.info).

Without strict measures and an *educated community*, the number of cases will increase exponentially throughout the global population!

Stay safe,
Keith
2020-03-20 06:15:50
46.101.1.131 attackbots
Invalid user postgres from 46.101.1.131 port 52252
2020-03-20 06:11:14
156.96.153.204 attackbots
Mar 19 18:10:50 ns41 sshd[24752]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.96.153.204
2020-03-20 05:52:26
51.178.81.239 attackbotsspam
SSH Invalid Login
2020-03-20 05:37:55
104.236.63.99 attack
SSH Brute-Force attacks
2020-03-20 06:16:46
49.235.87.213 attackspam
Mar 19 21:48:06 haigwepa sshd[12042]: Failed password for root from 49.235.87.213 port 35142 ssh2
...
2020-03-20 05:39:03
162.245.222.117 attackbots
(From keithhoff@imail.party) 
Hello,

I have not received an update regarding measures you're taking to combat COVID-19. I hope you'll assure us that you are following all recently released guidelines and taking every precaution to protect our community?

I'm very concerned that countless young people are not taking COVID-19 seriously (ex. the Spring Break beaches are still packed). I think the only way to combat this 'whatever attitude' is by sharing as much information as possible. 

I hope you will add an alert banner with a link to the CDC's coronavirus page (https://www.cdc.gov/coronavirus/2019-ncov/index.html) or the WHO's page. More importantly, please consider copy & pasting this Creative Commons 4.0 (free to re-publish) article to your site (https://covidblog.info).

Without strict measures and an *educated community*, the number of cases will increase exponentially throughout the global population!

Stay safe,
Keith
2020-03-20 06:17:19
49.235.49.150 attackspambots
Mar 19 14:51:15 server1 sshd\[1985\]: Invalid user freeswitch from 49.235.49.150
Mar 19 14:51:15 server1 sshd\[1985\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.49.150 
Mar 19 14:51:17 server1 sshd\[1985\]: Failed password for invalid user freeswitch from 49.235.49.150 port 54814 ssh2
Mar 19 14:55:50 server1 sshd\[3286\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.49.150  user=root
Mar 19 14:55:51 server1 sshd\[3286\]: Failed password for root from 49.235.49.150 port 44234 ssh2
...
2020-03-20 05:39:19

Recently Reported IPs

104.22.1.5 134.29.114.162 134.255.4.201 134.245.13.21
134.249.57.23 134.236.97.194 104.22.1.52 134.213.47.186
134.245.13.22 21.235.98.228 104.22.14.19 104.22.14.195
104.22.14.2 104.22.14.205 104.22.14.206 82.159.118.192
104.22.14.214 104.22.14.220 104.22.14.221 104.22.14.229