IPDebrief

103.171.69.104

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: 103.171.69.104

Date: 2026-06-17

---

**1. Core Profile**

- BGP prefix: `103.171.69.0/24`

- DNSSEC valid; no route stability issues.

---

**2. Observation History**

- Reputed as low-risk with 13 pulse signals (e.g., "nested data omitted").

- First observed June 2, 2026, with mixed network classification (abuse density: 0.3462).

- No persistent malicious behavior or threat persistence.

---

**3. Relationships & Network Context**

- Total IPs: 61 (52 siblings in /24).

- Risk Distribution: 9 medium-risk, 49 low-risk, 0 high-risk.

- Abuse Density: 34.6% (moderate risk within subnet).

---

**4. Actionable Insights**

- Allow traffic only if necessary, given the low-risk profile.

- Consider blocking high-risk neighbors in the subnet.

---

Conclusion: 103.171.69.104 is currently low-risk but resides in a subnet with moderate abuse density. Historical data suggests no active threats, but ongoing monitoring is advised.

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

🌍 Geolocation

CountryπŸ‡§πŸ‡© Bangladesh
Regionβ€”
Cityβ€”
Timezoneβ€”
Latitude23.70
Longitude90.37

🏒 Ownership & Registration

OrganizationMultilink International
ASNAS142627
Network Nameβ€”
CIDR Blockβ€”
RIRAPNIC
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
29%
24
routing
13%
11
services
15%
22
ownership
27%
23
reputation
26%
13
geolocation
13%
11
Overall21%914
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:03:26 UTC
Last Seen2026-06-26 18:10:14 UTC
Profile Built2026-06-22 06:38:53 UTC
Data FreshnessLive
Signal Types18
Total Observations19
πŸ” 18 signal types Β· 19 observations collected
This report is generated from 18+ 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.