212.47.252.101
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: 212.47.252.101/32
Date: June 14, 2026
---
**1. Core Profile**
- Risk Score: 50 (Moderate Risk)
- Provider: Scaleway (CloudCompute)
- Geolocation: Paris, France (Ele-de-France region)
- Ownership: MNT-TISCALIFR (RIPE-registrant)
- Network Role: Hosting/Web Server (Nginx, HTTPS/HTTP services)
- Threat Indicators: None detected (no malware, spam, or known attacker associations).
---
**2. Network & Infrastructure**
- Subnet: 212.47.252.101/24 (abuse density: 0.5, classified as "mostly_clean").
- Neighbors: 1 active sibling IP (212.47.252.162) with a risk score of 25.
- Cloud Provider: Scaleway (Paris region), likely a virtual private server (VPS) or container.
- Services:
- Open ports: 80 (HTTP), 443 (HTTPS).
- TLS certificate: Issued to `lic01.par1.scw-prod.arkmap.net` (Scaleway domain).
- Server banner: Nginx.
---
**3. Threat & Risk Trends**
- Observation History (30-day window):
- Minimal risk scores (operator score: 0.13) consistently recorded.
- No spikes in threat signals, DNS anomalies, or geo-plausibility violations.
- Abuse Confidence: 0 (no blacklisted or malicious activity).
- BGP & Routing: Stable route (no recent changes), valid DNSSEC, and RPKI compliance.
---
**4. Relationships & Context**
- Linked Entities:
- Subnet: `SCALEWAY-PAR1` (Scaleway's Paris cloud network).
- Certificates: Issued to Scaleway-managed domains.
- DNS: Resolves to `101-252-47-212.instances.scw.cloud` (Scaleway's infrastructure).
- No Malicious Associations: No ties to Tor, VPNs, or known malicious campaigns.
---
**5. Recommendations**
- Monitoring: Track for unexpected port openings or TLS certificate changes.
- Firewall: Allow traffic on ports 80/443; no blocking required based on risk profile.
- Context: Legitimate cloud server; no immediate mitigation needed.
Conclusion: 212.47.252.101 is a Scaleway-managed cloud instance with no malicious activity detected. Maintain standard monitoring practices for cloud infrastructure.
Source: IPDebrief Threat Intelligence Platform.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | MNT-TISCALIFR |
| ASN | AS12876 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 101-252-47-212.instances.scw.cloud |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 101-252-47-212.instances.scw.cloud |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | 2/2 domains |
| DMARC | 1/2 domains |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
| Domains Checked | 2 domains |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | nginx |
| HTTP Title | — |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=lic01.par1.scw-prod.arkmap.net, C=SK
Issued by CN=lic01.par1.scw-prod.arkmap.net, C=SK
Self-signed: Yes
| SANs | lic01.par1.scw-prod.arkmap.net |
| Valid From | 2026-05-19T10:31:14+00:00 |
| Valid Until | 2036-05-16T10:31:14+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 3650 days |
| Serial Number | 1A017DDBE46D932B182753F7BA07A9B99DE8812D |
| Thumbprint | 71502269B0F85DAD43664B024B991C3C5B5E4B90 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 28% | 2 | 3 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 31% | 2 | 3 |
| Overall | 25% | 10 | 17 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mixed Signals (68%) — 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Geo sources disagree on country: SK, FR
⚠ TLS certificate claims SK but primary geo says FR
⚠ TLS certificate claims SK but primary geo says FR
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-09 11:33:53 UTC |
| Last Seen | 2026-06-27 15:29:35 UTC |
| Profile Built | 2026-06-28 09:33:49 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 31 |
🔍 24 signal types · 31 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.