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: United States of America (the)

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

;; QUESTION SECTION:
;21.12.245.57.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 10:42:41 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 57.245.12.21.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 57.245.12.21.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
196.38.70.24 attack
Invalid user apache from 196.38.70.24 port 18132
2020-03-07 03:43:35
46.99.178.18 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 03:29:27
34.236.202.207 attackbotsspam
CMS (WordPress or Joomla) login attempt.
2020-03-07 03:35:06
80.211.50.102 attackbots
Trolling for resource vulnerabilities
2020-03-07 03:38:11
121.17.168.169 attackspambots
3389/tcp
[2020-03-06]1pkt
2020-03-07 03:56:14
93.77.117.167 attack
Mar  6 14:28:32 grey postfix/smtpd\[23651\]: NOQUEUE: reject: RCPT from unknown\[93.77.117.167\]: 554 5.7.1 Service unavailable\; Client host \[93.77.117.167\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[93.77.117.167\]\; from=\ to=\ proto=ESMTP helo=\<93-77-117-167.dynamic-FTTB.kharkov.volia.com\>
...
2020-03-07 04:10:24
45.151.254.218 attackspambots
45.151.254.218 was recorded 16 times by 9 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 16, 117, 853
2020-03-07 04:08:50
219.78.206.158 attackspambots
Honeypot attack, port: 5555, PTR: n219078206158.netvigator.com.
2020-03-07 03:38:39
183.136.239.206 attackbotsspam
suspicious action Fri, 06 Mar 2020 10:29:24 -0300
2020-03-07 03:29:45
184.95.59.122 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2020-03-07 03:46:38
183.136.188.116 attackbotsspam
suspicious action Fri, 06 Mar 2020 10:29:02 -0300
2020-03-07 03:45:48
185.202.1.164 attackspambots
Mar  6 19:33:42 l03 sshd[10460]: Invalid user admin from 185.202.1.164 port 7896
...
2020-03-07 04:06:58
80.82.77.245 attackspam
Mar  6 19:44:00 debian-2gb-nbg1-2 kernel: \[5779404.477445\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.245 DST=195.201.40.59 LEN=57 TOS=0x00 PREC=0x00 TTL=247 ID=54321 PROTO=UDP SPT=35261 DPT=136 LEN=37
2020-03-07 03:44:48
200.209.174.76 attackspam
Mar  6 05:55:23 hanapaa sshd\[28892\]: Invalid user P4SSW0RD2020 from 200.209.174.76
Mar  6 05:55:23 hanapaa sshd\[28892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
Mar  6 05:55:25 hanapaa sshd\[28892\]: Failed password for invalid user P4SSW0RD2020 from 200.209.174.76 port 50151 ssh2
Mar  6 06:00:39 hanapaa sshd\[29309\]: Invalid user ROOT1@3\$ from 200.209.174.76
Mar  6 06:00:39 hanapaa sshd\[29309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
2020-03-07 03:39:14
120.132.109.178 attackspambots
SSH Brute Force
2020-03-07 03:39:56

Recently Reported IPs

199.77.222.186 81.248.92.53 96.107.75.12 246.198.189.28
240.160.161.140 193.35.116.135 42.6.125.59 250.195.43.119
114.19.188.247 109.150.69.111 104.240.72.80 153.233.103.96
114.222.220.18 87.234.183.212 180.188.39.244 155.57.44.149
229.96.84.221 135.55.54.14 149.128.70.172 133.142.236.163