IPDebrief

193.176.211.30

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.

IP Intelligence Briefing: 193.176.211.30

Date: 2026-06-02

---

**1. Core Profile**

---

**2. Subnet Analysis**

- 78 IPs with Medium Risk (score 25–40).

- 2 IPs with Low Risk.

- 75 IPs in the subnet show potential threat activity.

---

**3. Behavioral Observations**

---

**4. Threat Context**

---

**5. Recommended Actions**

1. Monitor Subnet: Track traffic from 193.176.211.0/24 due to high abuse density.

2. Block IP: Consider blocking 193.176.211.30 if it persists in scans or connects to internal assets.

3. Investigate Neighbors: Focus on high-risk IPs in the subnet (e.g., 193.176.211.27–29).

4. Verify DNS: Confirm no DNS misconfigurations or spoofing in the subnet.

---

**6. Summary**

The IP is part of a high-risk subnet linked to a VPN provider. While no direct threats are detected, the subnet’s abuse density and potential for compromised hosts warrant close monitoring. SOC teams should prioritize isolating this subnet and verifying traffic patterns.

Tools Used: `ipdebrief_profile`, `ipdebrief_history`, `ipdebrief_relationships`, `ipdebrief_neighbors`, `ipdebrief_actions`.

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

🌍 Geolocation

CountryπŸ‡­πŸ‡° Hong Kong
RegionHCW
CityCentral
TimezoneAsia/Hong_Kong
Latitude22.40
Longitude114.11

🏒 Ownership & Registration

OrganizationVPN Consumer Hong Kong
ASNAS206092
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
26%
24
routing
13%
11
services
15%
22
ownership
24%
23
reputation
26%
13
geolocation
32%
23
Overall23%1016
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:04 UTC
Last Seen2026-06-23 02:52:29 UTC
Profile Built2026-06-23 03:00:16 UTC
Data FreshnessLive
Signal Types20
Total Observations21
πŸ” 20 signal types Β· 21 observations collected
This report is generated from 20+ 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.