The IP address 2.57.19.15/32 was categorized as Low Risk with a reputation score of 25. Ownership records identify the host as belonging to LABIXE LTD (ASN 204914, NL-LABIXE-04) within the RIPE registry in the Netherlands. Network analysis indicated the system functioned as a Single-Service Host with Remote Desktop Protocol (RDP) exposed on TCP port 3389.
Threat intelligence feeds found no association with known attackers, spam sources, or malicious campaigns. The IP was not identified as a Tor exit node or proxy. DNS analysis showed no forward resolution or PTR records, and email authentication protocols such as SPF and DMARC were absent. BGP data for the originating prefix 2.57.19.0/24 indicated route instability over the last 30 days, while DNSSEC validation remained valid. No blacklisting activity was recorded.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | LABIXE LTD |
| ASN | AS204914 |
| Network Name | NL-LABIXE-04 |
| CIDR Block | 2.57.19.0/24 |
| RIR | RIPE |
| Country | NL |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 3389 | rdp | tcp | — |
| Closed Ports | 22, 25, 80, 443, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS204914 |
| Network Prefix | 2.57.19.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 35% | 2 | 2 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 22% | 6 | 7 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-18 05:30:11 UTC |
| Last Seen | 2026-09-04 19:59:40 UTC |
| Profile Built | 2026-09-03 00:57:07 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 22 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 2.57.19.15
Who owns the IP address 2.57.19.15?
2.57.19.15 is registered to LABIXE LTD. The address falls within the 2.57.19.0/24 network block. Registration is held at RIPE.
Where is 2.57.19.15 located?
Geolocation data places 2.57.19.15 in New York. The local time zone is Europe/Amsterdam. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 2.57.19.15 malicious or safe?
2.57.19.15 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 2.57.19.15?
Responsive ports observed on 2.57.19.15 include 3389. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.