83.209.250.100
83.209.250.100 is an IPv4 address operated by BREDBAND2, SE (AS29518), with approximate network location London, United Kingdom. Its reverse DNS name is h83-209-250-100.cust.bredband2.com. As of November 14, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | BB2-MNT |
| ASN | AS29518 |
| Network Name | BREDBAND2-NET-SE |
| CIDR Block | 83.209.248.0/21 |
| RIR | RIPE |
| Network registration country | SE |
| Routing operator | BREDBAND2, SE |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | h83-209-250-100.cust.bredband2.com |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | h83-209-250-100.cust.bredband2.com |
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.
Partial coverage: 1 conclusive IP DNS checks.
| caa | Not found at queried name com |
| spf | Not found at queried name h83-209-250-100.cust.bredband2.com |
| dmarc | Not found at queried name _dmarc.h83-209-250-100.cust.bredband2.com |
| dnssec | Unknown / lookup inconclusive 100.250.209.83.in-addr.arpa |
| fcrDns | Present / verified h83-209-250-100.cust.bredband2.com |
☁️ 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.209.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 | 31% | 2 | 10 |
| routing | 15% | 1 | 2 |
| services | 23% | 2 | 6 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 20% | 2 | 3 |
| Overall | 19% | 9 | 24 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (40%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Fresh
| First Seen | 2026-08-01 22:42:13 UTC |
| Last Seen | 2026-11-14 14:50:48 UTC |
| Profile Built | 2026-11-14 03:26:29 UTC |
| Data Freshness | Fresh |
| Signal Types | 21 |
| Total Observations | 46 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 83.209.250.100
Who owns the IP address 83.209.250.100?
83.209.250.100 is registered to BB2-MNT. The address falls within the 83.209.248.0/21 network block. Registration is held at RIPE.
Where is 83.209.250.100 located?
Geolocation data places 83.209.250.100 in London, Värmland 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.209.250.100 malicious or safe?
83.209.250.100 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 83.209.250.100?
The reverse DNS (PTR) record for 83.209.250.100 is h83-209-250-100.cust.bredband2.com. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 83.209.250.100?
Responsive ports observed on 83.209.250.100 include 80, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.