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

;; QUESTION SECTION:
;162.140.230.44.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 15:36:08 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 44.230.140.162.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 44.230.140.162.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
196.52.43.125 attackbotsspam
Jun  9 19:44:44 debian-2gb-nbg1-2 kernel: \[13983418.155921\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=196.52.43.125 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=244 ID=59163 PROTO=TCP SPT=63564 DPT=8531 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-10 02:45:00
209.95.51.11 attackbots
(sshd) Failed SSH login from 209.95.51.11 (US/United States/nyc-exit.privateinternetaccess.com): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun  9 16:22:44 ubnt-55d23 sshd[10893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.95.51.11  user=root
Jun  9 16:22:46 ubnt-55d23 sshd[10893]: Failed password for root from 209.95.51.11 port 60304 ssh2
2020-06-10 02:37:07
190.197.64.49 attackbotsspam
Email server abuse
2020-06-10 02:59:29
43.250.81.54 attack
Unauthorized connection attempt from IP address 43.250.81.54 on Port 445(SMB)
2020-06-10 02:40:01
117.201.97.14 attackbots
Unauthorized connection attempt from IP address 117.201.97.14 on Port 445(SMB)
2020-06-10 02:56:14
113.160.117.14 attackbotsspam
Unauthorized connection attempt from IP address 113.160.117.14 on Port 445(SMB)
2020-06-10 02:31:24
14.186.72.180 attackbotsspam
Unauthorized connection attempt from IP address 14.186.72.180 on Port 445(SMB)
2020-06-10 02:47:26
115.84.91.101 attack
(imapd) Failed IMAP login from 115.84.91.101 (LA/Laos/-): 1 in the last 3600 secs
2020-06-10 02:51:56
120.196.120.110 attack
Jun  9 18:15:51 mail sshd[25380]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.196.120.110 
Jun  9 18:15:53 mail sshd[25380]: Failed password for invalid user zabbix from 120.196.120.110 port 2152 ssh2
...
2020-06-10 02:57:17
112.85.42.232 attackbots
Jun  9 20:33:03 home sshd[22525]: Failed password for root from 112.85.42.232 port 24964 ssh2
Jun  9 20:33:05 home sshd[22525]: Failed password for root from 112.85.42.232 port 24964 ssh2
Jun  9 20:33:07 home sshd[22525]: Failed password for root from 112.85.42.232 port 24964 ssh2
...
2020-06-10 02:49:12
210.97.40.34 attack
SSH brute-force: detected 6 distinct username(s) / 15 distinct password(s) within a 24-hour window.
2020-06-10 02:24:03
46.142.14.52 attackspam
User [zhangrd] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [root] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [deepmagic] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [teamspeakbot] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [ihor] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [root] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [admin] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [admin] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [yuchen] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [root] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
User [user3] from [46.142.14.52] failed to log in via [SSH] due to authorization failure.
2020-06-10 02:54:15
39.53.200.109 attackbotsspam
39.53.200.109 - - [09/Jun/2020:13:57:48 +0200] "POST /xmlrpc.php HTTP/1.1" 301 162 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
39.53.200.109 - - [09/Jun/2020:14:02:41 +0200] "POST /xmlrpc.php HTTP/1.1" 301 162 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
...
2020-06-10 02:33:28
45.6.72.17 attackbots
Jun  9 14:00:19 ns381471 sshd[24585]: Failed password for root from 45.6.72.17 port 52278 ssh2
Jun  9 14:02:48 ns381471 sshd[24688]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.6.72.17
2020-06-10 02:29:17
217.131.158.17 attackbots
Port Scan detected!
...
2020-06-10 02:31:39

Recently Reported IPs

101.212.86.242 240.255.46.17 217.175.97.39 126.109.222.157
126.197.7.77 68.73.119.241 81.56.61.127 97.108.161.115
74.16.207.110 59.195.66.143 69.6.199.60 86.90.227.217
164.197.14.161 108.76.69.202 157.31.26.211 158.114.225.223
229.92.59.77 163.195.14.89 29.60.241.172 191.91.94.99