IPDebrief

95.0.32.102

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

Date: 2026-06-08

---

**1. Risk Profile**

---

**2. Network Role & Infrastructure**

---

**3. Threat & DNS Context**

- Resolves to `95.0.32.102.static.ttnet.com.tr` (Turk Telekom).

- No malicious domains or email authentication records (SPF/DKIM).

- Stable ownership since 2008.

- No persistent malicious activity detected in 30-day history.

---

**4. Key Red Flags**

---

**5. Recommended Actions**

1. Monitor Subnet: Investigate high-risk neighbors (e.g., 95.0.32.43, 95.0.32.144) for anomalous traffic.

2. Verify Geolocation: Confirm if the IP’s Netherlands registration is legitimate or spoofed.

3. Block/Restrict: Apply firewall rules to block traffic from this subnet if it aligns with known malicious patterns.

4. Check for Anomalies: Use SIEM tools to detect unusual DNS queries or TLS handshakes from this IP.

---

Note: No immediate action required for 95.0.32.102 itself, but its subnet’s elevated risk warrants closer scrutiny.

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

🌍 Geolocation

CountryπŸ‡³πŸ‡± Netherlands
RegionZonguldak Province
CityAmsterdam
TimezoneEurope/Amsterdam
Latitude41.27
Longitude31.73

🏒 Ownership & Registration

OrganizationAS9121-MNT
ASNAS9121
Network NameKKTC_TELEKOM_IDARESI_XREAL_NET_LTD
CIDR Block95.0.32.0/24
RIRRIPE
CountryTR
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR95.0.32.102.static.ttnet.com.tr
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnames95.0.32.102.static.ttnet.com.tr

πŸ” DNS Hygiene

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

☁️ Network Classification

InfrastructureMobile
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
Mobile

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
13%
11
routing
13%
11
services
13%
11
ownership
30%
23
reputation
0%
00
geolocation
17%
11
Overall14%67
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: TR, NL

πŸ“… Observation Timeline πŸ”„ Recent

First Seen2026-05-19 15:39:43 UTC
Last Seen2026-06-16 00:09:50 UTC
Profile Built2026-06-14 02:00:58 UTC
Data FreshnessRecent
Signal Types21
Total Observations21
πŸ” 21 signal types Β· 21 observations collected
This report is generated from 21+ 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.