IPDebrief

212.58.114.231

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

Date: 2026-06-13

---

**1. Core Profile**

---

**2. Observation History**

- No persistent malicious behavior or ownership changes.

- DNSBL Listings: Identified in 3 out of 8 DNSBLs (e.g., Spamhaus, OpenBL, SpamRbl).

- DNSSEC Validity: Confirmed valid.

- BGP Prefix: Routable via AS16010 (MagticomAS) with stable route stability.

---

**3. Relationships & Network Context**

- Same network: *GE-IMEDI* (AS16010).

- No neighboring IPs detected in the 212.58.114.0/24 subnet.

- Subnet abuse density: 0% (no malicious activity in sibling IPs).

---

**4. Threat & Risk Assessment**

---

**5. Recommended Actions**

1. Monitor DNSBL Listings: Investigate why the IP is listed in 3 DNSBLs (e.g., spam, phishing).

2. Verify DNS Configuration: Ensure no misconfigured PTR records or spoofed domains.

3. Check Subnet Isolation: Confirm if the IP is part of a legitimate, isolated network segment.

4. Review BGP Anomalies: Confirm AS16010's routing policies to ensure no unintended traffic leakage.

---

Conclusion:

The IP exhibits no direct malicious activity but shows indirect risks via DNSBL listings. SOC teams should prioritize validating DNS configurations and investigating the source of DNSBL inclusions. No immediate blocking required, but ongoing monitoring is advised.

Source: IPDebrief Threat Intelligence Platform

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-NY
CityNew York
TimezoneAmerica/New_York
Latitudeβ€”
Longitudeβ€”

🏒 Ownership & Registration

OrganizationCaucasus Online NOC
ASNAS16010
Network NameGE-IMEDI
CIDR Block212.58.114.0/24
RIRRIPE
CountryGE
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
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β€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
0%
00
routing
0%
00
services
0%
00
ownership
25%
12
reputation
0%
00
geolocation
0%
00
Overall4%12
Coverage: 1/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-06-07 07:50:09 UTC
Last Seen2026-06-13 19:23:06 UTC
Profile Built2026-06-13 19:49:03 UTC
Data FreshnessLive
Signal Types16
Total Observations16
πŸ” 16 signal types Β· 16 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.