IPDebrief

154.127.36.139

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 154.127.36.139

Classification: Moderate Risk | Risk Score: 55/100 | Date: 2026-07-29

---

## Executive Summary

IP address 154.127.36.139 presents moderate threat risk with elevated neighborhood activity. The subnet exhibits 20% abuse density with 3 high-risk siblings. No active services detected on target IP, but DNSBL listings and geolocation inconsistencies warrant monitoring.

---

## Network Ownership & Geolocation

AttributeValue
ASN37292 (Christian N. MIGNAN)
CIDR Block154.127.36.0/24
RIRafrinic
Reported LocationsBoston, MA, US / Cotonou, Benin
Geolocation Confidence85%
Route Stability**UNSTABLE**

Note: Conflicting geolocation data detected. US and Benin locations observed in recent signals.

---

## Threat Indicators

---

## Subnet Analysis (154.127.36.0/24)

MetricValue
Total Siblings15 active
Abuse Density20% (0.2)
High-Risk Neighbors3 IPs
Medium-Risk Neighbors11 IPs
Low-Risk Neighbors1 IP

High-Risk Siblings: 154.127.36.209 (80), 154.127.36.232 (80), 154.127.36.237 (80)

---

## Historical Observations

Recent signal history (10 observations):

---

## Recommended Actions

Priority: Monitor / Block (based on risk score 55)

SystemRecommended Rule
iptables`iptables -A INPUT -s 154.127.36.139 -j DROP`
nftables`nft add rule inet filter input ip saddr 154.127.36.139 drop`
Nginx`deny 154.127.36.139;`
pfSense`154.127.36.139/32`
Cloudflare WAFBlock with expression: `ip.src eq 154.127.36.139`
AWS WAFAddresses: `["154.127.36.139/32"]`

---

## SOC Analyst Notes

1. Elevated Risk Score (55/100) triggers monitoring recommendation

2. Subnet Abuse Density (20%) suggests coordinated or shared infrastructure risk

3. Geolocation Inconsistencies between US and Benin may indicate routing anomalies or spoofing

4. No Active Services detected reduces immediate exploitation risk

5. Route Instability detected in BGP control plane data

Recommendation: Implement blocking rule with monitoring enabled. Investigate subnet-wide activity patterns and consider blocklisting entire /24 if business case supports it given 20% abuse density.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-MA
CityBoston
TimezoneAmerica/New_York
Latitude42.36
Longitude-71.06

🏒 Ownership & Registration

OrganizationChristian N. MIGNAN
ASNAS37292
Network Name154.127.36.0 - 154.127.36.255
CIDR Block154.127.36.0/24
RIRAFRINIC
CountryBJ
Abuse Contactβ€”

🌐 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 PurposeWeb Server
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
Serverlighttpd/1.4.39
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
25%
11
routing
25%
11
services
25%
11
ownership
0%
00
reputation
0%
00
geolocation
0%
00
Overall12%33
Coverage: 3/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-07-24 14:25:56 UTC
Last Seen2026-08-09 23:07:36 UTC
Profile Built2026-08-04 11:51:12 UTC
Data FreshnessLive
Signal Types16
Total Observations17
πŸ” 16 signal types Β· 17 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.