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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;252.139.224.65.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 01:05:49 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 65.224.139.252.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 65.224.139.252.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
216.246.242.153 attackbotsspam
Apr 17 22:45:39 server1 sshd\[31243\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.246.242.153  user=root
Apr 17 22:45:42 server1 sshd\[31243\]: Failed password for root from 216.246.242.153 port 46780 ssh2
Apr 17 22:49:25 server1 sshd\[32284\]: Invalid user test3 from 216.246.242.153
Apr 17 22:49:25 server1 sshd\[32284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.246.242.153 
Apr 17 22:49:27 server1 sshd\[32284\]: Failed password for invalid user test3 from 216.246.242.153 port 54964 ssh2
...
2020-04-18 13:03:30
51.75.70.30 attackbots
Invalid user testftp from 51.75.70.30 port 40703
2020-04-18 13:15:53
134.175.54.154 attack
2020-04-18T03:55:00.320668upcloud.m0sh1x2.com sshd[31173]: Invalid user vd from 134.175.54.154 port 32034
2020-04-18 13:10:32
60.250.164.169 attackbotsspam
Apr 18 05:56:07 sip sshd[5615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.250.164.169
Apr 18 05:56:09 sip sshd[5615]: Failed password for invalid user rt from 60.250.164.169 port 56748 ssh2
Apr 18 06:03:38 sip sshd[8402]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.250.164.169
2020-04-18 12:58:26
163.172.61.214 attackbots
Apr 18 00:49:06 ws22vmsma01 sshd[140040]: Failed password for root from 163.172.61.214 port 43350 ssh2
...
2020-04-18 13:29:11
49.235.132.42 attack
Apr 18 05:00:37 localhost sshd[116493]: Invalid user ubuntu from 49.235.132.42 port 58442
Apr 18 05:00:37 localhost sshd[116493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.132.42
Apr 18 05:00:37 localhost sshd[116493]: Invalid user ubuntu from 49.235.132.42 port 58442
Apr 18 05:00:39 localhost sshd[116493]: Failed password for invalid user ubuntu from 49.235.132.42 port 58442 ssh2
Apr 18 05:06:06 localhost sshd[117106]: Invalid user admin from 49.235.132.42 port 34206
...
2020-04-18 13:07:34
222.173.242.30 attackbots
20 attempts against mh-ssh on echoip
2020-04-18 13:17:28
49.235.86.177 attackbots
$f2bV_matches
2020-04-18 13:15:01
106.54.95.232 attackbots
Apr 17 22:32:41 server1 sshd\[27203\]: Invalid user saned from 106.54.95.232
Apr 17 22:32:41 server1 sshd\[27203\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.95.232 
Apr 17 22:32:43 server1 sshd\[27203\]: Failed password for invalid user saned from 106.54.95.232 port 57978 ssh2
Apr 17 22:36:48 server1 sshd\[28450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.95.232  user=root
Apr 17 22:36:50 server1 sshd\[28450\]: Failed password for root from 106.54.95.232 port 45338 ssh2
...
2020-04-18 12:51:42
190.80.13.3 attack
Port probing on unauthorized port 1433
2020-04-18 12:56:11
222.186.52.139 attackspambots
04/18/2020-00:40:02.058132 222.186.52.139 Protocol: 6 ET SCAN Potential SSH Scan
2020-04-18 13:01:54
159.65.138.22 attackspam
2020-04-17T20:56:47.540544-07:00 suse-nuc sshd[29198]: Invalid user pulse from 159.65.138.22 port 58202
...
2020-04-18 13:29:31
95.165.160.46 attackbots
Apr 18 06:07:43 mail.srvfarm.net postfix/smtpd[3932546]: NOQUEUE: reject: RCPT from unknown[95.165.160.46]: 554 5.7.1 Service unavailable; Client host [95.165.160.46] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?95.165.160.46; from= to= proto=ESMTP helo=<95-165-160-46.static.spd-mgts.ru>
Apr 18 06:07:49 mail.srvfarm.net postfix/smtpd[3932546]: NOQUEUE: reject: RCPT from unknown[95.165.160.46]: 554 5.7.1 Service unavailable; Client host [95.165.160.46] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?95.165.160.46; from= to= proto=ESMTP helo=<95-165-160-46.static.spd-mgts.ru>
Apr 18 06:07:54 mail.srvfarm.net postfix/smtpd[3932546]: NOQUEUE: reject: RCPT from unknown[95.165.160.46]: 554 5.7.1 Service unavailable; Client host [95.165.160.46] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?95.165.160.46; from=
2020-04-18 13:04:46
165.227.58.61 attackspambots
Invalid user jet from 165.227.58.61 port 33420
2020-04-18 13:08:04
14.186.180.49 attack
Email SMTP authentication failure
2020-04-18 13:19:17

Recently Reported IPs

204.64.223.38 175.152.28.63 5.9.90.182 132.180.102.185
218.181.64.228 228.234.224.218 244.182.28.176 127.52.161.9
247.166.155.209 210.188.223.204 39.162.137.190 107.11.99.144
176.89.218.151 174.196.43.91 137.16.23.152 57.126.157.149
68.214.223.128 80.181.17.136 239.215.176.172 91.176.173.34