IPDebrief

213.95.149.22

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 213.95.149.22

*Generated via IPDebrief Analysis*

---

**1. Core Threat Profile**

- Tor exit node activity observed

- Blacklisted in 1 DNSBL (DNS-Based Open Resolver Pollution)

- No known malware campaigns or spam associations

---

**2. Ownership & Infrastructure**

- Subnet: 213.95.149.22/24 (abuse density: 0%)

- No malicious siblings or neighbors detected

- Open SSH port (22/tcp) with banner: *"SSH-2.0-OpenSSH_10.0p2 Debian-7"*

- No TLS certificates or HTTP services detected

---

**3. Temporal Observations (Last 30 Days)**

- 14 total observations (12/24 signals analyzed)

- Consistent Tor exit node classification (confidence: 0.29โ€“0.90)

- No significant changes in risk profile or network behavior

- No persistent malicious activity (threat persistence days: 0)

---

**4. Relationships & Dependencies**

- PTR hostname: `tor.m-u.xyz` (linked to Tor exit node)

- No email authentication (SPF/DKIM/DARC) detected

- Same network as `SMURF-EXTERN-NET` (likely internal or shared infrastructure)

- No direct ties to known malicious organizations or subnets

---

**5. Recommended Actions**

- Block SSH access to this IP unless explicitly required.

- Filter traffic to `tor.m-u.xyz` for further investigation.

- Track DNS queries to `tor.m-u.xyz` for potential command-and-control (C2) activity.

- Monitor for new Tor exit nodes in the 213.95.0.0/16 range.

---

Conclusion:

This IP is a Tor exit node linked to `tor.m-u.xyz`, which may be used for anonymized malicious activity. While the subnet shows no abuse, the Tor association and DNS ties warrant close monitoring. SOC teams should prioritize blocking Tor exit nodes and investigate the linked domain for potential threats.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฉ๐Ÿ‡ช Germany
RegionBavaria
CityNuremberg
TimezoneEurope/Berlin
Latitude51.17
Longitude10.45

๐Ÿข Ownership & Registration

Organizationnoris network netmaster
ASNAS12337
Network Nameโ€”
CIDR Blockโ€”
RIRRIPE
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRtor.m-u.xyz
Forward ConfirmedYes โ€” FCrDNS verified
Forward Hostnamestor.m-u.xyz

๐Ÿ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSVerified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeSingle-Service Host
Network TierTier 3 โ€” Basic operator with some routing infrastructure
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
22sshtcp
Closed Ports25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”
SSH VersionSSH-2.0-OpenSSH_10.0p2 Debian-7

๐Ÿ” TLS Certificate

๐Ÿ”’
No certificate
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
22%
24
routing
13%
11
services
15%
22
ownership
24%
23
reputation
24%
13
geolocation
27%
23
Overall21%1016
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-22 13:35:43 UTC
Last Seen2026-06-26 21:06:49 UTC
Profile Built2026-06-27 17:09:45 UTC
Data FreshnessLive
Signal Types24
Total Observations53
๐Ÿ” 24 signal types ยท 53 observations collected
This report is generated from 24+ 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

โ„น๏ธ 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.