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

;; QUESTION SECTION:
;48.45.239.15.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 06:36:01 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 15.239.45.48.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 15.239.45.48.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
123.136.128.13 attackspambots
(sshd) Failed SSH login from 123.136.128.13 (IN/India/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jul 17 08:38:09 elude sshd[8082]: Invalid user developer from 123.136.128.13 port 55298
Jul 17 08:38:11 elude sshd[8082]: Failed password for invalid user developer from 123.136.128.13 port 55298 ssh2
Jul 17 08:45:10 elude sshd[9253]: Invalid user harry from 123.136.128.13 port 41768
Jul 17 08:45:12 elude sshd[9253]: Failed password for invalid user harry from 123.136.128.13 port 41768 ssh2
Jul 17 08:48:59 elude sshd[9848]: Invalid user postgres from 123.136.128.13 port 36355
2020-07-17 15:57:09
152.101.29.177 attackbots
Port scan denied
2020-07-17 15:23:17
51.255.35.58 attackspam
Jul 17 09:18:58 h1745522 sshd[10771]: Invalid user courtier from 51.255.35.58 port 54356
Jul 17 09:18:58 h1745522 sshd[10771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.35.58
Jul 17 09:18:58 h1745522 sshd[10771]: Invalid user courtier from 51.255.35.58 port 54356
Jul 17 09:19:00 h1745522 sshd[10771]: Failed password for invalid user courtier from 51.255.35.58 port 54356 ssh2
Jul 17 09:23:02 h1745522 sshd[11165]: Invalid user drcomadmin from 51.255.35.58 port 33441
Jul 17 09:23:02 h1745522 sshd[11165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.35.58
Jul 17 09:23:02 h1745522 sshd[11165]: Invalid user drcomadmin from 51.255.35.58 port 33441
Jul 17 09:23:05 h1745522 sshd[11165]: Failed password for invalid user drcomadmin from 51.255.35.58 port 33441 ssh2
Jul 17 09:27:10 h1745522 sshd[11487]: Invalid user Admin from 51.255.35.58 port 40759
...
2020-07-17 15:41:33
39.41.171.107 attack
C1,WP GET /wp-login.php
2020-07-17 16:02:01
89.248.167.141 attackbotsspam
Jul 17 08:53:03 debian-2gb-nbg1-2 kernel: \[17227339.472425\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.167.141 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=50860 PROTO=TCP SPT=8080 DPT=4502 WINDOW=1024 RES=0x00 SYN URGP=0
2020-07-17 15:33:56
196.52.84.39 attackbotsspam
0,27-02/04 [bc01/m09] PostRequest-Spammer scoring: harare01
2020-07-17 15:58:11
45.80.65.82 attackspam
(sshd) Failed SSH login from 45.80.65.82 (RU/Russia/-): 5 in the last 3600 secs
2020-07-17 15:43:41
141.98.81.133 attackbots
*Port Scan* detected from 141.98.81.133 (NL/Netherlands/South Holland/Dordrecht/-). 4 hits in the last 95 seconds
2020-07-17 15:44:53
104.248.119.77 attackbotsspam
Jul 17 05:51:46 gospond sshd[13972]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.119.77 
Jul 17 05:51:46 gospond sshd[13972]: Invalid user pare from 104.248.119.77 port 37126
Jul 17 05:51:48 gospond sshd[13972]: Failed password for invalid user pare from 104.248.119.77 port 37126 ssh2
...
2020-07-17 15:52:58
134.175.19.39 attack
SSH Brute-Force reported by Fail2Ban
2020-07-17 15:58:31
144.76.38.40 attackbots
Automatic report - Banned IP Access
2020-07-17 15:27:42
91.240.118.64 attack
07/17/2020-03:33:39.242235 91.240.118.64 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-07-17 15:43:13
177.0.23.37 attackbotsspam
2020-07-17T08:59:05.268004ks3355764 sshd[8125]: Invalid user montse from 177.0.23.37 port 41256
2020-07-17T08:59:07.173158ks3355764 sshd[8125]: Failed password for invalid user montse from 177.0.23.37 port 41256 ssh2
...
2020-07-17 15:28:52
93.99.133.243 attack
(smtpauth) Failed SMTP AUTH login from 93.99.133.243 (CZ/Czechia/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-07-17 08:24:49 plain authenticator failed for ([93.99.133.243]) [93.99.133.243]: 535 Incorrect authentication data (set_id=dairy@pishgamds.com)
2020-07-17 16:00:40
121.126.37.150 attackspam
$f2bV_matches
2020-07-17 15:41:05

Recently Reported IPs

83.210.13.154 40.47.27.239 124.164.43.196 214.51.52.91
24.233.90.125 87.175.213.243 90.225.115.83 241.233.75.100
81.85.122.47 2.134.173.62 172.27.35.1 240.125.17.219
74.49.206.29 64.173.155.80 176.142.183.43 181.40.149.50
245.121.130.75 22.64.212.75 56.210.194.241 214.234.63.0