181.67.246.47📋 Copy

IP INTELLIGENCE BRIEFING: 181.67.246.47/32

OVERVIEW

IP address 181.67.246.47/32 presents a low-risk profile with no active threat indicators. The address is registered to INTEGRATEL PERÚ S.A.A. within the 181.66.0.0/15 CIDR block (LACNIC RIR). Current risk score: 0. No malicious activity, blacklisting, or campaign associations detected.

OWNERSHIP & REGISTRATION

• Organization: INTEGRATEL PERÚ S.A.A.
• CIDR Block: 181.66.0.0 - 181.67.255.255
• RIR: LACNIC
• Abuse Contact: Available via RDAP
• Registration Date: Not available

GELOCATION ANALYSIS

The profile exhibits geolocation inconsistencies requiring attention:

• Reported Geolocation: New York, US (US-NY)
• Ownership Registration: Peru (PE), Lima
• GeoValidation: GeoPlausible flag set to false
• Transit Networks: Comcast (17 hops timed out, 30 total hops)

NETWORK CLASSIFICATION

• Service Purpose: Firewalled / No Services
• Open Ports: None detected
• DNS Records: No PTR, no forward resolution, no hosted domains
• Email Authentication: No SPF, DMARC, or TXT records
• Is Cloud/CDN/VPN/Proxy: Negative across all categories
• Bogon Status: Negative

THREAT INDICATORS

• Risk Score: 0
• Blacklist Count: 0
• Abuse Confidence Score: None
• Known Campaigns: None
• Tor Exit Node: No
• Known Attacker: No
• Spam Source: No
• Threat Feeds: Empty

HISTORICAL OBSERVATIONS

Six observations recorded from 2026-07-07 through 2026-07-24. Recent signals (2026-07-24) show continued ownership attribution to INTEGRATEL PERÚ S.A.A. with geolocation signals fluctuating between Peru and US. No escalation in threat signals observed over the observation period.

RELATIONSHIPS & NEIGHBORHOOD

• Network: 181.6

Thinking Process:

1. Analyze the Request:

* User wants me to continue exactly where I left off in the previous response.

* The previous response was cut off mid-sentence in the "RELATIONSHIPS & NEIGHBORHOOD" section.

* The instruction is to finish the remaining answer only, without repeating text already written.

* The persona is an IP intelligence analyst for IPDebrief.

* Tone: Factual, professional, third person, past tense, based only on provided data.

* Constraint: Do not include disclaimers about being an AI.

2. Locate the Break Point:

* The last sentence written was: "- Network: 181."

* I need to complete the sentence and the section based on the data provided in the tool outputs.

3. Review Available Data for Continuation:

* Relationships: One relationship found ("Same Network" -> "181.66.0.0 - 181.67.255.255").

* Neighbors: Subnet 181.67.246.47/24. Neighbor count: 1. Risk distribution: 1 low. Abuse density: 0. Neighbor IP: 181.67.246.77 (riskScore: 0, authorityScore: 50).

* Actions: Risk Score: 0. Recommendations: Empty list. Firewall Rules: null.

* Threat/Campaign: No matches, likelihood null, zero incidents.

* Control Plane: Route changes 30d: 0. Is Route Stable: false. DNSSEC Valid: false.

4. Draft the Continuation:

* Complete the "Network" line.

* Summarize the neighborhood data (181.67.246.77).

* Include Actionable Recommendations (empty based on data, but mention status).

* Include Control Plane/Technical details (DNSSEC, Route Stability).

* Conclude the briefing.

5. Refine Content:

* *Network:* 181.67.246.47 belongs to the 181.66.0.0/15 block.

* *Neighbors:* Only one neighbor found in /24 subnet (181.67.246.77). Both have low risk.

* *Recommendations:* No specific actions recommended by the tool due to low risk.

* *Technical:* No BGP prefix, no RPKI state data, route stability marked false despite 0 changes.

* *Conclusion:* Maintain monitoring due to geolocation inconsistency.

6. Verify Constraints:

* Third person? Yes.

* Past tense? Yes.

* No AI disclaimers? Yes.

* No speculation beyond data? Yes.

* Continue exactly from "- Network: 181."? Yes.

7. Final Polish:

* Ensure the transition is smooth.

* Check formatting to match the previous section style.

*Draft:*

.66.0.0 - 181.67.255.255

* Sibling Analysis: 0 threat siblings identified.

* Neighbor Analysis: Subnet 181.67.246.47/24 contains one neighbor (181.67.246.77) with a risk score of 0 and authority score of 50.

* Recommendations: No firewall rules or mitigation actions are currently recommended due to the absence of threat indicators.

* Control Plane: BGP prefix data unavailable. Route stability is marked false despite zero route changes in the last 30 days. DNSSEC validation is invalid.

* Conclusion: The IP exhibits no active malicious behavior. Monitoring is advised due to conflicting geolocation data between ownership records (Peru) and probe location (US).

*Wait, I need to check the exact cutoff.*

The cutoff was: `"- Network: 181.`

So I continue from `66.0.0 - 181.67.255.255`

*Let's construct the full continuation.*

`66.0.0 - 181.67.255.255`

- Abuse Density: 0

- Inherited Risk: 0

*Technical Control Plane:*

- Route Stability: Marked false despite zero route changes in the last 30 days.

- DNSSEC Validation: Invalid

- RPKI State: Not reported

*Operational Status:*

- Firewall Rules: None detected

- Recommendations: No specific actions recommended based on current risk score of 0.

*Assessment:*

No active threat indicators were observed. The primary anomaly remains the geolocation discrepancy between the RIR registration (Peru) and observed probe locations (New York, US). No immediate blocking is warranted based on current data.

*Wait, I need to make sure I don't repeat the bullet points that were already started.*

The previous text ended with:

`"- Network: 181.`

So I start with `66.0.0 - 181.67.255.255`.

Let's assemble the full text.

`- Network: 181.66.0.0 - 181.67.255.255`

- Ab

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