IP abuse report77.83.39.6

Critical Residential IPv4 The Netherlands AS43109

77.83.39.6 is an IPv4 address located in Amsterdam (Amsterdam-Zuidoost), The Netherlands. It belongs to a network operated by Pitline Ltd (AS43109). The address is listed by 6 of the threat-intelligence sources we track and carries a confidence score of 100/100. No community reports have been filed for it yet.

Last updated Listing sources 4 Community Reports 0 How the score works
Listing sources4
Community Reports0
Distinct Reporters0
Last seen 15 minutes ago

IP Information

ISP / Organization
Pitline Ltd
ASN
AS43109 CUSTOMER-AS
ASN Domain
pitline.net
IP Range
Unknown
Regional Registry
NONE
Connection Type
Residential
Country
The Netherlands (NL)
Region / State
North Holland
City
Amsterdam (Amsterdam-Zuidoost)
Time Zone
Unknown

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

Approximate location

City level
Amsterdam (Amsterdam-Zuidoost) North Holland, The Netherlands
Coordinates
52.34, 4.87
Network
AS43109 Pitline Ltd
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

77.83.39.0/24

138 of the 256 addresses in 77.83.39.0/24 are listed by our sources (53.9%).

Most of the block is listed. That points to a network being run for the purpose rather than one compromised machine — consider blocking at the block level instead of the single address.

Examples from the same block
77.83.39.277.83.39.377.83.39.477.83.39.577.83.39.877.83.39.977.83.39.1077.83.39.11

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

Blacklist Matches

6

In our pool since: 2026-11-11 09:18 (8 days ago) · Last confirmed: 2026-11-20 05:48

Aggregated List (High Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 1 Aggregator 77.83.36.0/22 2026-11-07 19:33 2026-11-20 05:4815 minutes ago
Hijacked Network 2
SourceScopeFirst seenConfirmed
Spamhaus DROP 77.83.36.0/22 2026-11-08 04:47 2026-11-19 09:1720 hours ago
Spamhaus DROP 77.83.39.0/24 2026-11-08 04:47 2026-11-19 09:1720 hours ago
Malicious Activity 3
SourceScopeFirst seenConfirmed
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-11 09:18 2026-11-20 05:4815 minutes ago
Emerging Threats Block IPs 77.83.36.0/22 2026-11-07 19:32 2026-11-20 05:4716 minutes ago
Emerging Threats Block IPs 77.83.39.0/24 2026-11-07 19:32 2026-11-20 05:4716 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 77.83.39.6 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 77.83.39.6 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 77.83.39.6 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 77.83.39.6 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 0

Report This IP

No community reports yet for this IP.

Report This IP

Listing History

9
Added to the pool
8 days ago
2026-11-11 09:22
Removed from the pool
8 days ago · score at the time: 45/100 · carried by 1 sources
2026-11-11 08:22
Added to the pool
9 days ago
2026-11-10 09:22
Removed from the pool
9 days ago · score at the time: 45/100 · carried by 1 sources
2026-11-10 08:52
Added to the pool
10 days ago
2026-11-09 09:52
Removed from the pool
10 days ago · score at the time: 45/100 · carried by 1 sources
2026-11-09 08:52
Added to the pool
1 month ago
2026-10-16 17:22
Removed from the pool
1 month ago · score at the time: 50/100 · carried by 1 sources
2026-10-16 11:22
Added to the pool
2 months ago · score at the time: 90/100 · carried by 2 sources
2026-08-29 07:47

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 77.83.39.6

Is 77.83.39.6 safe?

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

Who owns 77.83.39.6?

77.83.39.6 is announced by AS43109 and operated by Pitline Ltd.

Where is 77.83.39.6 located?

Geolocation places 77.83.39.6 in Amsterdam (Amsterdam-Zuidoost), The Netherlands. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 77.83.39.6 on a blacklist?

Yes. 77.83.39.6 is currently listed by 4 threat sources: Malicious IP (romainmarcoux), Spamhaus DROP, Emerging Threats Block IPs, FireHOL Level 1.

How do I report abuse from 77.83.39.6?

File a report on IP-DB with your log lines; the registry publishes no abuse mailbox for this network.

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/77.83.39.6

Guides for this IP