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: Frankfurt am Main

Region: Hessen

Country: Germany

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

;; QUESTION SECTION:
;52.57.245.52.			IN	A

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

;; Query time: 194 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 02 16:48:05 CST 2022
;; MSG SIZE  rcvd: 105
Host info
52.245.57.52.in-addr.arpa domain name pointer ec2-52-57-245-52.eu-central-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.245.57.52.in-addr.arpa	name = ec2-52-57-245-52.eu-central-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.103.127.250 attack
Brute forcing RDP port 3389
2019-11-24 09:50:38
218.107.133.49 attack
2019-11-23 22:54:23 dovecot_login authenticator failed for (lerctr.com) [218.107.133.49]:48602 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=nologin@lerctr.org)
2019-11-23 22:54:41 dovecot_login authenticator failed for (lerctr.com) [218.107.133.49]:50504 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=password123@lerctr.org)
2019-11-23 22:54:56 dovecot_login authenticator failed for (lerctr.com) [218.107.133.49]:52668 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=contact@lerctr.org)
...
2019-11-24 13:29:24
103.52.16.35 attackbots
$f2bV_matches
2019-11-24 13:06:13
68.183.153.161 attackbotsspam
Nov 24 07:13:13 server sshd\[7762\]: User root from 68.183.153.161 not allowed because listed in DenyUsers
Nov 24 07:13:13 server sshd\[7762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.153.161  user=root
Nov 24 07:13:15 server sshd\[7762\]: Failed password for invalid user root from 68.183.153.161 port 41404 ssh2
Nov 24 07:19:24 server sshd\[6319\]: User root from 68.183.153.161 not allowed because listed in DenyUsers
Nov 24 07:19:24 server sshd\[6319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.153.161  user=root
2019-11-24 13:24:02
106.12.13.143 attackspambots
2019-11-24T04:55:24.779843abusebot-7.cloudsearch.cf sshd\[10072\]: Invalid user stebbings from 106.12.13.143 port 43298
2019-11-24 13:01:08
187.173.247.50 attack
Nov 24 06:51:35 vibhu-HP-Z238-Microtower-Workstation sshd\[30142\]: Invalid user 123@p@$$w0rd from 187.173.247.50
Nov 24 06:51:35 vibhu-HP-Z238-Microtower-Workstation sshd\[30142\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.173.247.50
Nov 24 06:51:37 vibhu-HP-Z238-Microtower-Workstation sshd\[30142\]: Failed password for invalid user 123@p@$$w0rd from 187.173.247.50 port 50658 ssh2
Nov 24 06:59:34 vibhu-HP-Z238-Microtower-Workstation sshd\[30449\]: Invalid user lekve from 187.173.247.50
Nov 24 06:59:34 vibhu-HP-Z238-Microtower-Workstation sshd\[30449\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.173.247.50
...
2019-11-24 09:41:53
180.106.81.168 attackbots
Nov 23 21:10:01 mockhub sshd[19560]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.106.81.168
Nov 23 21:10:04 mockhub sshd[19560]: Failed password for invalid user do from 180.106.81.168 port 35906 ssh2
...
2019-11-24 13:27:58
211.75.102.247 attackbotsspam
11/23/2019-17:42:05.778369 211.75.102.247 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-24 09:55:44
121.69.130.2 attackbotsspam
SSHScan
2019-11-24 09:50:59
125.160.67.254 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 04:55:17.
2019-11-24 13:14:45
197.232.47.210 attackbotsspam
Nov 24 02:51:38 vpn01 sshd[5157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.232.47.210
Nov 24 02:51:40 vpn01 sshd[5157]: Failed password for invalid user guest from 197.232.47.210 port 46491 ssh2
...
2019-11-24 09:52:34
151.52.41.241 attackspambots
Automatic report - Port Scan Attack
2019-11-24 09:49:14
1.179.128.124 attack
SMB Server BruteForce Attack
2019-11-24 09:51:54
189.170.6.8 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 04:55:19.
2019-11-24 13:11:42
1.180.133.42 attackbots
Nov 23 21:13:55 mockhub sshd[19681]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.180.133.42
Nov 23 21:13:57 mockhub sshd[19681]: Failed password for invalid user dossie from 1.180.133.42 port 34050 ssh2
...
2019-11-24 13:27:30

Recently Reported IPs

208.46.121.138 74.68.32.73 90.216.239.12 53.193.38.110
88.131.178.88 13.29.188.38 50.83.195.180 36.150.1.95
162.244.118.115 100.35.151.141 50.39.174.173 244.5.171.73
7.212.21.182 30.74.185.68 216.242.23.241 200.214.125.26
206.143.210.43 16.37.222.14 246.141.141.29 26.10.35.56