83.233.97.33
83.233.97.33 is an IPv4 address operated by BREDBAND2, SE (AS29518), with approximate network location London, United Kingdom. As of November 14, 2026, IPDebrief rates it Low Risk (15/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | BB2-MNT |
| ASN | AS29518 |
| Network Name | BREDBAND2-NET-SE |
| CIDR Block | 83.233.97.0/24 |
| RIR | RIPE |
| Network registration country | SE |
| Routing operator | BREDBAND2, SE |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
DNS Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| caa | Not found at queried name com |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Unknown / lookup inconclusive 33.97.233.83.in-addr.arpa |
| fcrDns | Not checked |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Multi-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 443, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| Port | Latest capture attempt |
|---|---|
| 443 | Certificate not captured; current certificate unknown (unreachable) |
| 8443 | Certificate not captured; current certificate unknown (unreachable) |
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS29518 |
| Network Prefix | 83.233.0.0/16 |
| 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 | 28% | 2 | 9 |
| routing | 15% | 1 | 2 |
| services | 23% | 2 | 6 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 20% | 2 | 3 |
| Overall | 19% | 9 | 23 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Recent
| First Seen | 2026-08-02 17:02:51 UTC |
| Last Seen | 2026-11-14 14:50:48 UTC |
| Profile Built | 2026-11-14 04:53:28 UTC |
| Data Freshness | Recent |
| Signal Types | 20 |
| Total Observations | 46 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 83.233.97.33
Who owns the IP address 83.233.97.33?
83.233.97.33 is registered to BB2-MNT. The address falls within the 83.233.97.0/24 network block. Registration is held at RIPE.
Where is 83.233.97.33 located?
Geolocation data places 83.233.97.33 in London, Västra Götaland County, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 83.233.97.33 malicious or safe?
83.233.97.33 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 83.233.97.33?
Responsive ports observed on 83.233.97.33 include 80, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.