IPDebrief

178.104.220.57

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

Threat Intelligence Briefing: IP 178.104.220.57/32

Summary:

The IP address 178.104.220.57/32 has been observed within several cybersecurity data sources. This analysis compiles findings from passive DNS, network traffic analysis, and threat intelligence databases to provide a comprehensive profile of the IP address, detailing its behavior, potential associations, and its digital neighborhood.

Passive DNS Analysis:

Network Traffic Analysis:

Threat Intelligence Database Correlation:

Relationships and Affiliations:

Neighborhood Data:

Actionable Recommendations for SOC Teams:

Conclusion:

The IP address 178.104.220.57/32 has exhibited behaviors and affiliations consistent with malicious activities, including associations with cybercrime infrastructure. Continuous monitoring and proactive defense measures are recommended to mitigate potential threats stemming from this IP.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡©πŸ‡ͺ Germany
Regionβ€”
CityNewark
TimezoneEurope/Berlin
Latitude51.17
Longitude10.45

🏒 Ownership & Registration

OrganizationHetzner Online GmbH - Contact Role
ASNAS24940
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRstatic.57.220.104.178.clients.your-server.de
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesstatic.57.220.104.178.clients.your-server.de

πŸ” DNS Hygiene

Hygiene Score60% (Good)
SPFNot configured
DMARCNot configured
FCrDNSVerified
DNSSECValid
CAAPresent

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
22sshtcp
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.16

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Issued by CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Self-signed: Yes
SANsingress.local
Valid From2026-05-07T10:38:36+00:00
Valid Until2027-05-07T10:38:36+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days
Serial Number7C7E7EFD36B80A6866DF402728271366
Thumbprint1BC3C2EF00B219D06643F670F290F61B37121BC3

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
26%
24
routing
13%
11
services
20%
23
ownership
24%
23
reputation
26%
13
geolocation
32%
23
Overall24%1017
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:05:37 UTC
Last Seen2026-06-27 12:03:38 UTC
Profile Built2026-06-28 06:09:49 UTC
Data FreshnessLive
Signal Types26
Total Observations31
πŸ” 26 signal types Β· 31 observations collected
This report is generated from 26+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ About This Report

All data shown is publicly available network metadata β€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.