148.113.221.144
IP Intelligence Dossier
Your IP: 216.73.217.34
🏢 Ownership & Registration
| Organization | OVH Hosting, Inc. |
| ASN | AS16276 |
| Network Name | SD-ONENETWORK |
| CIDR Block | 148.113.221.0/24 |
| RIR | ARIN |
| Country | Canada |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | ns5038816.git.rancher.io |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | ns5038816.git.rancher.io |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | 2/3 domains |
| DMARC | 2/3 domains |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Not configured |
| Domains Checked | 3 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 | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_9.6 |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Issued by CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Self-signed: Yes
| SANs | ingress.local |
| Valid From | 2026-09-10T19:15:40+00:00 |
| Valid Until | 2027-09-10T19:15:40+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
| Serial Number | 71F4DFC9DB6E39185F570A9194A46047 |
| Thumbprint | 94B9488840F2281AAE5F4E5C079A514299A15386 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 43% | 2 | 5 |
| routing | 13% | 1 | 1 |
| services | 33% | 2 | 4 |
| ownership | 27% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 35% | 2 | 3 |
| Overall | 30% | 10 | 19 |
Coverage: 2/6 dimensions · Data sufficiency: partial
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-13 07:28:45 UTC |
| Last Seen | 2026-09-20 19:08:14 UTC |
| Profile Built | 2026-09-20 19:17:09 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 32 |
🔍 22 signal types · 32 observations collected
This report is generated from 22+ 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.