IP abuse report139.59.248.84

Critical Hosting / Datacenter IPv4 Singapore AS14061

139.59.248.84 is an IPv4 address located in Singapore (Pioneer), Singapore. It belongs to a network operated by DigitalOcean, LLC (AS14061). The address is listed by 4 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 4 Community Reports 1 How the score works
Listing sources4
Community Reports1
Distinct Reporters1
Last seen 19 minutes ago

IP Information

ISP / Organization
DigitalOcean, LLC
ASN
AS14061 DIGITALOCEAN-ASN
IP Range
139.59.0.0/17, 139.59.128.0/18, 139.59.192.0/19, 139.59.224.0/20, 139.59.240.0/21, 139.59.248.0/22, 139.59.252.0/23, 139.59.254.0/24, 139.59.255.0/25, 139.59.255.128/26, 139.59.255.192/27, 139.59.255.224/28, 139.59.255.240/29, 139.59.255.248/30, 139.59.255.252/31, 139.59.255.254/32
Regional Registry
APNIC
Connection Type
Hosting / Datacenter
Country
Singapore (SG)
Region / State
South West
City
Singapore (Pioneer)Local database
SingaporeLive service

The two sources report different cities. Neither is confirmed; the country is the reliable part.

Time Zone
Asia/Singapore
Abuse contact
noc@digitalocean.com The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Singapore (Pioneer) South West, Singapore
Coordinates
1.32, 103.69
Network
AS14061 DigitalOcean, LLC
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

139.59.248.0/24

2 of the 256 addresses in 139.59.248.0/24 are listed by our sources (0.8%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
139.59.248.201

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

4

In our pool since: 2026-11-18 17:47 (yesterday) · Last confirmed: 2026-11-20 03:19

Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator Single address 2026-11-19 21:57 2026-11-20 03:1820 minutes ago
Attack Source 2
SourceScopeFirst seenConfirmed
Blocklist.de (all) Single address 2026-11-18 17:47 2026-11-20 03:1721 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-18 18:18 2026-11-20 03:1919 minutes ago
Web Server Attack 1
SourceScopeFirst seenConfirmed
Blocklist.de Web/Apache Single address 2026-11-18 17:47 2026-11-20 03:1721 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 139.59.248.84 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 139.59.248.84 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 139.59.248.84 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 139.59.248.84 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. nak Registered member
    2 days ago 2026-11-17 15:46Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 7 requests (2 matched attack signatures) on 2026-11-17 11:38:44–11:38:45 UTC (1 s). Automated PHPMailer version scanner. Attack attempts: - PHPMailer version file probing [2 requests]: GET /vendor/phpmailer/phpmailer/VERSION, /PHPMailer/VERSION -> identifies vulnerable PHPMailer versions for targeted exploitation Signatures: ai-triage

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
yesterday
2026-11-18 17:52

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 139.59.248.84

Is 139.59.248.84 safe?

No. 139.59.248.84 scores 100/100 with strong, recent evidence of abuse (4 sources, 1 community report). Blocking it at your firewall is advisable.

Who owns 139.59.248.84?

139.59.248.84 is announced by AS14061 and operated by DigitalOcean, LLC. It sits in the 139.59.0.0/17, 139.59.128.0/18, 139.59.192.0/19, 139.59.224.0/20, 139.59.240.0/21, 139.59.248.0/22, 139.59.252.0/23, 139.59.254.0/24, 139.59.255.0/25, 139.59.255.128/26, 139.59.255.192/27, 139.59.255.224/28, 139.59.255.240/29, 139.59.255.248/30, 139.59.255.252/31, 139.59.255.254/32 block registered with APNIC.

Where is 139.59.248.84 located?

Geolocation places 139.59.248.84 in Singapore (Pioneer), Singapore. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 139.59.248.84 on a blacklist?

Yes. 139.59.248.84 is currently listed by 4 threat sources: Blocklist.de (all), Blocklist.de Web/Apache, FireHOL Level 2, Data-Shield IPv4 Blocklist.

How do I report abuse from 139.59.248.84?

Send your log lines to the network's abuse contact, noc@digitalocean.com, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/139.59.248.84

Guides for this IP