IPDebrief

178.219.97.130

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: 178.219.97.130

Date: 2026-06-07

---

**1. Core Risk Profile**

---

**2. Observation History**

- Subnet abuse density increased to 0.429 (mixed classification) over 30 days.

- High-risk neighbors (80+ score) detected in the 178.219.97.0/24 subnet.

- No persistent malicious behavior or long-term threat persistence.

---

**3. Network Relationships**

- Subnet: 178.219.97.0/24 (abuse density: 0.375).

- Organization: MOKADI (Kamil Kazmierczak).

- BGP prefix: 178.219.96.0/20 (RIPE).

- DNSSEC valid; no CAA records.

- Route stability: Unstable (0 route changes last 30 days).

---

**4. Neighborhood Analysis**

- 7 total IPs, 3 high-risk (80+ score), 3 medium-risk (55–70), 1 low-risk (30).

- Notable neighbors:

- 178.219.97.67 (80), 178.219.97.180 (30), 178.219.97.188 (80).

- Subnet abuse density: 42.9% (moderate risk).

---

**5. Recommendations**

- Monitor high-risk neighbors (e.g., 178.219.97.67, 178.219.97.188) for potential lateral movement.

- Validate DNSSEC and check for CAA records in the MOKADI domain.

- Consider blocking high-risk neighbors via firewall rules (e.g., iptables, Cloudflare WAF).

- Investigate DNSBL listings (3/8) for potential abuse.

---

Source: IPDebrief Threat Intelligence Platform

Note: No immediate action required for 178.219.97.130 itself, but contextual risks from neighbors and subnet abuse warrant closer scrutiny.

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

🌍 Geolocation

CountryπŸ‡΅πŸ‡± Poland
Region10
CityWolborz
TimezoneEurope/Warsaw
Latitude51.92
Longitude19.15

🏒 Ownership & Registration

OrganizationKamil Kazmierczak
ASNAS51079
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
Countryβ€”
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 TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Serverβ€”
HTTP Titleβ€”

πŸ” 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
15%
22
routing
13%
11
services
8%
11
ownership
24%
23
reputation
13%
12
geolocation
27%
23
Overall17%912
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 23:35:11 UTC
Last Seen2026-06-26 18:10:50 UTC
Profile Built2026-06-23 19:19:00 UTC
Data FreshnessLive
Signal Types16
Total Observations18
πŸ” 16 signal types Β· 18 observations collected
This report is generated from 16+ 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.