# IP Intelligence Briefing: 5.253.146.130
## Executive Summary
IP address 5.253.146.130 is classified as Low Risk with a risk score of 25. The address belongs to IGRA-SERVICE NOC (ASN 33991) and is geolocated to Krasnoyarsk Krai, Russia. The IP shows no active threat indicators and presents as a firewalled infrastructure address with no open services.
## Ownership and Network Context
- Organization: IGRA-SERVICE NOC
- ASN: 33991
- BGP Prefix: 5.253.144.0/22
- RIR: RIPE
- Geolocation: Krasnoyarsk Krai, RU
- DNS PTR Host: c0b2wj.g-service.ru (forward confirmed)
- Network Classification: Firewalled / No Services
## Threat Assessment
Risk Profile: Low Risk
- Risk Score: 25/100
- Abuse Confidence: Not available
- Blacklist Count: 0
- Tor Exit Node: No
- Known Attacker: No
- Spam Source: No
- Known Campaigns: None correlated
Control Plane Observations:
- DNSSEC: Valid
- RPKI State: Not evaluated
- Route Changes (30d): 0
- DNSBL Listings: 1 of 8 total lists
## Services and Ports
No open services detected. The IP presents as firewalled with no active HTTP, TLS, or service banners observed.
## Neighborhood Analysis (5.253.146.0/24)
- Abuse Density: 0
- Subnet Classification: Mostly Clean
- Threat Siblings: 1
- Active Siblings: 0
- Total Siblings: 1
## Observation History
19 historical observations recorded. Most recent activity dated 2026-06-18. Key observations:
- Geographic signals consistently point to Russia
- No persistent malicious behavior detected
- Single threat observation recorded
- ICMP validation blocked (unable to validate)
## Relationship Graph
27 relationship entries identified:
- DNS Associations: c0b2wj.g-service.ru (multiple entries)
- Network Associations: RU-IGRA-SERVICE-20190208 (multiple entries)
## Recommended Actions
No immediate blocking recommended based on current risk profile. Monitoring advised for:
- DNSBL listing changes
- Any emergence of open services
- Neighborhood activity correlation
## SOC Analyst Notes
This IP represents infrastructure for IGRA-SERVICE NOC with no active malicious indicators. The low risk score (25) and absence of threat indicators suggest benign network activity. Standard monitoring protocols apply. If traffic from this IP exhibits anomalous behavior, correlate with neighborhood IP 5.253.146.130 and investigate potential service enumeration or configuration changes.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | IGRA-SERVICE NOC |
| ASN | AS33991 |
| Network Name | โ |
| CIDR Block | โ |
| RIR | RIPE |
| Country | โ |
| Abuse Contact | Available via RDAP |
๐ DNS Intelligence
| PTR | c0b2wj.g-service.ru |
| Forward Confirmed | Yes โ FCrDNS verified |
| Forward Hostnames | c0b2wj.g-service.ru |
๐ DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Present |
โ๏ธ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Tier 3 โ Basic operator with some routing infrastructure |
๐ Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | โ |
| HTTP Title | โ |
๐ TLS Certificate
| SANs | None |
| Valid From | โ |
| Valid Until | โ |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 24% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 11% | 1 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 24% | 1 | 3 |
| geolocation | 32% | 2 | 3 |
| Overall | 22% | 9 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-07 23:04:24 UTC |
| Last Seen | 2026-06-23 15:27:12 UTC |
| Profile Built | 2026-06-23 15:31:54 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 22 |
Full dossier details are available via our API.