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

;; QUESTION SECTION:
;139.249.107.48.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 12 23:01:53 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 48.107.249.139.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.107.249.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.117.248.204 attackbots
23/tcp
[2019-08-02]1pkt
2019-08-02 12:28:25
107.170.201.213 attackspambots
5903/tcp 51465/tcp 135/tcp...
[2019-06-01/07-31]65pkt,53pt.(tcp),4pt.(udp)
2019-08-02 12:26:20
106.13.32.106 attack
Aug  2 01:31:07 Ubuntu-1404-trusty-64-minimal sshd\[11284\]: Invalid user fctrserver from 106.13.32.106
Aug  2 01:31:07 Ubuntu-1404-trusty-64-minimal sshd\[11284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.32.106
Aug  2 01:31:09 Ubuntu-1404-trusty-64-minimal sshd\[11284\]: Failed password for invalid user fctrserver from 106.13.32.106 port 33192 ssh2
Aug  2 01:36:01 Ubuntu-1404-trusty-64-minimal sshd\[12322\]: Invalid user radu from 106.13.32.106
Aug  2 01:36:01 Ubuntu-1404-trusty-64-minimal sshd\[12322\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.32.106
2019-08-02 12:39:37
119.27.165.134 attackbotsspam
2019-08-02T01:24:25.586153abusebot-5.cloudsearch.cf sshd\[17410\]: Invalid user mwang from 119.27.165.134 port 48153
2019-08-02 12:47:54
177.130.138.240 attack
SMTP-sasl brute force
...
2019-08-02 12:27:33
130.102.131.123 attackspambots
Port Scan: UDP/19
2019-08-02 12:49:16
162.247.73.192 attackbotsspam
Aug  2 04:19:38 ip-172-31-1-72 sshd\[30497\]: Invalid user eurek from 162.247.73.192
Aug  2 04:19:38 ip-172-31-1-72 sshd\[30497\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.73.192
Aug  2 04:19:41 ip-172-31-1-72 sshd\[30497\]: Failed password for invalid user eurek from 162.247.73.192 port 44192 ssh2
Aug  2 04:19:45 ip-172-31-1-72 sshd\[30499\]: Invalid user netscreen from 162.247.73.192
Aug  2 04:19:45 ip-172-31-1-72 sshd\[30499\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.73.192
2019-08-02 12:56:28
125.188.55.167 attack
DATE:2019-08-02 01:18:37, IP:125.188.55.167, PORT:1433 - MSSQL brute force auth on a honeypot server (epe-dc)
2019-08-02 12:43:04
180.250.111.17 attack
Aug  2 03:17:30 mout sshd[12951]: Invalid user fv from 180.250.111.17 port 41535
Aug  2 03:17:31 mout sshd[12951]: Failed password for invalid user fv from 180.250.111.17 port 41535 ssh2
Aug  2 03:17:31 mout sshd[12951]: Connection closed by 180.250.111.17 port 41535 [preauth]
2019-08-02 11:57:39
66.42.52.214 attackbotsspam
Aug  2 05:45:54 raspberrypi sshd\[2123\]: Invalid user dropbox from 66.42.52.214 port 58892
Aug  2 05:45:54 raspberrypi sshd\[2123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.42.52.214
Aug  2 05:45:56 raspberrypi sshd\[2123\]: Failed password for invalid user dropbox from 66.42.52.214 port 58892 ssh2
Aug  2 05:50:44 raspberrypi sshd\[2132\]: Invalid user gnuworld from 66.42.52.214 port 52236
Aug  2 05:50:45 raspberrypi sshd\[2132\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.42.52.214
...
2019-08-02 12:46:55
92.53.65.123 attackspam
08/01/2019-23:29:08.356135 92.53.65.123 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-02 11:44:47
176.31.250.171 attackbots
Aug  2 05:47:29 SilenceServices sshd[14407]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.250.171
Aug  2 05:47:31 SilenceServices sshd[14407]: Failed password for invalid user michey from 176.31.250.171 port 43785 ssh2
Aug  2 05:52:46 SilenceServices sshd[18567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.250.171
2019-08-02 11:56:19
201.33.229.91 attackbotsspam
$f2bV_matches
2019-08-02 12:47:22
117.50.49.74 attackbotsspam
$f2bV_matches
2019-08-02 12:43:31
88.99.145.83 attack
Only those who intend to destroy a site makes "all day" attempts like this below, so if this ip appears on your website block immediately 88.99.0.0/16 is high risk:

88.99.145.83/01/08/2019 02:23/error 403/GET/HTTP/1.1/9/
88.99.145.83/01/08/2019 12:33/9/error 403/GET/HTTP/1.1/
2019-08-02 11:46:31

Recently Reported IPs

174.164.74.199 143.181.122.240 18.122.41.49 21.177.28.72
213.26.223.76 120.236.152.88 56.68.164.111 126.142.66.36
223.9.185.34 93.77.138.23 108.46.220.200 188.32.247.46
185.70.84.150 178.61.164.89 222.191.27.105 209.200.49.9
5.8.42.175 59.64.160.216 245.1.68.32 18.42.48.106