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

;; QUESTION SECTION:
;148.27.157.45.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 13:01:42 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 45.157.27.148.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.157.27.148.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
37.49.231.121 attack
02/21/2020-19:53:19.708734 37.49.231.121 Protocol: 17 ET CINS Active Threat Intelligence Poor Reputation IP group 35
2020-02-22 03:16:14
113.31.98.20 attack
Invalid user news from 113.31.98.20 port 43902
2020-02-22 02:54:48
118.32.108.78 attackbots
firewall-block, port(s): 8000/tcp
2020-02-22 03:06:42
181.49.47.190 attack
Automatic report - Port Scan Attack
2020-02-22 03:24:41
200.117.27.82 attackspambots
firewall-block, port(s): 23/tcp
2020-02-22 03:04:54
103.92.225.43 attackspam
Unauthorized connection attempt from IP address 103.92.225.43 on Port 445(SMB)
2020-02-22 03:06:55
197.50.51.179 attackbots
Automatic report - Port Scan Attack
2020-02-22 03:25:40
170.84.48.82 attackbots
Unauthorized connection attempt from IP address 170.84.48.82 on Port 445(SMB)
2020-02-22 03:12:03
122.51.191.69 attackspambots
(sshd) Failed SSH login from 122.51.191.69 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 21 15:31:35 elude sshd[22669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.191.69  user=root
Feb 21 15:31:38 elude sshd[22669]: Failed password for root from 122.51.191.69 port 47708 ssh2
Feb 21 15:53:31 elude sshd[23974]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.191.69  user=news
Feb 21 15:53:33 elude sshd[23974]: Failed password for news from 122.51.191.69 port 57732 ssh2
Feb 21 15:57:51 elude sshd[24205]: Invalid user lisha from 122.51.191.69 port 50772
2020-02-22 03:08:35
54.36.189.198 attackspambots
Feb 21 17:26:04 vps647732 sshd[26424]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.198
Feb 21 17:26:07 vps647732 sshd[26424]: Failed password for invalid user carol from 54.36.189.198 port 64778 ssh2
...
2020-02-22 03:35:13
180.250.140.74 attack
Feb 21 14:08:48 web8 sshd\[7496\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.140.74  user=sys
Feb 21 14:08:50 web8 sshd\[7496\]: Failed password for sys from 180.250.140.74 port 47422 ssh2
Feb 21 14:11:13 web8 sshd\[9110\]: Invalid user gitlab-runner from 180.250.140.74
Feb 21 14:11:13 web8 sshd\[9110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.250.140.74
Feb 21 14:11:14 web8 sshd\[9110\]: Failed password for invalid user gitlab-runner from 180.250.140.74 port 34956 ssh2
2020-02-22 03:15:41
192.3.143.79 attackbotsspam
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - fpchiro.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across fpchiro.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your site.

CLI
2020-02-22 03:06:01
171.239.152.152 attackspambots
20/2/21@08:13:12: FAIL: IoT-Telnet address from=171.239.152.152
...
2020-02-22 02:58:42
123.24.160.70 attack
proto=tcp  .  spt=44076  .  dpt=25  .     Found on   Blocklist de       (243)
2020-02-22 02:55:36
103.100.209.228 attack
Feb 21 16:27:25 srv01 sshd[5424]: Invalid user moodle from 103.100.209.228 port 45079
Feb 21 16:27:25 srv01 sshd[5424]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.100.209.228
Feb 21 16:27:25 srv01 sshd[5424]: Invalid user moodle from 103.100.209.228 port 45079
Feb 21 16:27:27 srv01 sshd[5424]: Failed password for invalid user moodle from 103.100.209.228 port 45079 ssh2
Feb 21 16:29:57 srv01 sshd[5616]: Invalid user cloud from 103.100.209.228 port 56557
...
2020-02-22 03:21:13

Recently Reported IPs

80.145.1.15 50.61.119.40 61.211.66.32 204.73.180.250
223.209.192.27 174.234.0.161 40.240.161.143 172.91.60.156
20.85.221.220 226.250.25.129 113.96.112.196 33.37.219.241
140.186.181.222 96.175.124.172 61.21.249.32 184.150.66.56
63.117.29.34 141.131.160.78 101.229.43.213 61.229.162.83