IPDebrief

2.27.54.13

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

## EXECUTIVE SUMMARY

IP 2.27.54.13 is assessed as MODERATE RISK (55/100). The address belongs to Xorek.Cloud Moscow (ASN 215590) within the 2.27.54.0/24 CIDR block. No active malicious indicators were detected, though the IP is listed on 3 of 8 DNSBLs. The IP hosts no active services and appears to be firewalled.

## OWNERSHIP AND GEOLOCATION

## THREAT INDICATORS

## NETWORK CLASSIFICATION

## NETWORK NEIGHBORHOOD ANALYSIS

- 2.27.54.62 (Risk Score: 25, Authority Score: 50)

- 2.27.54.133 (Risk Score: 25, Authority Score: 50)

## OBSERVATION HISTORY

## RELATIONSHIP GRAPH

## CONTROL PLANE DATA

## RECOMMENDED ACTIONS

Risk Score: 55/100 β€” Monitoring recommended

SystemAction
iptables`iptables -A INPUT -s 2.27.54.13 -j DROP`
nftables`nft add rule inet filter input ip saddr 2.27.54.13 drop`
nginx`deny 2.27.54.13;`
pfSenseBlock 2.27.54.13/32
Cloudflare WAFBlock IP with filter expression `ip.src eq 2.27.54.13`
AWS WAFAdd to rule group with description "IPDebrief risk 55"

Primary Recommendation: Increase logging verbosity and review recent activity from this IP due to elevated risk score (55/100).

## ANALYSIS NOTES

This IP address shows moderate risk characteristics without active malicious indicators. The primary concern is the presence on multiple DNSBLs combined with the risk score of 55. The absence of open ports and services suggests either a dormant infrastructure or a purely internal/network-layer presence. The geolocation discrepancies (US vs RU signals) warrant monitoring but do not indicate active threat behavior. The subnet's low abuse density and neighbor risk profiles suggest this is an isolated moderate-risk address within otherwise benign infrastructure.

Classification: Moderate Risk β€” Monitor but block by default

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNJ
CityNewark
Timezoneβ€”
Latitude40.74
Longitude-74.17

🏒 Ownership & Registration

OrganizationXorek.Cloud Moscow
ASNAS215590
Network Namexorekcloud-msk
CIDR Block2.27.54.0/24
RIRRIPE
CountryRU
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 PurposeSingle-Service Host
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
3389rdptcpβ€”
Closed Ports22, 25, 80, 443, 8080, 8443 (1 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
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-25 02:41:46 UTC
Last Seen2026-07-30 02:01:52 UTC
Profile Built2026-07-30 02:15:49 UTC
Data FreshnessLive
Signal Types17
Total Observations17
πŸ” 17 signal types Β· 17 observations collected
This report is generated from 17+ 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.