IPDebrief

203.12.31.167

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

## Threat Intelligence Briefing: 203.12.31.167/32

Date: 2026-08-10

Classification: Moderate Risk

Prepared by: IPDebrief Intelligence Analysis

---

Executive Summary

IP address 203.12.31.167 is a Tor exit node associated with ASN 210083 (SE-OMA-19950123) originating from the APNIC region. The address presents a moderate risk profile (score: 59) with confirmed Tor exit node activity and one DNSBL listing. No active services or open ports were detected on the IP. The subnet environment shows low-to-moderate abuse density (0.25), with three neighboring IPs exhibiting comparable risk scores (49-59).

---

Technical Profile

AttributeValue
**Risk Score**59 (Moderate)
**ASN**210083
**Organization**lir-se-oma-1-MNT
**CIDR**203.12.31.0/24
**Geolocation**Stockholm, SE (APNIC RIR)
**Timezone**Europe/Stockholm
**Network Role**Tor Exit Node
**Threat Indicators**Tor exit node indicators observed
**Blacklist Status**Listed on 1 of 8 DNSBLs
**Route Stability**Stable (no changes in 30 days)

---

Threat Assessment

Primary Risk Factor: Tor Exit Node Activity

Observed Signals:

Temporal Analysis:

---

Neighborhood Analysis

Subnet: 203.12.31.0/24

Notable Neighbors:

IP AddressRisk ScoreAuthority Score
203.12.31.874950
203.12.31.994950
203.12.31.1015950

The subnet contains three additional active IP addresses, all with moderate risk scores (49-59). One neighbor (203.12.31.101) matches the risk profile of the target IP.

---

Relationships

The IP maintains 395 relationships primarily linked to the network identifier SE-OMA-19950123. All relationships are classified as "Same Network," indicating the IP is part of a larger infrastructure cluster with consistent routing and ownership attributes.

---

Recommended Actions

SOC/Security Operations:

1. Monitor for Tor Traffic Patterns: Flag any outbound connections to this IP as potentially anonymized traffic requiring investigation

2. Block at Perimeter: Consider blocking inbound connections to this IP at network perimeter if not required for business operations

3. Correlate with Logs: Search SIEM for connection attempts from known Tor exit node IP ranges

4. Whitelist Decision: Evaluate if this IP should be whitelisted for legitimate use cases (e.g., privacy-focused users, CDN providers)

Firewall Rules (iptables/nftables):

```

# Recommended: Block Tor exit nodes (adjust as needed for business requirements)

iptables -A INPUT -s 203.12.31.167/32 -j DROP

```

Cloudflare/AWS WAF:

---

Intelligence Notes

---

Status: Monitor. This IP represents a known Tor exit node with moderate risk. No immediate threat indicators, but traffic from Tor exit nodes should be treated as potentially suspicious depending on organizational policy.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

Country🇸🇪 Sweden
RegionNorth Holland
CityAmsterdam
TimezoneEurope/Stockholm
Latitude52.35
Longitude4.94

🏢 Ownership & Registration

Organizationlir-se-oma-1-MNT
ASNAS210083
Network NameSE-OMA-19950123
CIDR Block203.12.31.0/24
RIRAPNIC
CountrySE
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)

🔐 DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierTier 3 — Basic operator with some routing infrastructure
Tor

🔌 Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

🔒
No certificate
Issued by —
N/A
SANsNone
Valid From—
Valid Until—

🛡️ Public Network Snapshot

Origin ASNAS210083
Network Prefix203.12.31.0/24
Route mappingFound
RPKI StatusValid

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
27%
24
routing
26%
23
services
12%
22
ownership
37%
35
reputation
27%
13
geolocation
23%
23
Overall25%1220
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (65%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-07-06 11:47:31 UTC
Last Seen2026-08-27 02:21:45 UTC
Profile Built2026-08-29 06:29:15 UTC
Data FreshnessLive
Signal Types27
Total Observations29
🔍 27 signal types · 29 observations collected
This report is generated from 27+ 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.
{ } JSON API 🔧 Actions API 📧 Enterprise Access

❓ Frequently Asked Questions About 203.12.31.167

Who owns the IP address 203.12.31.167?

203.12.31.167 is registered to lir-se-oma-1-MNT. The address falls within the 203.12.31.0/24 network block. Registration is held at APNIC.

Where is 203.12.31.167 located?

Geolocation data places 203.12.31.167 in Amsterdam, North Holland, Sweden. The local time zone is Europe/Stockholm. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 203.12.31.167 malicious or safe?

203.12.31.167 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.

Is 203.12.31.167 a VPN, proxy, or data center address?

203.12.31.167 is classified as the Tor network based on network ownership and behavioural analysis.

🏘️ Related IP Addresses

Nearby addresses in 203.12.31.0/24

Browse related networks

ℹ️ 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.