193.202.11.112
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 193.202.11.112
Date: 2026-06-08
---
**1. Risk Profile**
- Risk Score: 50 (Moderate Risk)
- Ownership: Registered to ALB-MNT (ASN 215540, RIPE).
- Geolocation: Claimed location in Israel (31.5°N, 34.75°E), but geo validation fails (RTT discrepancy, plausible location mismatch).
- Network Role: Web server (ports 80, 443, 22 open).
- TLS Certificate: Self-signed, issued to "parking" (likely misconfigured or non-standard).
---
**2. Threat Indicators**
- No direct malicious activity detected (no indicators, blacklists, or campaigns).
- RTT Anomalies: Observed 36ms RTT (minimum possible for 3252km distance: 65ms), suggesting potential spoofing or misconfigured routing.
- DNSSEC/CAA: Valid DNSSEC and CAA records present.
---
**3. Network Relationships**
- Subnet: 193.202.11.0/24 (no neighboring IPs found).
- Shared Network: Linked to GCS_SER-NET (likely a hosting provider network).
- Abuse Density: 0% (subnet classified as "mostly clean").
---
**4. Historical Observations**
- Recent Activity (30d):
- 1 RTT violation (geo plausibility failure).
- 23 total observations (mix of routing, DNS, and geolocation signals).
- No persistent malicious behavior detected.
---
**5. Recommended Actions**
- Verify Geolocation: Investigate RTT anomalies and geo plausibility mismatch.
- Audit TLS Configuration: Self-signed certificate may indicate misconfiguration or non-standard use.
- Monitor Traffic: Track unusual traffic patterns or unexpected port activity.
- Firewall Rules (Example):
- `iptables -A INPUT -s 193.202.11.112 -j DROP`
- AWS WAF: Block IP with rule `{"Addresses":["193.202.11.112/32"], "Description":"IPDebrief risk 50"}`
---
Conclusion:
The IP appears to be a misconfigured web server with no direct malicious activity. The geo validation issues and RTT anomalies warrant further investigation to rule out spoofing or network misconfiguration. No immediate mitigation is required, but continuous monitoring is advised.
Source: IPDebrief Threat Intelligence Platform
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | ALB-MNT |
| ASN | AS215540 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| Country | — |
| 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 | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | — |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | nginx/1.30.1 |
| HTTP Title | — |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=parking, OU="", O=FASTPANEL, L="", S="", C=""
Issued by CN=parking, OU="", O=FASTPANEL, L="", S="", C=""
Self-signed: Yes
| SANs | None |
| Valid From | 2026-05-17T22:44:15+00:00 |
| Valid Until | 2027-05-17T22:44:15+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
| Serial Number | 01 |
| Thumbprint | 560013DDB056B2844B853CE35C47DA4BB3B3D8FE |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 31% | 2 | 4 |
| ownership | 27% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 13% | 1 | 1 |
| Overall | 24% | 9 | 16 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Contradictory (48%) — 3 contradiction(s) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
⚠ Geo sources disagree on country: RU, IL, ""
⚠ TLS certificate claims "" but primary geo says IL
⚠ Geo sources disagree on country: RU, IL, ""
⚠ TLS certificate claims "" but primary geo says IL
📅 Observation Timeline 🔄 Fresh
| First Seen | 2026-05-17 03:08:12 UTC |
| Last Seen | 2026-06-26 18:10:59 UTC |
| Profile Built | 2026-06-26 10:15:20 UTC |
| Data Freshness | Fresh |
| Signal Types | 24 |
| Total Observations | 25 |
🔍 24 signal types · 25 observations collected
This report is generated from 24+ 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.
Full dossier details are available via our API.
ℹ️ 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.