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

;; QUESTION SECTION:
;108.54.240.45.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 23:16:52 CST 2025
;; MSG SIZE  rcvd: 106
Host info
45.240.54.108.in-addr.arpa domain name pointer pool-108-54-240-45.nycmny.fios.verizon.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.240.54.108.in-addr.arpa	name = pool-108-54-240-45.nycmny.fios.verizon.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.248.126.170 attackbotsspam
Jan 24 17:44:35 sd-53420 sshd\[14031\]: User root from 104.248.126.170 not allowed because none of user's groups are listed in AllowGroups
Jan 24 17:44:35 sd-53420 sshd\[14031\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.126.170  user=root
Jan 24 17:44:36 sd-53420 sshd\[14031\]: Failed password for invalid user root from 104.248.126.170 port 43922 ssh2
Jan 24 17:49:07 sd-53420 sshd\[15131\]: Invalid user cms from 104.248.126.170
Jan 24 17:49:07 sd-53420 sshd\[15131\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.126.170
...
2020-01-25 01:11:12
40.117.125.206 attack
Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2020-01-25 01:07:39
193.242.149.16 attackspam
20/1/24@07:34:40: FAIL: Alarm-Network address from=193.242.149.16
20/1/24@07:34:41: FAIL: Alarm-Network address from=193.242.149.16
...
2020-01-25 01:16:55
51.91.136.174 attackspambots
SIP/5060 Probe, BF, Hack -
2020-01-25 01:05:42
111.252.151.216 attack
Unauthorized connection attempt from IP address 111.252.151.216 on Port 445(SMB)
2020-01-25 01:03:53
117.205.238.149 attackbots
Unauthorized connection attempt from IP address 117.205.238.149 on Port 445(SMB)
2020-01-25 00:59:02
222.186.30.31 attackbots
2020-01-24T10:27:03.270488homeassistant sshd[10573]: Failed password for root from 222.186.30.31 port 16514 ssh2
2020-01-24T17:11:32.195424homeassistant sshd[14492]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.31  user=root
...
2020-01-25 01:19:11
150.129.5.98 attack
Unauthorized connection attempt from IP address 150.129.5.98 on Port 445(SMB)
2020-01-25 01:20:01
178.33.175.19 attackspam
Unauthorized connection attempt detected from IP address 178.33.175.19 to port 1433 [J]
2020-01-25 01:23:30
122.179.159.7 attackbotsspam
Unauthorized connection attempt from IP address 122.179.159.7 on Port 445(SMB)
2020-01-25 00:51:02
171.255.170.35 attack
445/tcp 445/tcp
[2020-01-24]2pkt
2020-01-25 00:50:37
31.148.168.12 attackspambots
Unauthorized connection attempt from IP address 31.148.168.12 on Port 445(SMB)
2020-01-25 01:13:31
114.30.57.254 attack
Telnet/23 MH Probe, BF, Hack -
2020-01-25 01:05:20
114.119.151.197 attackspam
badbot
2020-01-25 00:43:47
89.136.226.182 attackbotsspam
Automatic report - Port Scan Attack
2020-01-25 01:06:00

Recently Reported IPs

8.174.173.244 50.54.166.57 233.203.59.197 19.238.64.109
179.97.230.234 6.244.136.173 77.219.1.97 54.230.45.26
188.122.156.247 58.69.41.34 12.244.63.133 137.140.189.70
71.26.73.120 127.134.159.191 233.152.251.237 243.105.139.50
120.189.154.215 54.9.107.39 138.35.23.233 82.188.56.190