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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;155.9.140.48.			IN	A

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

;; Query time: 81 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 19 19:12:39 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 48.140.9.155.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 48.140.9.155.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.41.154 attack
Nov 24 08:08:19 *** sshd[10025]: Invalid user myrle from 139.59.41.154
2019-11-24 20:04:39
80.82.64.127 attack
UTC: 2019-11-23 port: 1000/tcp
2019-11-24 19:32:21
112.85.42.176 attackspambots
112.85.42.176 was recorded 5 times by 5 hosts attempting to connect to the following ports: 22. Incident counter (4h, 24h, all-time): 5, 36, 390
2019-11-24 19:57:33
51.77.230.125 attackbotsspam
2019-11-24T08:26:49.184447abusebot-4.cloudsearch.cf sshd\[13403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.ip-51-77-230.eu  user=root
2019-11-24 19:42:21
91.185.193.101 attack
Brute-force attempt banned
2019-11-24 19:34:03
106.13.32.56 attackspam
2019-11-24T11:59:44.688419abusebot.cloudsearch.cf sshd\[1711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.32.56  user=root
2019-11-24 20:15:04
185.4.132.183 attack
fail2ban honeypot
2019-11-24 20:08:24
192.99.86.53 attackbotsspam
192.99.86.53 was recorded 8 times by 2 hosts attempting to connect to the following ports: 1433. Incident counter (4h, 24h, all-time): 8, 66, 320
2019-11-24 20:06:26
220.158.148.132 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.158.148.132  user=root
Failed password for root from 220.158.148.132 port 58050 ssh2
Invalid user widder from 220.158.148.132 port 37184
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.158.148.132
Failed password for invalid user widder from 220.158.148.132 port 37184 ssh2
2019-11-24 20:09:59
68.183.160.63 attackspam
2019-11-24T11:26:04.951974shield sshd\[15071\]: Invalid user lll from 68.183.160.63 port 44936
2019-11-24T11:26:04.956223shield sshd\[15071\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.160.63
2019-11-24T11:26:06.854899shield sshd\[15071\]: Failed password for invalid user lll from 68.183.160.63 port 44936 ssh2
2019-11-24T11:31:55.344957shield sshd\[16483\]: Invalid user sadfad from 68.183.160.63 port 60854
2019-11-24T11:31:55.349042shield sshd\[16483\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.160.63
2019-11-24 19:44:28
31.147.204.65 attackbots
Nov 24 02:32:36 linuxvps sshd\[9727\]: Invalid user 123450 from 31.147.204.65
Nov 24 02:32:36 linuxvps sshd\[9727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.147.204.65
Nov 24 02:32:38 linuxvps sshd\[9727\]: Failed password for invalid user 123450 from 31.147.204.65 port 40359 ssh2
Nov 24 02:39:08 linuxvps sshd\[13790\]: Invalid user 01234 from 31.147.204.65
Nov 24 02:39:08 linuxvps sshd\[13790\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.147.204.65
2019-11-24 19:58:33
1.55.6.162 attack
Fail2Ban Ban Triggered
2019-11-24 19:37:25
128.199.142.138 attackbots
Nov 24 02:07:40 ny01 sshd[23028]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
Nov 24 02:07:42 ny01 sshd[23028]: Failed password for invalid user miami from 128.199.142.138 port 45614 ssh2
Nov 24 02:12:12 ny01 sshd[23449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
2019-11-24 20:10:46
45.138.100.233 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/45.138.100.233/ 
 
 FI - 1H : (3)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : FI 
 NAME ASN : ASN0 
 
 IP : 45.138.100.233 
 
 CIDR : 45.138.100.0/22 
 
 PREFIX COUNT : 50242 
 
 UNIQUE IP COUNT : 856039856 
 
 
 ATTACKS DETECTED ASN0 :  
  1H - 4 
  3H - 7 
  6H - 8 
 12H - 9 
 24H - 17 
 
 DateTime : 2019-11-24 07:21:11 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-11-24 19:53:29
104.221.147.34 attackbots
Port 1433 Scan
2019-11-24 19:43:36

Recently Reported IPs

16.17.168.4 95.67.200.199 171.37.129.144 10.211.175.163
0.176.199.231 214.138.166.72 235.254.234.42 168.145.206.138
95.38.16.182 181.234.164.118 185.188.62.235 92.246.85.232
74.196.50.218 223.133.79.72 20.200.211.138 195.230.155.143
169.203.13.145 90.91.198.9 34.110.5.5 32.89.18.166