Your IP: 216.73.217.11
🏢 Ownership & Registration
| Organization | Unknown |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | — |
| Country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 0% (None) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 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 | — |
| HTTP Title | — |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=1, C=CN
Issued by CN=1, C=CN
Self-signed: Yes
| SANs | None |
| Valid From | 2026-10-15T13:10:27+00:00 |
| Valid Until | 2029-07-12T13:10:27+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_128_GCM_SHA256 |
| Signature Algorithm | sha256RSA |
| Validity Period | 1001 days |
🛡️ Public Network Snapshot
| Origin ASN | AS58224 |
| Network Prefix | 46.100.48.0/21 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 35% | 2 | 2 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 14% | 4 | 4 |
Coverage: 3/6 dimensions · Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Low (30%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-11-01 08:38:10 UTC |
| Last Seen | 2026-11-01 08:38:10 UTC |
| Profile Built | 2026-11-01 08:56:35 UTC |
| Data Freshness | Live |
| Signal Types | 10 |
| Total Observations | 10 |
🔍 10 signal types · 10 observations collected
This report is generated from 10+ 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.
❓ Frequently Asked Questions About 46.100.53.197
Is 46.100.53.197 malicious or safe?
46.100.53.197 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 46.100.53.197?
Responsive ports observed on 46.100.53.197 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
ℹ️ 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.